Integrations

Oracle Central Coding system timeout when attempting to process duplicate records

Now, duplicate source ID entries are not being entered in the CODING_AUDIT table when a GET request job retry fails. Previously, duplicate entries were made in the CODING_AUDIT table when the Get Request job failed and a retry was attempted. Subsequent GET requests would attempt to process the duplicates resulting in a system timeout. (Issue 34087438)

API endpoints can now be used for adding subjects in a study

For integration managers who use Oracle Clinical One Digital Gateway

Now, the API endpoint typically used to add subjects can be used to add subjects through an integration with Oracle Clinical One Digital Gateway, as expected. This task can be performed even when the corresponding setting is set to No in a study. Previously, when a study manager had configured the study to prevent site users from manually adding subjects (setting the value for Allow Subjects to be Manually Added to No), that study setting would also apply to the API endpoint. This prevented both site users from adding subjects in a study, as well as adding them through an integration. (Issue 34376688)

For API users who only operate in Oracle Clinical One Platform

Now, if you need to add subjects through the APIs, while the Allow Subjects to be Manually Added setting is set to No, you can do so by using the Add transferred subject API endpoint.

This API endpoint does not validate the command of adding subjects against the Allow Subjects to be Manually Added setting, as well as other subject-related settings in Oracle Clinical One Platform. To ensure that no duplicate subject numbers are created in a study, the API endpoint does validate the newly added subject against existing subject numbers.

For specific details related to the API endpoint, see Add a transferred subject.