Data can be reviewed using the Subject Matrix or the Queries page. Each of these review options is outlined below. Monitors also have the option of reviewing data using the Source Data Verification page.

Review and Manage Data from the Participant Matrix

Typically, Monitors and Data Managers are responsible for reviewing data, but anyone with access to the Participant Matrix can view/review data as needed. Data Managers can also remove a participant and/or reassign a participant to a different site. The actions column presents the appropriate actions available, based on your user role. The following displays the actions available to a Data Manager:

Remove a Participant

Data Managers have access to remove Participants. Removing a Participant does not delete the Participant, but instead removes access to that Participant’s data. The data for that subject can still be viewed, but cannot be edited and will not be included in data extracts. Once a Participant is removed from the study, the remove icon changes to a restore icon. To restore access to that Participant’s data, simply click the restore icon and the data is available again for editing and extracts. 

Reassign a Participant

Data Managers also have access to reassign a Participant to another Site. This may be needed if a Participant moves to a different location but still wants to continue on the Study. Prior to reassigning, be sure that the original Site has an extract of that Participant’s data. Then, to Reassign a Participant, click the Reassign icon. Specify the new site and click Reassign Participant.

The new site has immediate access to that Participant’s forms and all data previously collected for the Participant. The original site no longer has access to that Participant’s ongoing data.

Review Participant Data

To review data, click the view icon for the participant whose data you’d like to review.

The participant detail page displays. All visit-based events are listed first, followed by all common events.

To review data on a specific form, click the view icon for that form.

Filter Participant Details

As you review data, you can enter search criteria for the Common Events – for example, to show only AEs that are ongoing. You can also change the number of rows listed for any of the Common Events, and you can sort Common Events by clicking the toggles next to any of the column headings. When you customize anything related to what is displayed for Common Events, the Custom View On button displays at the top of the Participant Detail page.

The Custom View is active for that participant throughout the time you are logged into OpenClinica. If you view a different participant’s detail page, the view may not be customized, or if it is, it may be a different customization. In the example above, throughout the current session, any time you view participant 001, that same custom view is in effect.

To clear a custom view, click anywhere on the Custom View On button and all view customizations are removed for that participant.

 

Form Migration

 

Overview: Data Managers can migrate Form data on a Participant-by-Participant basis or in a batch.

Definition: Form migration is the ability to transfer data from one Form version to another.

Example: A Data Manager might choose to migrate Form data in order to update the Form to a new version.

 

If there are multiple versions of a Form available before data has been entered, any user can choose which version to use. 

However, if data has already been entered and a new Form version becomes available afterward, you must have a User Role of Data Manager to migrate Form data. You can migrate data either on a Participant-by-Participant basis or in a batch.

Form migration causes the following:

  • Audit Log: Form migration appears in the Audit Log for the Participant(s) the data was migrated for.
  • E-Signature Status: If a Participant Casebook or Event was signed before the Form migration, that signature is removed, and it must be signed again.
  • SDV Status: If SDV was already performed, the status resets to needs source data verification
  • Extracts: If data existed in the original Form version that does not exist in the new Form version, that data does not appear on extracts. 
  • Response Options: You can remove responses, but the values in the Name field for those that remain cannot be changed. For example, if the options were Mild, Moderate, and Severe (1, 2, and 3) you can remove Severe, but you cannot change Mild from 1 to any other value.

Note: Data will not be deleted from the database due to Form version migration, even if it no longer exists in the new Form version. (See Potential Migration Outcome Examples below for more information.)

 

Requirements:

  • Data Entry Status: Data Entry Started
  • Study Status: Available
  • User Role: Data Manager
  • Participant Status: Active
  • Event Status: Active (not removed, locked, or skipped)
  • Form Status: Active (not removed)
  • New Form Version: Active (not removed)
  • Previous Form Version (used for initial data entry): Active

 

