Understand options to construct ODM

The external IWR system will make Rest API POST calls to ib-ext-svc with a request body. The request body is expected to be data wrapped in an <IRTData> element, in the ODM XML format.

An <IRTData> element is sent as the input data in the integration request. Each consists of a <ClinincalData> element, including the information to be mapped, and an <EventType> element that defines what kind of data is being sent.
  • The event type allows integration to know how the corresponding data is to be processed according to the integration configuration.
  • The <ClinicalData> element includes the ODM XML subject data and can consist of multiple <SubjectData> nodes.
You must construct your ODM according to your integration configuration, the event type and the clinical data you want to map. Additionally, each external IWR system can choose to fit one of two different patterns to map IRTData into Oracle Clinical One Platform:
REFNAME mapping GUID mapping
  • The external IWR system sends OIDs from the source system.
  • The OIDs are sent as refnames.
  • You have two options when using Oracle Clinical One Platform study refnames in the payload:
    • Option #1: The integration looks into the integration template and uses the refnames to locate the question, then imports the data.

      Note: To use this approach, an Oracle Services Consultant must first map the source values to the target refnames in the integration template.

    • Option #2: The integration looks directly into the Oracle Clinical One Platform design service, using the refnames to locate the question, then imports the data.
  • You can also configure acceptable data transformations.
  • Keys for repeating visits and forms can be used from the source or can be configured.

For more information see Construct ODM using REFNAME mapping.

  • The external IWR system configures source-target static mappings on their end.
  • OIDs are sent as Clinical One GUIDs.
  • Ownership of mappings and data transformations remain with the external IWR system.
  • Repeat keys and item values will be sent in target format. OIDs, repeat keys and items values will be used as-is.

For more information see Construct ODM using GUID mapping.

For more information on IRTData payload types and mapping examples see IRTData payload reference.