Mapping Central Designer terms to InForm terms
When you deploy a study created in the Central Designer application to the InForm application, the Central Designer study components and workflow are translated to InForm study components. The conversion to InForm study components is based on both the data definition of each study component and the layout specified for each form or item in the Central Designer application.
Correspondences between Central Designer and InForm study components
Central Designer study component |
Corresponding InForm study component |
Notes |
---|---|---|
Codelist |
Radio, checkbox, or pulldown control |
The following codelist specifications determine how codelist items deploy to the InForm application:
|
Codelist item |
Simple control |
|
Collaboration note |
No corresponding component |
This type of study object is not deployed to the InForm application. |
Data series |
|
|
Data set |
|
The data dimensions of a data set form the key for each row of a CDD table. Data values defined as custom dimensions form pivot columns around which the data in the table is organized. |
Description |
No corresponding component |
Study object descriptions are visible only in a Central Designer annotated study book. |
Form |
Form |
|
|
Alternate form |
|
|
Associated forms |
Two forms defined as repeating and linked with the AssociatedForm property in the Central Designer application deploy as associated forms in the InForm application. |
|
Common form |
A form defined as a common form deploys as a common form. |
|
Date of Visit form |
If you do not include a special Date of Visit item in the study, a default Date of Visit form is deployed to the InForm application. |
|
Dynamic form |
A form for which the precondition is the outcome of a workflow rule or global condition deploys as a dynamic form in the InForm application. |
|
Enrollment form |
If you do not include a special Enrollment form in the study, a default Enrollment form is deployed to the InForm application. |
|
Regulatory report forms and visit report forms |
You can create regulatory report and visit report forms in the NonClinical container in the Project Explorer. If you do not create the forms, default versions are generated and deployed. |
|
Repeating form |
A form defined as repeating in the Central Designer application deploys as a repeating form in the InForm application. |
|
Screening form |
If you do not include a special Screening form, a default Screening form is deployed to the InForm application. |
Global condition |
Rule |
The deployment process treats a global condition as a rule and creates rule attachments, arguments, and dependencies in the InForm application as necessary based on the items referenced in the global condition definition. |
Help text |
CRF Help |
Instructions and Help defined for forms or items in the Central Designer application deploy as CRF Help in the InForm application. Instructions and Help defined for other study objects (for example, study events) in the Central Designer application do not deploy to the InForm application. |
Item |
Item |
Item deployment considerations:
|
|
Date/time control |
Date time items in the Central Designer application become date/time controls in the InForm application. |
|
Group control |
A compound item defined with child items in the Central Designer application deploys in the InForm application as a group control consisting of the child items. |
|
Nested control |
An item in the Central Designer application that is conditional on another item deploys in the InForm application as a nested control within the item on which it is conditional. |
|
Text control |
Text, integer, and float items in the Central Designer application become the appropriate text controls in the InForm application. |
|
Unit |
|
Library |
No corresponding component |
This type of study object is not deployed to the InForm application. |
Library project |
No corresponding component |
This type of study object is not deployed to the InForm application. |
Mapping |
CDD or CIS mapping definition object |
|
Rule |
Rule |
The deployment process creates rule attachments, arguments, and dependencies in the InForm application as necessary based on the items referenced in the rule definition. |
Section |
Section |
|
|
Itemset |
The items in a section defined as repeating in the Central Designer application are grouped into an itemset in the InForm application. |
|
Repeating Data itemset |
The items in a section defined as fixed and repeating in the Central Designer application are grouped into a Repeating Data itemset in the InForm application. |
Short Question |
Itemset column header |
|
Study |
Study |
The study version (VERSIONDESCRIPTION attribute in InForm MedML) is a concatenation of:
|
Study element |
No corresponding component |
This type of study object is not deployed to the InForm application. |
Study event |
Visit |
The Short Title of a study event is used as the visit mnemonic in the InForm application. |
|
Dynamic visit |
A study event for which the precondition is the outcome of a workflow rule or global condition deploys as a dynamic visit in the InForm application. |
|
Enrollment visit |
A special InForm visit that must be included in the Central Designer study design.
|
|
Regulatory report and visit report visits |
The deployment process creates regulatory report and visit report visits. |
|
Repeating visit |
A study event defined as repeating in the Central Designer application deploys as a repeating visit in the InForm application. |
|
Screening visit |
A special InForm visit that must be included in the Central Designer study design.
The screening visit must be the first visit in the workflow and the enrollment visit must be second. |
Study project |
No corresponding component |
This type of study object is not deployed to the InForm application. |
Task |
No corresponding component |
This type of study object is not deployed to the InForm application. |
Template |
No corresponding component |
This type of study object is not deployed to the InForm application. |
Type |
No corresponding component |
This type of study object is not deployed to the InForm application. |
No corresponding component |
Calculated control |
You cannot create calculated controls in the Central Designer application. You can create a read-only control that serves the same purpose as a calculated control in that it uses a rule to fill in data. |
Note: Components in MedML are named based on the RefNames of study objects in the Central Designer application, with the following two exceptions:
- PFElements. The RefName from the codelist item is concatenated with an underscore and a 40-character identifier that the application creates using the RefName, code, and translations of the codelist label. If you modify the RefName, code, or codelist label, the application creates a new PFElement.
- Group controls are prefaced with "GC_" only when multiple items are conditional on the same item.