Oracle Clinical One Analytics
| Fixed issue | Description |
|---|---|
| 39469136 |
Future visits are consistent with visit status Now, projected visit processing correctly reports failures when a projected visit update cannot be completed. Failed updates can be retried, helping keep projected visit information accurate and consistent. Note: This fix does not affect existing study data. Your Oracle point of contact will reach out to you if your existing data has been impacted. |
| 39415374 |
Repeating form records record the correct data Now, repeating form sign and verify records capture the correct repeat context when form associations are added, ensuring Subject Item SVFL and data in Oracle Clinical One Analytics display the full audit history for affected repeating records. Note: This fix does not affect existing study data. Your Oracle point of contact will reach out to you if your existing data has been impacted. |
| 39682866 |
Performance Improvement for Subject Form Item and Subject Item SVFL Datasets Now, the Subject Form Item and Subject Item SVFL datasets load and return data more reliably, with significantly improved performance for large studies. For performance-impacted reports, add the newly introduced Study_Wid column in report filter, save the report, and when it is rerun, be sure the Study_Wid value is selected to benefit from the improved query performance and expected dataset results. |
| 39189816 |
New data element with correct spelling PRECISION_FOR_EACH_DOSE is added in the Kits and Randomization Design dataset Now, the Calculated Dose folder in the Kits and Randomization Design dataset includes a new data element for PRECISION_FOR_EACH_DOSE with correct spelling. Another data element already existed for this data point, but its name is misspelled as PERCISION_FOR_EACH_DOSE. The existing misspelled data element is now obsolete, but still available as part of the dataset for backward compatibility. This is to avoid impacting on existing integrations, if any downstream systems are currently using it. Both, the existing misspelled data element and the new one with correct spelling, display the same value. Note: Systems consuming the Kits and Randomization Dataset API will require a full refresh before they can use the new column. |
| 38644641 |
Data Collection Dataset API responds in an adequate amount of time Now, the Data Collection Dataset API for incremental load scenarios takes an adequate time to complete, ensuring overall API stability. Previously, queries using DH_TIMESTAMP filters timed out and could not complete successfully within the expected response time. |
| 38903987 |
Queries Dataset API populates select fields correctly in Oracle Clinical one Analytics Now, the Queries Dataset API correctly populates the CURRENT_STUDY_ROLE_NAME, CURRENT_STUDY_ROLE_ID, and CURRENT_STUDY_ROLE fields in Oracle Clinical One Analytics, ensuring consistency in study role information. Note: Systems using the Queries dataset API will refresh all queries. |
| 38633742 |
Subject Forms SVFL datasets return only a single active record for lock actions Now, the Subject Form SVFL dataset now correctly includes active records for sign, verify, freeze and lock actions at the form level. Previously, section level records duplicated the form level information for 2-section forms and lab forms. Excluding the section level information from the Subject Form SVFL dataset views and API calls ensures consistent SVFL data is available for downstream integrations and reporting workflows. Note: Reporting on this data in Oracle Clinical One Analytics; this will now include a reduced number of records due to the exclusion of the duplicate section level record(s). Integrating this data 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. |
| 39200955 |
Subject Forms dataset displays the correct form title Now, the Subject Forms dataset correctly displays the Study-Version-Specific form title as FORM_NAME for triggered dynamic forms, while form names in Oracle Clinical One Analytics datasets and related reporting views are now aligned with the configured form titles, instead of internal reference names. Note: Systems using the Subject Forms dataset API will have the data for all triggered dynamic forms refreshed. |
| 38784240 |
SAS variables and column names are validated and mapped correctly in Oracle Clinical One Analytics Now, Oracle Clinical One Analytics validates SAS variables and column names using a case-insensitive and standardized uppercase format, preventing duplicate mapping conflicts during study version updates and ensuring successful incremental load processing. |
| 39031900 |
Accurate dataset API descriptions are provided in Oracle Clinical One Analytics Now, dataset API descriptions in Oracle Clinical One Analytics include standardized recommendations for order-by columns across supported datasets, providing clear guidance for consistent sorting and reliable dataset retrieval behavior. |
Parent topic: Fixed issues in 26.2