Integrations

Missing start time creates duplicate event processing in CTMS

Now, the system fetches only relevant data for the current specified time window specified in the integration payload for that specific integration run. Previously, because the start time was missing from the payload, data was fetched from Oracle Clinical One Platform to send to CTMS from an overly broad time range, which led to duplicate event processing and Bad Gateway Errors.

(Issue 37890401 and 38101163)

Form fields create a status error in CTMS

Now, when integrating to CTMS, Informed Consent form date fields populate correctly. Previously, when an Informed Consent date was updated for a subject, the field would not integrate properly to CTMS and generated a system error message: Status Date cannot be Null.

(Issue 37734776 and 37316545)

The Oracle Clinical One Digital Gateway User Interface (UI) doesn’t consistently render after login

Now, the Oracle Clinical One Digital Gateway consistently renders in the browser after entering valid login credentials when a study is undergoing maintenance. Previously, the home page loaded successfully for some users after logging in, but for others, the UI took longer than expected to load.

This issue only happened if a study was in maintenance mode. Performance for logging into Oracle Clinical One Digital Gateway went back to normal once the study maintenance period ended.

(Issue 38224043)

Newly created study versions in CTMS lack previously recorded data

Now, newly added study versions are integrated properly. Previously, when a new study version was added in CTMS during an active integration job, the system implemented the study too soon, causing the study to start from the wrong time window and lack historical data.

(Issue 37384182 )