Workflow for an integration with Fisher Clinical Services

This workflow applies to shipments when you use an integration with Fisher Clinical Services . It applies to all types of shipments, including the initial shipment to a site, a resupply shipment that is generated automatically when resupply runs, and a manual shipment.

Want details about the workflow when you don't use an integration for shipments?

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 depots.

Prerequisites for clinical supply managers

For shipments sent through this integration, only IDs that contain numbers are accepted. To make sure you use the right Shipment ID Prefix, go to the Supply Settings tab. In the Shipment Settings section, either select Use Depot ID or None. If a depot ID contains leading zeros, they do not appear in the Shipment Request file as part of the Shipment ID format for Fisher Clinical Services.

Workflow for a shipment when you use an integration with Fisher Clinical Services for shipments

1. When a new shipment is raised, the status of the shipment changes to Pending. This activity is automated.
2. The depot adds a ship date to the shipment, and the status of the shipment changes to In Transit. The setting of the ship date and the status change are both automated.
3. A site receives the shipment and marks the shipment as received, changing its status to Received.