Prerequisites:

  • The study must contain at least 2 versions of a Form.
  • The study must be published.

 

Participant-by-Participant Migration:

  1. Click the View button across from the Participant on the Participant Matrix.
  2. Click the Enter Data button, and enter data. 
  3. When finished entering data, click the Close button or the Complete button.
  4. Click the Reassign CRF to a new version button.

 

 

5. Select the new Form version in the New CRF Version field.

6. Click the Continue button.

 

7. Verify the data mapping information on the Confirm CRF Version screen, and click the Submit button.

 

Batch Migration:

  1. In the header bar of Runtime, select Tasks.
  2. Select CRFs under Monitor and Manage Data.

Click the Batch CRF version migration button next to the CRF you want to update.

 

3. Select the current version of the Form in the Current Version of (Form Name) field.

4. Select the new version of the Form in the New Version of (Form Name) field.

5. (Optional) Select a site to update the version at. (The default is all sites.)

6. (Optional) If the Form is in multiple events, select an Event to update the version in. (The default is all Events.)

7. Click the Preview button.

8. Verify the Migration Summary information that appears below the Preview button.

9. Click the Migrate button.

When you return to the CRF screen, the following message appears under Alerts in the sidebar: Batch CRF version migration is running. You will receive an email once the process is complete

You will receive an email with a link to a report of the migration, which provides a list of all Participants and Forms that the data was migrated for. 

 

Potential Migration Outcome Examples:

 

Example A: More Items in Original Form Version than New Form Version:

Before:

  • Version A has an item named meditem2.
  • Version B does not have an item named meditem2.
  • Both versions have an item named item1.

After:

  • Data for meditem2 is not migrated.
  • Data for item1 is migrated.
  • The user will not see meditem2 in the new Form version.
  • meditem 2 will not appear in extracts but remains in the database.

 

Example B: More Response Options Available in Original Form Version than New Form Version:

Before:

  • Both CRF versions have an item named item1.
  • Version A has the response options X, Y, and Z.
  • Version B only has the response options X and Y.
  • The user selected the response option Z in the original Form version.

 

After:

  • Data for item1 is migrated, but it will appear as though no response was selected since response option Z no longer exists in the new Form version.
  • For single-select types: New data will overwrite existing data.
  • For multi-select types: New response options will be added. (If the user selected the response option Z in the original Form version, and that option no longer exists in the new version of the Form, if they then select the response option Y, both the values of Z and Y will be stored in the database.)

 

Example C: The maximum number of repeats in the original Form version exceeds that in the new Form version:

Before:

  • Both Form versions have a repeating group named group1.
  • The maximum number of repeats in Form A is 5.
  • The maximum number of repeats in Form B is 3.
  • The user entered data for 5 repeats.

After:

  • All 5 rows of data appear on the Form despite the fact that in the new Form version only allows 3 rows of data. 
  • No additional data can be entered.

 

Review and Manage Data from the Queries Page

A table displays queries, annotations, and reasons for change. Details about each query, annotation, or reason for change are listed in the Detailed Notes column. You can also click Show More to show more columns or click the Download or Print button above the table.

To filter by reason for change, click the gray filter box under the Type column, and select Reason for Change. You can change the view of the Queries screen to filter any column that includes a gray filter box.

The table below displays statuses for queries and annotations:

 

Status

Bubble Appearance

Comments

No Query

Click this bubble to create a query.

New

A query has been added by either a site user (e.g., a comment/annotation), data manager, or monitor, or was auto-generated by OpenClinica based on built-in edit checks.

Updated

Either a site user, data manager, or monitor has added information to the query.

Closed

The query is considered resolved by the data manager or monitor.

Closed Modified

Slightly paler than Closed, this means the data was changed after the query was closed

Multiple New Queries (or 1 New and 1 Updated)

You can select each query from the sidebar.

Multiple Updated Queries

You can select each query from the sidebar.

1 or Multiple Annotations

