Unexpected form items are now displayed

All form data is now correctly displayed in Oracle Clinical One Analytics and Oracle Life Sciences Data Management Workbench (DMW). Previously, some form items appeared incorrectly in both platforms after updating the Oracle Clinical One Analytics system. This issue occurred because some study version changes were not properly filtered out before being shared with these platforms.

From now on, only the finalized changes that are part of a study version are displayed as expected.

(Issue 37925063)

Differences in metadata prevent data from being integrated

You can now integrate study data from the Oracle Clinical One Platform to Oracle DMW. Previously, issues with calculations identifying clinical tables and items within Oracle Clinical One Platform caused some items to be mislabeled, leading to integration problems.

(Issue 37924980)

Some form items display multiple columns with different titles in Oracle DMW

All data related to form items in your Oracle Clinical One Platform is now displayed correctly in Oracle DMW. If available, the SAS Variable is displayed. If not, the Reference Code is displayed, but not both. Previously, you may have noticed that some form items had two columns listed – one was named after the form item's SAS Variable, while the other was named after the form item's Reference Code.

(Issue 37925071)

ROW_ID data element displays different data

Oracle Clinical One Platform study data that's integrated with Oracle DMW displays the correct ROW_ID elements in Oracle DMW. Previously, there were discrepancies between these IDs despite no changes having been made in the study before integrating its data into Oracle DMW.

(Issue 37924902)

COUNTRY_NAME and INVESTIGATOR data elements aren't displayed in datasets

Now, you can properly view data being populated for the COUNTRY_NAME and INVESTIGATOR data elements whenever you include them in your datasets or dashboards. Previously, these data elements weren't displaying the expected data.

(Issue 37756629)

Not-yet-triggered dynamic forms appear in Oracle Clinical One Analytics datasets (former Known Issue)

Only dynamic forms that are triggered are now included in the Subject Forms dataset, as expected. Previously, dynamic forms that have not been triggered were incorrectly included in the dataset. These forms were categorized as missing and assigned a status of Scheduled, even though they should not have been present. This issue occurred when a single show-form rule was configured to trigger multiple forms, leading to the unintended inclusion of untriggered forms in the dataset.

Retracted recommended action: Create one show form rule per form.

(Issue 36976923)