Oracle Clinical One Analytics

Duplicate records created for a site, depot, or lab

Now, when you create or modify a site, depot or lab facility in the Oracle Clinical One Platform, data related to these facilities is provided to Data Hub with a unique identifier. Previously, creating or updating sites in the Oracle Clinical One Platform would generate duplicate active records due to the lack of a unique identifier for a lab facility. This impacted the integration of downstream services such as Oracle Life Sciences Data Management Workbench.

(Issue 37111618)

Two active records for the same inventory ID in the Blinded and Unblinded Kits datasets

There are no longer duplicate rows for the same inventory ID in the Blinded and Unblinded Kits datasets in Oracle Clinical One Analytics. Previously, two different records were incorrectly created at the same time for a new inventory ID: one for the CREATED action and another one for the REMOVED action. Both records were displayed in the Oracle Clinical One Analytics tables, creating a data mismatch.

Due to a primary key violation, this issue was also causing a data load failure in Oracle DMW which is now corrected along with this fixed issue.

(Issue 36999348)

Two active records for the same site after a change of primary address

Oracle Clinical One Analytics datasets now display the correct new primary address for a site and no duplicate records are observed. Previously, with the introduction of multiple primary addresses for sites, a duplicate entry for the same site's address was created when there was a change of primary address. This was particularly observed for sites created before Oracle Clinical One Platform 23.3 as part of a backward compatibility issue.

Due to a primary key violation, this issue was also causing a data load failure in Oracle DMW which is now corrected along with this fixed issue.

(Issue 36958248)

Oracle Clinical One Analytics data refresh event completes with errors (former known issue)

The Oracle Clinical One Analytics data refresh event, to synchronize data entered in Oracle Clinical One Platform with Oracle Clinical One Analytics tables, now completes successfully. This makes all kit dispensation details to be available and accurate in Oracle Clinical One Analytics datasets.

All previously impacted data elements now populate correctly.

Impacted dataset	Impatcted data elements
Unblinded Subject Event dataset	INSTANCE_NUMBER INVENTORY_ID KIT_NUMBER KIT_TYPE_SRC_ID INVENTORY_STATUS_ID INVENTORY_STATUS DISPENSATION_DATE MHEALTH_DEVICE_ID DOSAGE BAR_CODE DISPENSATION_CONFIRMED MEASUREMENT FREQUENCY RETURNED_UNITS MISSING_UNITS CONSERVED KIT_DESCRIPTION
Blinded Subject Event dataset	KIT_NUMBERS
Unblinded Kits dataset	DISPENSATION_DATE DOSAGE MEASUREMENT FREQUENCY CONSERVED QUANTITY INSTANCE_NUMBER
Blinded Kits dataset	DISPENSATION_DATE DOSAGE MEASUREMENT FREQUENCY CONSERVED QUANTITY INSTANCE_NUMBER

Retracted recommended action: Verify the information of the impacted data elements in your study in Oracle Clinical One Platform.

(Issue 36249843)

The Blinded Kits dataset does not include blinded kit records (former known issue)

The Blinded Kits dataset, used to analyze and visualize supply data, now includes details for both blinded and unblinded kit types. Previously, this dataset only displayed data for unblinded kits.

(Issue 36131614)