Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Continue studies that need to be moved from another platform into TrialKit

  • Lab values

  • Data Bulk data from an external source to avoid manual/hand-entry

  • Lab values

  • Adding study Participants (ePRO studies)

...

For example, if importing patient physical exam data, a configuration would be set up to import all physical exam data for all patients and all visits at once.  

...

Normalized tables are a separate table from the

...

form they reside in.  That means a form with a normalized table will need TWO configurations: one for the form and one for the table in that form

...

.

All configurations are saved and can be reused in the future without needing to follow these steps.

...

The following descriptions correspond to the image directly below:

...

...

1. Import Configuration Basics

Select one or more options on how the import should be run. All imports will be recorded in the corresponding records' audit trails. The options selected below are a common example, where records will be created if they don't exist. Here are some useful notes on this particular configuration:

  • If the system finds a record already in place, whatever data is mapped will be overwritten - unless 'Update' is not checked.

  • If the source file contains a blank value for a given data point, any existing record data will NOT be overwritten - unless 'Update with null value' is checked.

  • Any sites found under the source file's 'Site' column will automatically be created if they don't exist already.

  • And subjects found in the Sub ID column will be automatically created.

...

2. Import control fields

...

Identify the source file column headers that correspond to: 

  • Subject ID - If the subject Id in the source file does not already exist, the system will create that subject and insert a blank registration form.

  • Date field - All subject records must have a date/transaction field. If the source data does not contain one, it must be created. Be sure the date field on the form that is defined as the transaction date is what is used here. This helps the system identify unique records, along with the search key in item 3 below.

  • Visit Interval - This is what was mapped in the visit interval map on the right side of the page to correspond with the visit column from the source file

  • Site Name - If sites already exist in the study, use the same site names in the source file. Otherwise, the system will automatically create a new site.

...

3. Import search key

...

Identify which data point(s) the system should use to identify unique records. In most cases, this will be the visit date and visit interval that is defined in the Import control fields from item 2 above. The important thing here is to be sure to identify as many items that are necessary to differentiate a record so the system can determine if it is previously existing or not.

...

Info

Consider the different Field Types in the destination form:

  • Choice Fields (dropdown or radio) - Ensure the choices are accurately identified based on what the source file contains. These are case sensitive when using text matching.

  • Checkboxes - The source file must contain 1's and 0's OR TRUE and FALSE. These correspond to checked and unchecked respectively.

  • Date fields - The system is able to parse dates correctly, so don't worry about separating dates from times.

  • Normalized table fields - If importing into a FIXED table, the first column will be used by the system as a search key to determine whether or not to update date in a given table row. This requires mapping the CODED values for each of the choices in the first column of the fixed table. In other words, the source data must use the coded values based on how the destinationi form is configured.

Note

Don't forget to select 'Save Configuration' at the bottom of the page

...

Page Properties
hiddentrue

Related issues