Mapping Objects
[Rate this topic]

The Object Mapping page allows you to manually map folders, forms, fields, data dictionaries, and unit dictionaries between source and target CRF versions.

The objects are shown as tabs at the top of the Object Mapping page, with the following icons:

Folder

Form (and Fields)

Data Dictionary

Unit Dictionary

Click one of the tabs along the top of this page to manually change the mapping between source and target versions.

Mapping for Folders

The following table describes the mapping for folders:

COLUMN	CHANGE	RESULT	PROCESSING
Folder Name	Different Name	OK
Access Days	Different Value	OK
Start Win Days	Different Value	OK
Target Days	Different Value	OK
End Win Days	Different Value	OK
Overdue Days	Different Value	OK
Close Days	Different Value	OK
Parent Folder ID	Different Value (After mapping parent folder)	OK
Ordinal	Different Value	OK
OID	Different Name		Folder is manually mapped to a new OID
Is Reusable	Different Value	OK

Mapping for Forms

The following table describes the mapping for forms. The table shows a summary of the component fields as well as any line items for any warnings for the form.

Note: If a form in the Source does not exist in the Target, the system marks the data pages, all records, and all data points associated with the form as inactive.

COLUMN	CHANGE	RESULT	PROCESSING
Form Name	Different Name	OK
Form Active	Checked to Unchecked		Any existing data for the form will not show in the User Interface but remain in the database.
Form Active	Unchecked to checked	OK
Ordinal	Different Value	OK
Help Text ID	Different Value	OK
OID	Different Name		Form is manually mapped to new OID
Edit Direction	Different Value	OK
Is Template	Different Value		Existing templates are deleted when moving from checked to unchecked
Confirmation Style	Different Value	OK
Link Form OID	Different Value	OK
Link Folder OID	Different Value	OK

Mapping for Fields

The following table describes the mapping rules for fields, based on database field names and potential change type:

Note:

Mapping for Fields always appears under a Form mapping tab because fields can only be mapped to fields on the same form as the original.
If a field in the Source does not exist in the Target, the system marks all associated data points as deleted.
If a date format for a data field changes, the system converts the existing data into the new format. For example: If date format in the Source is dd/mm/yyyy and Target is mm/dd/yyyy, the existing date is converted to the new format in the Target.

COLUMN	CHANGE	RESULT	PROCESSING
Analyte ID	Different Value		After data migration, all existing lab range checks must rerun
Can Set Data Page Date	Different Value		Affects new data entry only
Can Set Instance Date	Different Value		Affects new data entry only
Can Set Record Date	Different Value		Affects new data entry only
Can Set Subject Date	Different Value		Affects new data entry only
Control Type	Different Value		See Mapping for Control Types.
Default Value	Different Value		Affects only new data
Does Not Break Signature	Different Value		Affects only new data entry
Field Active	Checked to Unchecked		Any existing data for the field will not show in the User Interface but will remain in the database.
Field Active	Unchecked to Checked	OK
Field Name	Different Name	OK
Field Number ID	Different Value	OK
Header Text ID	Different Value	OK
Help Text ID	Different Value	OK
Indent Level	Different Value	OK
Is Child	Different Value	OK	This is not in the User Interface and therefore, should never be different.
Is Clinical Significance	Different Value		After data migration, all existing lab range checks must rerun
Is Log	Log to Non-Log	Error	Change from Log to Non-Log format is not supported.
Is Log	Non-Log to Log	OK
is Visible	Different Value		Affects only new data entry. Existing data relies on the Is Visible setting on the data point.
OID	Different Value		Affects Data Warehouse
Ordinal	Different Value	OK
Other Visits	Different Value	OK
PreText ID	Different Value	OK
PostTextID	Different Value	OK
Requires Translation	Checked to Unchecked		Existing data in DataPointUntranslated is moved to Data Points.
Requires Translation	Unchecked to Checked		Existing data in Data Points is copied to DataPointsUntranslated. Translation is required only on new data.
Source Document	Different Value		Source document verification requirements will change.
Variable ID	Map to different variable		See Mapping for Variables.

Mapping for Data Dictionaries

The following table describes the mapping of data dictionaries and a summary for the component entries:

Note: A dictionary is not required to be mapped. Any data point assigned to the old dictionary is not assigned after migration.

COLUMN	CHANGE	RESULT	PROCESSING
Data Dictionary Name	Different Name	OK
Has Other	Different Value	OK
Is Local	Different Value		Changing between local or external dictionaries is not supported.

The following table describes mapping for data dictionary entries:

COLUMN	CHANGE	RESULT	PROCESSING
Coded Data	Different Value	OK
Ordinal	Different Value	OK
User Data String ID	Different Name	OK
Specify	Unchecked to Checked		Content of DATA are nulled out because this is where the "specify" data is stored. Data point is marked non-conformant.
Specify	Checked to Unchecked		Contents of DATA are replaced by the coded value of OTHER in the dictionary.

Mapping for Unit Dictionaries

The following table describes the mapping of unit dictionaries and a summary for the component entries: