Dispensation rollback events are supported by outbound integrations

Select outbound integrations support dispensation rollback event workflows and integrate rollback updates with downstream systems.

When a site user performs a dispensation rollback in Clinical One Cloud Service, the Clinical One Cloud Service to Oracle InForm, Outbound subject data, and Oracle Siebel CTMS Subject Visit (SV) integrations transmit rollback event details to downstream systems to preserve an accurate audit history. Subsequent dispensing activity after a rollback integrates with downstream systems as expected.

Note:

For more information about dispensation rollbacks, see Define dispensation rollback.

Downstream systems reflect the rollback by clearing the dispensation details for the subject. The following table describes how each supported integration reflects the rollback.

For information about the following integrations, see the Digital Gateway User Guide after the assessment environment upgrade.

Table 1-1 Integration specific details

Integration Enhancement details
Clinical One Cloud Service to Oracle InForm
  • If a repeating form is used in Oracle InForm, the initial row or record is not updated. Instead, the integration creates an additional row or record to display the dispensation rollback details, which can include the kit number and the rollback date.

    Note: Integration configuration determines which data is integrated with Oracle InForm.

  • To support this feature, you must adopt a new integration template. Reach out to your Oracle point of contact to request the update.
Outbound subject data
  • For non-serialized kits: If a repeating form is used in the downstream system, the initial row or record is not updated. Instead, the integration creates an additional row or record to display the dispensation rollback details, which include the kit number and the rollback date.
  • For serialized kits: The initial row or record is crossed out, and the rollback reason integrates with the custom text defined in the integration template.
  • To support this feature, you must adopt a new integration template. Reach out to your Oracle point of contact to request the update.
Oracle Siebel CTMS Subject Visit (SV) integration
  • The visit status Complete is reverted to Incomplete in CTMS, as the result of a dispensation rollback event.
  • Subsequent dispensation events that occur after rollback, update the status back to Complete.
  • Configuration changes are not required to support this feature.

Already using one of the integrations with a live study?

Existing Clinical One Cloud Service to Oracle InForm and Outbound Subject Data integrations can be updated to support dispensation rollback events. The updates apply to future rollback events only.