Work with two-section form data in DMW

When you create a two-section form in Clinical One and have it flow from Datahub to DMW, the data is condensed into a single table, viewable in DMW on the listings interface.

Lab and two-section forms can be comprised of a flat section and a repeating section. The flat section of the form has a set number of questions with corresponding answers. The repeating part of the form allows whoever is entering the data to enter multiple instances of the question. For example, a two-section form collecting data about adverse effects to medicine may have a flat section containing questions about the medication name and dosage while the repeating part of the form allows a user to add several different items relating to the symptoms.

Since the data is flattened into a single grid in the listings view, it's important for you to know how to interpret the data correctly, as creating a discrepancy or a validation check using wrong type of form data could cause a discrepancy to end up in an irreversible purgatory between Clinical One and DMW.

Tip:

The NONREPEATING column is a quick way to check whether you're working with flat section data or repeating form data. The flat section form data rows are marked as "Y" in the NONREPEATING column and repeated form data rows are marked as "N".

Guidelines for working with two-section and lab forms

We recommend that you adhere to the following guidelines to ensure clean data and an uninterrupted flow between Clinical One and DMW:

  • To create a discrepancy on a piece of data collected from the flat section of a form, make sure that the discrepancy is created on a row marked with Y in the NONREPEATING column. Flat section data is duplicated to the repeating section rows so it can be easy to create a discrepancy on the wrong record!
  • Make sure you create discrepancies for the repeating form data on the combined record by looking for the N in the NONREPEATING column.
  • Create separate Validation Checks for creating discrepancies on flat section vs. repeating section columns. Make sure to include NONREPEATING = Y/N in the Validation Check criteria accordingly.
  • Take all of the above into consideration when you design transformations or custom joins for downstream data models. For example, if you create a downstream transformation data model which only has combined records (NONREPEATING column is marked as N) but is used to create discrepancies on flat section columns, the discrepancies would be internally linked to the repeating row. If the repeated row is subsequently deleted, the discrepancy would automatically close, even though it was created on the flat section column.

What if I want to create a discrepancy on flat section column data but accidentally select a record in a combined (NONREPATING = N) row?

A discrepancy created on a flat column but in a repeating row will display correctly in the DMW and Clinical One interfaces. However, the discrepancy will be internally linked to the repeating row record. If the repeating row record is deleted in Clinical One, the discrepancy is automatically closed.

What if I want create a discrepancy on data in the repeating column but end up selecting a record in a flat-only (NONREPEATING =Y) row?

A discrepancy created on a repeating column but in a flat-only record will only be visible in DMW. The discrepancy will only appear on the right-hand side panel of Queries listed on the subject visit page in the Clinical One interface.