Pre-General Availability: 2025-07-15

The Multi-IWR integration has been simplified

The way the IWR integration processes subject data sent by an IWR provider has been enhanced, resulting in the removal of unnecessary steps.

Details for integration managers

IWR providers use the Study Design report to obtain the visit, form, and question refnames, which they include in the payload request sent to Oracle Clinical One Platform.

Prior to this enhancement, the IWR provider developed integration code to call an Oracle Clinical One Platform API to retrieve the study design GUIDs for the questions that needed to be integrated, and an Oracle Services Consultant created the refname-to-GUID mappings in the integration configuration file.

Beginning with 25.2, the IWR provider no longer needs to develop integration code, and Oracle Services no longer needs to create mappings. Now, the IWR provider can simply include the refnames (from the Study Design report) in the payload sent to Oracle Clinical One Platform via the API call.

The integration directly links to the Oracle Clinical One Platform Design service and uses the refnames in the payload to find the questions where the data should be imported or updated; no extra integration code or mappings are required.

What do I need to know if I have an existing IWR integration?

There is no need to update existing IWR integrations. They will continue to function as originally configured.

You can find additional information about this feature in the guide of REST API for Clinical One Platform and the Digital Gateway User Guide after the Release Assessment Environment (RAE) upgrade.