You can select each annotation from the sidebar.

 

To review data associated with a query, you have two options:

  • View Query Only: This option displays a shaded background showing the item value in question, with the query and item history in the foreground. You can add a query comment, assign the query, and you have the option of emailing the assigned user. All users with access to queries can update the query; only Data Managers and Monitors have access to close a query.

  • View Query Within Record: This option displays a shaded background of all the item values on the form for that query. You have access to update the query and update and/or review all the data on the form. This provides reviewers with more context when reviewing specific item data issues.

You can then update the query comment, use the x to close the query details, and review the entire form in question. Data Managers and Monitors have the additional option of closing the query.

If an item only displays based on the response to another question, there may be instances where an item was conditionally displayed, a query was added to that item, and then the response to the lead-in question was changed, so that item is no longer displayed. That query still exists, however, and needs to be addressed.

Similarly, if there is a form that has repeating records and a query was added to a row, but that row has since been deleted, the query still exists, but is no longer displayed on the form. OpenClinica informs you of these hidden items and provides an option for resolving the associated queries.

For example, when the item in question is a response that has since been hidden, or is on a repeating record that has since been deleted, the following message displays:

To review the remaining data on that form, click OK and review the data. To review the data for the item in question, return to the Queries page and use the view icon for that query (as instructed in the message).

Creating Queries

User Roles Who Can Perform this Action: All users

 

Workflow: 

 

  • All users can create queries when reviewing data. 
  • This is part of the standard workflow for Data Managers and Monitors when reviewing data.

 

Use Case(s): 

  • Participant data does not match the source record
  • Participant data is clinically inaccurate
  • Participant data contains a typographical error
  • A form needs to be marked complete
  • Information is missing from a form.
  • A form in an Event was not started on time

 

Description: Users can create queries to inquire about participant data.

Note: Each query is automatically assigned an ID that is unique to the study environment (i.e. Test or Production). The ID appears in the Queries widget but is not visible until you close and reopen the Form. It also appears on the Queries table.

You can add multiple queries regardless of any existing ones. 

You can only add/respond to queries and annotations in Edit Mode, as determined by your User Role. You cannot do so in Read-Only or Review-Only Mode.

You can view the history for all queries and annotations on a single item by selecting View All History, or you can view the history of each query or annotation individually by selecting that query or annotation from the left panel. If you check the Show value changes checkbox, each value change is included in the history.

 

Best Practice: 

  • If a form has not been started when it should have been, a Data Manager can add a query to the events start date.
  • When a query is created, it should be assigned to the correct recipient. If action is required excluding if the query needs to be closed, the Email checkbox should be checked off.
  • A new query should be created for a single issue, instead of combining multiple issues.
  • A new query should be created rather than reopening a query that has already been closed.

 

Instructions:

  1. Open a Form.
  2. Click the Query Bubble in the field you want to create a query for.
  3. Click the +New button next to Queries.
  4. In the Add a new query field, enter text explaining the possible error or question.
  5. (Optional) Select a user from the drop-down list next to Assign to. If you want to email that user to notify them about the query, check the box next to Email. When a query notification email is sent, it includes the Query ID for easy access.
  6. Click the Add Query button.

 

Responding To/Updating Queries

User Roles Who Can Perform this Action: All users

 

Workflow: 

 

  • All users can respond to/update queries when reviewing data. 
  • This is part of the standard workflow for Data Managers and Site and Study Monitors when reviewing data.

 

Use Case(s): 

  • A response is required for the query to be resolved.
  • Participant data must be changed for the query to be resolved.

 

Description: Users can update queries by responding to a query and/or changing data in the form. If data is changed, they will be prompted to enter a reason for change.

Note: 

You can only add/respond to queries and annotations in Edit Mode, as determined by your User Role. You cannot do so in Read-Only or Review-Only Mode.

