Release impact on other applications

This document describes the known impact and limitations that new features introduced in Clinical One Cloud Service 26.2 may have on downstream systems, specifically Oracle Clinical One Analytics, Clinical One Digital Gateway integrations, Oracle CRF Submit, Oracle Life Sciences Data Management Workbench, and Oracle Central Coding.

For additional information about the features in this release and the potential impact on your studies, Download the Release Implementation Assessment document.

Oracle Clinical One Analytics and Data Hub

The features introduced with this Clinical One Cloud Service release do not impact Oracle Clinical One Analytics and Data Hub.

Clinical One Digital Gateway configured integrations

Release feature Impact on Clinical One Digital Gateway
Update system assigned dates for Screening and Enrollment
  • Edits to the screening date for subjects in the Screened status are not reflected in the Encounter Date field in CTMS. Instead, the updated screening date is reflected only in the Status Date field. This behavior occurs because CTMS does not currently support updates to the Encounter Date after initial integrations.

    Note: To enable integration of the updated screening date with the Status Date field in CTMS, a template update is required. Reach out to your Oracle point of contact to implement the updated template.

  • Edits to the screening date for subjects whose status has progressed beyond Screened are not reflected in the Encounter Date field in CTMS.

For more information, see the Screening event in Subject Visit (SV) Integration.

Undo a subject's enrollment
  • Inbound status change updates related to undo enrollment events are not supported for the Multi-IWR integration with Clinical One Cloud Service.

Edit the shipment Received On date The Received Date for shipments will not be changed in SAP Supply Management Systems and SmartSupplies PMD integrations.

Oracle Life Sciences Data Management Workbench (DMW)

New Data Hub views are created to support the following features, introduced with this Clinical One Cloud Service release, but they will be available in Oracle DMW as part of a future release:

Oracle CRF Submit

The features introduced with this Clinical One Cloud Service release do not impact Oracle CRF Submit.

Oracle Central Coding

Release feature Impact on Oracle Central Coding
Undo a subject's enrollment If the setting for Do Not Code screen fail data is enabled, any data that was coded or in progress while the subject was enrolled is not impacted, but no further data is sent when enrollment is undone and the subject is at Screened or Screen Failed status.