Validation for data mappings

CDD data mappings

Data type compatibility

• All components of a date time item must be required and must not allow unknowns if the date time item is mapped to a data series with a data type of DateTime.
• If one or more parts of a date time item are not required or allowed to be unknown, the data series to which the item is mapped must have a type of Text.
• The length of an item mapped to a data series must not be longer than the value set in the DB Format Length custom property of the data series.
• The precision of a float item mapped to a float data series must not be greater than the value set in the DB Format Float Precision custom property of the data series.
• If a float item is mapped to an integer data series, the precision must be 0.

Date part and split date

If any item is mapped to a data series with the split date option, all items mapped to the data series must use the split date option.

Target key types

• Data series mapped to items in a repeating section cannot have a pivot target key type. Pivot tables are not supported for itemset data.
• If the target key type of the data set is a pivot target key type, one (and only one) data series must be identified as the pivot column.

Data sets and data series

Custom dimensions and custom dimension labels do not reference deleted codelists or codelist items.

CIS data mappings

Block key and page key

The block key and page key must conform to the specifications of the data series for the block key item or page key item in the context panel:

• The data type must convert to a compatible data type.
• The length must be within the length specified in the DB Format Length CIS custom property.
• If the data type of the data series is float, the precision must be within the precision specified in the DB Format Float Precision CIS custom property.

Context panel

• A data mapping can have only one custom context panel.
• The data series in a context panel must have data types of Text, Fixed, or Float.
• The value of the Context Type property of a data series in a context panel cannot be:
  • Other context item if the value of the Is Key property is True.
  • Not a context item.
• A context panel can have only one:
  • Subject key item.
  • Block key item.
  • Page key item.
  • Block repeat key item.
  • Page repeat key item.
• For a subject key item, if the data type of the data series is Text, the value of the DB Format Length custom property cannot be greater than 80.
• Data set aliases used in a context panel cannot be used in data sets for noncontext panels.
• If the study contains a data set that is a custom context panel, and the study contains a common form with one or more items that are mapped to any data series, you must specify a value in the Shared Form Block Key custom property on the study design.

Data type compatibility

• All components of a date time item must be required and must not allow unknowns if the date time item is mapped to a data series with a data type of DateTime.
• If one or more parts of a date time item are not required or allowed to be unknown, the data series to which the item is mapped must have a type of Text.
• The length of an item mapped to a data series must not be longer than the value set in the DB Format Length custom property of the data series.
• The precision of a float item mapped to a float data series must not be greater than the value set in the DB Format Float Precision custom property of the data series.
• If a float item is mapped to an integer data series, the precision must be 0.

Date part and split date

If any item is mapped to a data series with the split date option, all items mapped to the data series must use the split date option.

Enrollment panel

A data mapping can have only one enrollment panel.

Non-patient data panel

The data series in a non-patient data panel cannot have any mapped items.

Other validation for CIS data mappings

• The following CIS custom data series properties must be mutually exclusive:
  • Checklist and CIS Codelist.
  • Derived and Item Required.
• RefNames of data sets and data series that are used for:
  • CIS data mappings must not be longer than 20 characters.
  • CDD data mappings must not be longer than 25 characters.
• Aliases for data sets and data series must not be longer than 20 characters.
• RefNames and aliases for data sets must be unique within a data mapping, and RefNames and aliases for data series must be unique within a data set. Checking for RefName and alias uniqueness is case insensitive; for example, the names BP and bp are considered identical.
• The RefName and alias of a custom data dimension that is used as a subset key must not be the same as the RefName or alias of any data series in the data dimension.
• If the value of the Is Key custom property of a data series is True, the value of the Item Required custom property must also be True.
• If you do not create mappings for a CIS enrollment panel, the Central Designer application creates a an enrollment panel from the items in the special screening and enrollment forms. The RefNames of the special screening and enrollment items used to create the enrollment panel must not be longer than 20 characters.
• If a data set is marked as an enrollment or non-patient data panel, the value of the Detail Key Item, Detail Panel, Master Item, and Master Panel custom properties of all data series in the data set must not be True.

Data sets and data series

Custom dimensions and custom dimension labels do not reference deleted codelists or codelist items.