Special considerations
- Importing new subject data—You must use the MedML file option to import data for a subject who has not gone through the screening and enrollment process.
You cannot use the data and map file option to import screening and enrollment data.
Note: You cannot import new data to a form with a Frozen or Locked status in the InForm application.
- Importing comments—To import form-level comments, you must use the MedML file option.
To import item-level comments, you must use either the data and map file option or the MedML file option.
- Importing calculated controls—When you import calculated controls, the data type definition of the import field must be Text control. If Integer or Floating number is used, the match is not recognized and data is not updated. Instead, the data is added as a new row.
- Importing units—When you submit unit data, the units must be associated with the previous field in the data and map file.
- Importing unscheduled visit data—To import data to unscheduled visits, use either the MedML file or data and map file option.
- Importing on multiple servers—If your study is running on multiple servers, run the InForm Data Import utility on only one server at a time to eliminate the possibility of importing duplicate data.
- Editing repeating forms—To create or edit repeating form instances, you must create the map file using a text editor, not the InForm Data Import utility user interface. Follow these guidelines for editing a map file:
- Use NOFORMNEW in the first line of the map file to instruct the InForm Data Import utility not to create a new repeating form instance.
- Use the new !formmatch! element in the map file to specify an item (not within an itemset) that will be compared to other repeating form instances.
You can use multiple !formmatch! elements. If all such elements match some existing repeating form instance, then that form instance will be updated. If there is no match (or no !formmatch! element) then a new repeating form instance will be created, as illustrated in the following sample code:
FORMNOVISITNEWNOFORMNEW|
!cd!Site|
!cd!Patient|
!visitmatch!0.UnschVisit.DOV.DOV.0.DOV.DOV!dtdatetime!|
!formmatch!0.UnschVisit.HH.DH.0.DURATIONGROUP.DURTAIONGROUP.YRDURATION!dtstring!|
!formmatch!0.UnschVisit.HH.DH.0.DURATIONGROUP.DURTAIONGROUP.MTHDURATION!dtstring!|
0.UnschVisit.HH.DH.0.previousgroup.previousgroup!DTSTRING!| - When you create a repeating form, include regular items instead of itemsets to uniquely identify the form. If you cannot uniquely identify the form, then you can enter data only one time to the form, and the next data entry will go to a new form instance.
- Importing files that contain non-alphanumeric characters—All import files that include non-alphanumeric characters, such as Japanese characters, must be in Unicode format. All other formats will be read as ASCII and may yield misleading error messages.
- Importing data to an Add Entry itemset—You can add rows to an Add Entry itemset, and you can add or modify data in an existing Add Entry itemset row.
- To add a row to an Add Entry itemset, use the PATIENTDATA tag. You can add one row at a time to the itemset.
For more information, see Adding new clinical data.
- To add or modify data for an item in an Add Entry itemset, use the EDITPATIENTDATA tag.
- You must use the EDITPATIENTDATA tag to add or modify data for an item in an Add Entry itemset, regardless of whether the item previously contained data.
- When you use the EDITPATIENTDATA tag, you cannot use the DATA sub-tag with the ITEMSETINDEX tag to modify itemset data. You must use the ITEMSETINDEX attribute with the EDITPATIENTDATA tag.
For more information, see Updating existing clinical data.
- To add a row to an Add Entry itemset, use the PATIENTDATA tag. You can add one row at a time to the itemset.
- Importing data to a Repeating Data itemset—You can create the rows in the database for a Repeating Data itemset, and you can add or modify data in an existing Repeating Data itemset row.
- To create rows in the database for a Repeating Data itemset, use the PATIENTDATA tag. You can create one or more rows at a time for a Repeating Data itemset.
Note: To create rows in a Repeating Data itemset using the PATIENTDATA tag, you must use the ITEMSETINDEX attribute with the DATA sub-tag.
For more information, see Adding new clinical data.
- To add or modify data for an item in a Repeating Data itemset, use the EDITPATIENTDATA tag.
- You must use the EDITPATIENTDATA tag to add or modify data for an item in a Repeating Data itemset, regardless of whether the item previously contained data.
- When you use the EDITPATIENTDATA tag, you cannot use the DATA sub-tag with the ITEMSETINDEX tag to modify itemset data. You must use the ITEMSETINDEX attribute with the EDITPATIENTDATA tag.
For more information, see Updating existing clinical data.
- Do not use the itemset !match! field in a map file, which is used to match an itemset row, when using the !cd!ItemsetIndex field. The !match! field is generally added manually to a Map file, and does not appear on the Field Definition page of the InForm Data Import utility.
- To create rows in the database for a Repeating Data itemset, use the PATIENTDATA tag. You can create one or more rows at a time for a Repeating Data itemset.
- Deleting and undeleting Add Entry itemsets—To delete or undelete Add Entry itemset data, you must use the MedML file option.
Note: You cannot delete or undelete a Repeating Data itemset.