|
|
|
|
Manual mappings
If you choose, you can create manual data mappings for a trial. (This is not recommended unless you plan to store only a few data values in the Clintrial database, for example, during the testing of a specific portion of a trial design.) A more common strategy is to autogenerate mappings initially and then change them as necessary or create additional manual mappings to accommodate any data access requirements you have that are not met by the autogenerated mapping definitions.
After initially autogenerating mappings for a trial, you must manually update the mappings when you make changes to the trial if you want to capture the new or changed data in the Clintrial database. For example, you must update mappings manually when:
- Refreshing an existing protocol in the CIS library with changes introduced with the InForm Architect application.
- Adding a visit, form, or item to a trial.
- Changing the size of a data item, if you make it larger than originally designed.
- Applying any custom mappings that are required.
Manually mapping items in the InForm Architect application to the corresponding Clintrial item gives you flexibility. For example, in some instances it may be desirable to map two items in an InForm Architect form to the same item in the Clintrial software (mutually exclusive items in a radio group should only require one item). Alternatively, you may want to group clinical data items from one or more forms in an InForm trial into a single Clintrial panel.
