Oracle Clinical One Analytics

Fixed issue Fixed in Description

39980187

26.3.0.1

Improved query execution performance and data availability during the ETL IL process

Indexes were included in specific tables to improve the query execution performance of the VW_SIL_DH_SDV_SELECTION_CUR view during the ETL IL process. This fix represents a significant improvement on downstream data availability for large data volumes.

38991782

26.3.0.1

Dynamic forms are now included in the Subject Forms dataset as scheduled only after being triggered

When a parent question is configured with an action rule that can trigger multiple dynamic forms, Data Hub will now display those dynamic forms only after the parent question response triggers the applicable forms. Before the parent question triggers the action rule, the associated dynamic forms will no longer be displayed as SCHEDULED in Data Hub.

All existing records affected by this behavior have been identified and corrected. A full data refresh is not required.

Impact on Oracle Clinical One Analytics

Reporting in Oracle Clinical One Analytics may now include fewer records because dynamic forms that have not been triggered by the parent question will be excluded. This ensures that reports reflect only dynamic forms that were actually triggered based on the configured action rule.

Impact on API integrations

Dynamic forms that have not been triggered will no longer be available through API calls. As a result, if your integration previously retrieved records for dynamic forms that had not been triggered, those records will not receive further updates through the API. For a complete list of records impacted by this change, please contact your Oracle point of contact.

39891097

26.3.0.1

Duplicate records in the Subject Form Items and Subject Item SVFL datasets are now corrected

Duplicate records in the Subject Form Items and Subject Item SVFL datasets are now corrected. Previously, starting with release 26.2, certain Data Hub dataset extracts returned duplicate records when a user's study role was changed after the user had created or modified data in the study.

This issue only occurred when the dataset request included one or more of the following columns:
  • CURRENT_STUDY_ROLE_ID
  • CURRENT_STUDY_ROLE_WID
  • CURRENT_STUDY_ROLE_NAME
If none of these columns are requested, the dataset extract was not affected.

All the existing affected records have been identified and corrected. A full data refresh is not required.

Impact on Oracle Clinical One Analytics

For reports including this data in Oracle Clinical One Analytics, these will now include a reduced number of records due to the exclusion of the duplicate data.

Impact on API integrations

When this data is integrated via APIs, the duplicate records will not be available through API calls and therefore any previously integrated duplicate records will not be updated. For a full list of impacted records please reach out to your Oracle point of contact.

39436072

39459009

26.3.0.1

Form status is managed correctly after subject withdrawal, completion or screen failure

After a subject is withdrawn, completed, or screen-failed, the visits with New status and its associated forms with no data are now properly version-ended in Oracle Clinical One Analytics. With this, these forms no longer appear as New or Missing.

All previously affected records have been identified and corrected. A full data refresh is not required.

37002866

26.3.0.1

Non-repeating lab forms populate with the correct signed, freeze and verified statuses in the Subject Forms dataset

The flat section of non-repeating lab forms now populates with the correct signed, freeze, and verified actions statuses in the Subject Forms dataset. Previously, the signed, freeze and verified statuses were only reflecting properly for the table section of the lab form, while the flat section was incorrectly null.

All the existing affected records have been identified and corrected. A full data refresh is not required.

39737687

26.3.0.1

Query data is properly hidden in Oracle Clinical One Analytics for items with data classifications

When queries are opened on empty questions with data classifications, the data classification logic is now properly applied to show or hide item data and queries respectively in Oracle Clinical One Analytics. Previously, the flag used to hide data according to the data classifications applied was not being properly managed in queries created before the form-item data existed.

All the existing affected records have been identified and corrected. A full data refresh is not required.

39535877 26.3

SAS_LABEL and ITEM_NAME values are populated correctly after ASV is applied

Now, when an item added in an earlier study version has Advanced Study Versioning (ASV) applied in a subsequent version, Clinical One Cloud Service populates the appropriate SAS_LABEL and ITEM_NAME values in the Study Design, Study Codelists, Subject Form Items, Subject Form Items SVFL, and Queries datasets.

Note: This fix also updates data for records where these values were previously NULL.

39236748

26.3

Events and Forms datasets reflect Undo Add subject records correctly

Now, when Undo Add is performed on a subject, the Events and Forms datasets accurately reflect the records created and removed as part of this action.

For the first visit with a status of NEW, the Events dataset includes both CREATED and REMOVED version-ended records. For scheduled forms associated with the first visit, the Forms dataset includes both CREATED and REMOVED version-ended records.

Note: This fix also updates data in the Events and Forms dataset APIs for subjects where Undo Add was performed previously.

39761725

26.3

Study Code List dataset returns unique code list records

Now, the Study Code List dataset includes scheduled-from visit information when grouping code list records and uses a fallback value when CODE_VALUE_ID is not available. This prevents duplicate records and NULL CODE_VALUE_ID values in the dataset.

Note: Systems consuming the Study Code List dataset API must use the new V4 version and perform a full refresh before using the newly introduced columns.