Integrations

Fixed issue	Description
39672800	CTMS integrations and dispensation workflows function reliably Now, site API responses consistently return the correct site and study information for all request types, improving the reliability of CTMS integrations and dispensation workflows and ensuring visit status updates and study version information are processed correctly.
39672888	CTMS Subject Visit and Visit Schedule integrations process correctly Now, CTMS Subject Visit and Visit Schedule integrations correctly retrieve the site study version during processing, ensuring visit details are resolved successfully, and improving the reliability of Clinical One Cloud Service and CTMS synchronization following study version updates.
39695264	CTMS site integrations process concurrent site updates reliably Now, CTMS site integrations handle concurrent site updates more reliably, preventing duplicate site property records during simultaneous update requests, ultimately improving the stability of site synchronization and reducing integration failures caused by concurrent processing.
39666350	Shipment integrations add kits to pooled shipments reliably Now, shipment integrations reliably add kits to pooled shipments without returning errors during concurrent processing, improving shipment assignment stability and helping ensure kits are added successfully in support shipment workflows.
39133220	User integrations support user assignment correctly Now, user integrations correctly support assigning users to all sites or all depots by specifying ALL or ALL SITES (and ALL DEPOTS) in the integration file. These values are processed consistently, allowing users to be associated with all applicable sites or depots without requiring individual entries.
39293196	Clearing codes in Oracle Central Coding clears coding targets in Clinical One Cloud Service Now, when an Oracle Central Coding user clears codes by using Clear Code or Clear and Propagate, Clinical One Cloud Service clears the associated coding targets. Currently, the Reason for Change field for each cleared coding target is populated with Answer Removed instead of the reason selected in Oracle Central Coding. 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.
39650842 & 39650623	The Stock Report integration now establishes lot-to-depot associations Note: This applies only to studies that use pooled supplies. Now, the inbound Stock Report integration processes the lot-to-depot details included in the stock file. As a result, Clinical One Cloud Service establishes both lot-to-country and lot-to-depot associations, allowing shipment requests to be fulfilled from the correct depot. Previously, the integration processed only the lot-to-country details, which meant that Clinical One Cloud Service established only lot-to-country associations. Without the lot-to-depot association, shipment requests were fulfilled from the primary depot for the country rather than the depot associated with the lot. After the upgrade: For existing studies, rerun the daily stock file after the upgrade to establish lot-to-depot associations for existing inventory. Until the stock file has been processed, existing shipment requests continue to use the previous lot-to-country associations.
39189085	Site contact details synchronize properly Now, updates to site telephone numbers from CTMS integrations synchronize correctly to Clinical One Cloud Service through Clinical One Digital Gateway, while newly added or updated site contact details, including phone numbers, are properly reflected in Clinical One Cloud Service after integration updates.