Workflow for an integration with Almac Global Depot Network

This workflow applies to shipments when you use an integration with Almac Global Depot Network. It applies to all types of shipments, including the initial shipment to a site, a resupply shipment that is generated automatically when a 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 the organization managing the depot directly. If you make any updates to shipments from within Oracle Clinical One Platform, the changes won't be sent to the depots.

Workflow for a shipment when you use an integration with Almac for shipments

1. When a new shipment is raised, the status of the shipment changes to Pending. This activity is automated.
2. When the shipment request is sent to the depot, the status of the shipment changes to one of the following:
   • Confirmed, if the depot received the request.
   • Invalid, if an issue occurred with the request.

   Both status changes are automated.

3. The depot adds a ship date and tracking number to the shipment, and the status of the shipment changes to In Transit. The setting of the ship date, tracking number, and the status change are all automated.
   For an invalid shipment, a clinical supply manager should cancel the shipment and do one of the following:

   • Allow the resupply process to create a new shipment the next time inventory runs.
   • Create a new manual shipment.
4. A site marks the shipment as received, changing its status to Received.

Prerequisites for sending the depot order form to Almac-managed depot facilities

To make sure depot users at an Almac-managed depot facility get this email notification in their inbox, in Oracle Clinical One Platform, on the Depots tab, check that the Almac-managed depots are correctly defined and their Depot IDs match the exact names of the depot facilities.