You can view the history for all queries and annotations on a single item by selecting View All History, or you can view the history of each query or annotation individually by selecting that query or annotation from the left panel. If you check the Show value changes checkbox, each value change is included in the history.

Best Practice: 

  • All users can view a list of queries that have been assigned to them by expanding the Quick Links header in the left-hand sidebar and clicking Queries Assigned to Me.
  • Data Managers can view a list of queries that have been assigned to them by clicking Queries Assigned to Me on the Home screen.
  • When a query is responded to/updated, it should be assigned to the correct recipient. If action is required, the Email checkbox should be checked off.
  • Data Managers and Monitors should review the entire queries list regularly to check for unassigned queries.
  • If a conditional field (a field that appears based on the response to another field) has a query on it but a user has changed the response to the main field so that the conditional field no longer appears, the query still exists and needs to be addressed, but the field no longer appears on the Form. To review the remaining data on that Form, click OK, and review the data. 
  • If there is a form that has repeating records, and a query was added to a row, but that row has since been deleted, the query still exists, but no longer appears on the Form. A message appears to inform you of these hidden items and provides an option for resolving the associated queries. To review the remaining data on that Form, click OK, and review the data. 

Instructions

To respond to or update In a Form:

  1. Open a Form.
  2. Click the Query Bubble in the field you want to create a query for.
  3. Select the query you want to respond to and/or update.
  4. (Optional) If you need to change information in a form, close the Query widget, and make changes to the form manually. You must provide a reason for change before completing the form.
  5. In the Respond to query field, enter text explaining the query response.
  6. (Optional) Select a user from the drop-down list next to Assign to. If you want to email that user to notify them about the query, check the box next to Email. When a query notification email is sent, it includes the Query ID for easy access.
  7. Click the Update button to add the response and leave the query open.

 

To respond to or update a query from the Queries table:

  1.  Click View Query Only or View Query within record in the Actions column of the queries table.
  2. (Optional) If you need to change information in a form, close the Query widget, and make changes to the form manually. You must provide a reason for change before completing the form.
  3. In the Respond to query field, enter text explaining the query response.
  4. (Optional) Select a user from the drop-down list next to Assign to. If you want to email that user to notify them about the query, check the box next to Email. When a query notification email is sent, it includes the Query ID for easy access.
  5. Click the Update button to add the response and leave the query open.

 

Closing Queries

User Roles Who Can Perform this Action: Data Managers and Monitors

 

Workflow: This is part of the standard workflow for Data Managers and Monitors when reviewing data.

Use Case(s): 

  • The information on the form has been changed to address the query.
  • A response clarifies why the existing information is accurate.

Description: Data Managers and Monitors can close queries when the issue has been resolved.

Best Practice: 

  • A new query should be created rather than reopening a query that has already been closed.
  • If a conditional field (a field that appears based on the response to another field) has a query on it but a user has changed the response to the main field so that the conditional field no longer appears, the query still exists and needs to be addressed, but the field no longer appears on the Form. To review the remaining data on that Form, click OK, and review the data. 
  • If there is a form that has repeating records, and a query was added to a row, but that row has since been deleted, the query still exists, but no longer appears on the Form. A message appears to inform you of these hidden items and provides an option for resolving the associated queries. To review the remaining data on that Form, click OK, and review the data. 

Instructions:

To Close a Query In a Form:

  1. Open a Form.
  2. Click the Query Bubble in the field you want to create a query for.
  3. Select the query you want to close.
  4. Click the Close button.

 

To respond to or update a query from the Queries table:

  1.  Click View Query Only or View Query within record in the Actions column of the queries table.
  2. Click the Close button.

 

 

Annotations

 

User Roles Who Can Perform this Action: All users

 

Workflow: This is not part of the standard workflow but might occasionally be necessary.

Use Case(s): A user adds an annotation to keep track of workflow

Description: You can add an annotation to a field to make a note. Annotations cannot be assigned, responded to or closed. 

