Oracle Clinical One Analytics

Site records not properly displayed in datasets (former known issue)

From now on, data related to a site’s start date or end date will be properly reflected in the Oracle Clinical One Analytics application and its datasets.

Retracted workaround: You no longer need to reach out specifically to your Oracle Project Manager to refresh data in the Analytics application. (Issue 33940889)

Audit data is not displayed in Oracle Clinical One Analytics (former known issue)

Now, a subject’s kit data also display audit data, as expected. Here is what you will be able to see when it comes to a subject's kit audit data:
  • For a replaced kit (with a reason of Not dispensed to subject), subject and visit details are also risplayed until the kit is updated as Available in the system. For a new kit, only a subject's details are displayed, without any associated visit details.
  • For a replaced kit (with a reason of Lost/Damaged), subject and visit details are displayed until the kit is updated as Available in the system. For a new kit, only a subject's details are displayed, without any associated visit details.
  • For a reused kit, details of the associated visit before the kit's reuse are displayed. After the kit is reused, the latest visit details are displayed.
  • For a misallocated kit, details of the newly assigned subject are displayed.

Retracted workaround: None. (Issue 33563978)

Shipment records are not properly updated in the Unblinded Kits dataset (former known issue)

Now, when you attempt to include historic records of kit shipment details in your custom report, the data is displayed as expected. Previously, data was not properly updated. For example, if the status of a kit was updated from Pending Destruction to Destroyed, this update was not reflected in your report.

Retracted workaround: None. (Issue 33485267)

Kits’ data is not properly displayed in datasets (former known issue)

Now, in the Unblinded Kits dataset, when you attempt to display a kit with an updated shipment date, you may notice that the element DH_TIMESTAMP is updated, as expected. Previously, this element was not displayed accordingly.

Retracted workaround: None. (Issue 33448065)