Epic pharmacy Proof of Delivery with SuiteFleet

1. Start with the Epic pharmacy delivery request

Open the pharmacy delivery request RXD-01842 for Rebecca Turner and inspect its delivery destination, line quantities, and configured SuiteFleet relationship. The example contains PKG-001 | Sealed pharmacy parcel | 1 PACKAGE and DOC-001 | Accompanying document packet | 1 PACKET.

Start from a pharmacy-approved delivery request linked to the source prescription or dispense workflow. The pharmacy confirms release; SuiteFleet handles the transport allocation after that decision.

Epic prescription, dispense, and transport records serve different purposes. Keep the organization-approved delivery request as the dispatch boundary and preserve the source prescription and fill references without treating a transport update as a clinical action. Epic pharmacy interfaces.

2. Configure the evidence mapping

Preserve this relationship before exporting delivery work:

Capture the authorized recipient and parcel handover under the organization’s workflow. Keep clinical details out of routing notes and restrict evidence access to the intended operational users.

3. Define and check the evidence requirements

Agree the evidence policy before dispatch: which shipments need a recipient name, photographs, signature, and completion information, and who reviews missing evidence. Only require capture methods verified in the deployed driver workflow. Confirm that the connector can retrieve each required evidence field.

Before opening proof, match the task to Delivery allocation RXD-01842-1 through the correlation record. Names, addresses, and order display numbers alone are insufficient when the recipient receives repeat or split shipments.

Distinguish the expected consignee from the person who actually accepted the goods. Validate file access and retention requirements with the deployment owner so a saved link remains useful to the intended support team.

4. Review proof of recipient handover

Open Proof from the task or Reports → POD Analysis → Full proof. Review delivery photos, signature, recipient, and recorded completion together. Review Proof of pickup and Proof of delivery separately. Confirm recipient handover from the delivery record.

Do not infer received item quantities from a photograph, a signature, or the package count. Store the event time with its time zone. This example uses America/Chicago (CDT).

A redelivery attempt must retain the same authorized parcel relationship and pharmacy-controlled instructions. A failed stop must not create a new prescription, refill, or dispense action.

If there is a shortage, refusal, or disputed recipient, preserve the original evidence and record the exception. Retain the source shipment and line keys during review; do not create a new shipment simply because proof needs correction.

5. Store controlled evidence references

Epic publishes pharmacy interface and FHIR specifications, including fill-status access for supported implementations. Validate the exact resource, organization access, and permitted operations; read access does not establish a delivery writeback capability. Epic fill-status specification.

Write recipient, event time, outcome, and evidence references only to validated destinations. Check whether the interface stores a file, an attachment relationship, or an external URL. Apply access controls to the evidence location; a link in a transaction does not itself grant appropriate access.

Handle status and attachment updates independently. If the status sync succeeds but a photo reference fails, retain the partial integration error and retry that operation safely. Verify the target record after retry before reporting a clean sync.

6. Verify the result in Epic

Return recipient and delivery evidence to the approved delivery extension or document destination. Do not change medication-order, dispense, administration, or clinical completion states from a driver event. Epic pharmacy interfaces.

Read back the linked record and review every outstanding allocation before reporting the full delivery requirement complete. Test partial shipment, partial acceptance, failed delivery, duplicate completion, and delayed writeback. Keep inventory posting, receipt evidence, and payment reconciliation under their respective configured rules.