Best Practices: Annotations should not contain clinical information.

Note: You can view the history for all queries and annotations on a single item by selecting View All History, or you can view the history of each query or annotation individually by selecting that query or annotation from the left panel. If you check the Show value changes checkbox, each value change is included in the history.

 

To enter an annotation:

  1. Open a Form.
  2. Click the Query Bubble in the field for which you want to create an annotation.
  3. Click the +New button next to Annotations.
  4. In the Add a new annotation field, enter text for the annotation.

Click the Add Annotation button.

 

 

 

Source Data Verification

Overview: Monitors can perform Source Data Verification on the Source Data Verification screen, where they can review and verify data against source records.

Definition: Source Data Verification is the process of reviewing and verifying data against source records to ensure accuracy.

Example: Forms containing very important data might require a higher level of SDV than items containing less important data.

 

The Source Data Verification screen is the Monitors home screen.

To access the Source Data Verification screen, click Tasks in the header bar of Runtime, and select Source Data Verification.

 

The Source Data Verification table displays the SDV Status, SDV Requirements, CRF Status, etc. 

SDV Requirements

SDV Requirements are defined by your study protocol. Data Managers and Administrators can specify the level of SDV requirement for a Form in Study Designer.

 

Below is a table that displays basic definitions of each SDV Requirement.

 

 

SDV Requirement

Definition

Not Applicable

SDV is Not applicable to the study, and the form will not be included in the SDV table.

Not Required

SDV is not required for the study, and the Form will not be included in the SDV table.

Partial Required

This is specified by your study protocol but does not require every field to be verified.

100% Required

Every field in the Form must be verified.

 

SDV Table

 

Only Forms with a status of completed appear in the Source Data Verification table. Forms with an SDV Requirement of Not Applicable do not appear on the table.

 

You can click Show More to show more rows. You can also filter a column by clicking the gray box below the column header. You can sort the columns, Event Date and Last Updated Date by clicking the column headers.

 

The Open Queries column displays the number of queries that are open (New or Updated) for a specific CRF. This is a good way to keep track of which CRFs that are likely to change due to outstanding queries.

If the number of queries is 0, the number appears as plain text. If the number of queries is greater than 0, it appears as a link. If you click the link, it takes you to the Queries screen, which is filtered to the Participant, Form, and Event that the row in the SDV table corresponds to.

 

The Lock Status column displays an icon if the Form is locked. 

The View button in the Actions column opens the Form in Review-Only mode, unless the Form is in a status of Locked, in which case, the Form opens in Read-Only mode.

 

 

Click the Data button to view Form information. You can use the radio buttons in the upper-righthand corner to filter with Show all items or Show only changed since last Verified. You can also verify items from this screen.

 

SDV Statuses make it easy for Data Managers and Monitors to quickly evaluate which items to focus their review on.

Forms can have a status of Ready to Verify, Changed since verified, or Verified. If a Form was previously verified, the status will be Changed since verified, and it must be verified again.

SDV statuses are as follows:

Icon

SDV Status

Ready to verify

Changed since verified

Verified

 

You can filter by:

  • Ready to verify + Changed since verified
  • Changed since verified
  • Verified

 

To perform Source Data Verification:

  1. Click on the View icon in the Actions column to view the completed form.

  2. Compare the data entered in the form against the source record.

  3. If there are any discrepancies between the source record and the data on the form, click the query bubble for the item in question and create a query for the site to address.

  4. Complete the review of the data and close the form.

  5. To verify a single item, click the Verify button in the Actions column. This button is available only for Forms with an SDV status of Ready to verify or Changed since verified.

Alternately, you can click the Data button, review the data, and then click the Verify button on that screen.

Click the Verify All Checked button to mark all items Verified.

 

Note: If you inadvertently marked a record as source data verified, you can reset its status by clicking the double-check icon in the SDV Status column. You are prompted to confirm resetting the status.