Workflow and supported events

1. Events completed in the external ObvioHealth system trigger calls to a REST API-enabled web service.
   The supported events are:

   Note:

   Events depend on the source system design. The integration needs to be configured based on how the source system bundles and sends the data.

   • Screen a subject
   • Insert, update, and delete data in static-repeating, flat, and two-section forms; this includes forms within a rescreening visit.
     • Supported question types include text, date, check box (single and multi-select), radio control, and dropdown.
   • Update the status of a visit
   • Update visit date (all visit types are supported).
     • For cycle visits, the visit date should not be used as a repeat key if updates are expected.
   • Visit completion
   • Create Adverse Event entries
2. The web service validates the data, then triggers the parent integration (a specific integration configuration), which controls the entire integration process.
3. The integration reads the data and then groups it by subject and visits, allowing the integration to process data for multiple subjects in parallel.
4. Subject data is transformed per the Oracle Clinical One Platform study design.
5. Clinical One API calls are made to update the subject status and insert or update the data in the respective visit, form, and question.