Details about lab data, repeating form data, and data validation

Learn how EHR data import works when importing lab results and repeating form data, and how precision is handled.

Details for importing lab data

You have two options when importing lab results:
  • You can select one or more records, for example, White Blood Cell Count and Sodium, which results in the importation of all associated data points, like collection date, result, and units.
  • You can choose to import all records in a column by selecting the checkbox to the left of the date at the top of a column.

The data import compares the EHR value, for example, White Blood Cell Count, to the list on the form to determine which row the data is imported to.

Data import is unsuccessful if the EHR lab test name does not correspond to one of the lab test names on the form.

Note:

If the form-level setting Add Additional Rows is enabled, EHR lab tests that don't match one of the values on the form are imported at the end of the lab form.

Details for importing repeating form data

Similar to lab forms, when you import data for a repeating form, you select a record to import and not specific data points.
  • Importing the same record after clearing or updating a data point only imports the cleared or updated data. The Answer & Visit History side panel accurately reflects this.
  • After import, deleting an entire row removes both the data and the row from the study. Then, if you import the same record:
    • The deleted row data is no longer present under the Current Value column when the EHR data is presented to you.
    • The import is inserted as a new row on the form, which is standard functionality. The row has a fresh audit entry in the Answer & Visit History side panel and has no association with the deleted row.

Data validation and conversion details

Review the following details to better understand when and why data is converted and how to identify this in the Answer & Visit side panel.
  • Handling units
    To maintain the Oracle Clinical One Platform study design, we convert some EHR units to match the study's defined units. This includes length units (for height and head circumference), body weight units, and body temperature units.
    • For example, if the study design only allows temperatures to be entered in degrees Celsius, an EHR value collected in degrees Fahrenheit is converted on import.
    • The Answer & Visit History side panel captures the action and includes the date and time, as well as the source and converted units.
  • Handling precision
    For numbers, the import maintains the precision as defined in the EHR system.
    • If the precision defined in the study is less than the EHR value presented—for example, if the EHR value is 96.574 but the question precision is 0.00—the data is imported, and a red box appears around the question, which indicates that a validation error is present.

      Note:

      Users assigned to a study role that includes the Manually Update EHR Imported Data permission can update the data if needed.
    • If the precision defined in the study is greater than the EHR value, the system adds trailing zeros to maintain the study's design. For instance, if the study design precision is 0.000 and the EHR value is 6.54, the system converts the value to 6.540.
    • The Answer & Visit History side panel captures these actions and includes the date and time, along with the source and converted values.
  • Handling code lists
    • If the EHR value does not match one of the options in the EHR code list, data is not imported for that question, and nothing is tracked in the Answer & Visit side panel.
  • Handling date time
    • EHR date time values are converted to match the format defined for the question in the study, for example, DD-MON-YYYY.
    • Partial dates are allowed when the question setting Partial Date Allowed is enabled. If the EHR date time value is a partial value and the setting is not enabled, the partial value is not displayed for import selection.

Parent topic: Import Electronic Health Record (EHR) data