Oracle Clinical One Platform now integrates with Fisher Clinical Services

Last year, we automated some steps in the life cycle of a shipment in Oracle Clinical One Platform for users who distributed investigational products using Almac. This year, we're rolling out the same integration for Fisher Clinical Services, another global depot network. As for the benefits, this is yet another time-saving feature for clinical supply managers and depot users.

Remember that this integration can be used for all types of shipments: the initial shipment to a site, a resupply shipment that is generated automatically when resupply runs, and a manual shipment.

Sponsors: How can I connect my Oracle Clinical One Platform study with Fisher Clinical Services?

Reach out to your Oracle Project Manager if you're interested in setting up this shipment workflow. The Oracle Services team will define the integration between your Oracle Clinical One Platform study and Fisher Clinical Services.

Clinical supply managers and depot users: How can automation help me?

You'll see these changes in Oracle Clinical One Platform only after the Oracle Services team sets up a study so that it's connected with the Fisher Clinical Services network. These changes don't affect site users.

Want to know more about how this workflow affects your studies? See the table below.

Activity in the study	Activity that is now automated in Oracle Clinical One Platform
A new shipment is raised.	The status of the shipment changes to Pending.
The depot fulfills a shipment.	The ship date is set, and the status of the shipment changes to In Transit.

Note:

If you need to update a shipment after the shipment request has been sent to the depot, you must contact Fisher Clinical Services directly. If you make any updates to shipments from within Oracle Clinical One Platform, the changes won't be sent to the depot.