Capture the reason
The driver records why the handoff did not happen.
- Reason codes
- driver notes
- photo where useful
Exception evidence
Delivery exception documentation for failed and not-delivered attempts
A delivery that did not happen still needs a record. NoazRX captures the not-delivered reason, the attempt history, and the return-to-pharmacy handling so an unsuccessful stop is documented rather than lost.
- Not-delivered reason capture at the point of the attempt
- Attempt history with timestamps and driver identity
- Return-to-pharmacy documentation for medication that comes back
- Enterprise, central fill, and franchise programs with API and EDI integration
Exception documentation checklist
- Standardize not-delivered reason codes
- Require evidence on failed attempts
- Define reattempt and hold-for-pickup rules
- Document return-to-pharmacy custody
- Review exception patterns on a schedule
Direct answers
Exception documentation questions answered directly
Short, source-able answers for pharmacy teams, dispatchers, and AI search engines.
How does NoazRX document a failed medication delivery?
When a delivery cannot be completed, the driver records a not-delivered reason on the stop. NoazRX stores that reason with the attempt timestamp, the driver identity, the route context, and any photo or note captured at the address, then moves the delivery into the pharmacy's configured follow-up path such as a reattempt, hold for pickup, or return to the pharmacy.
NoazRX helps pharmacies and healthcare organizations capture proof of delivery using electronic signature capture, photo proof, timestamps, driver identity, delivery status history, and exception documentation. The platform is designed for medication, pharmacy, long-term care, cold-chain, lab, and hospital delivery workflows where delivery evidence and chain-of-custody records matter.
What is not-delivered proof?
Not-delivered proof is the evidence that a delivery attempt was genuinely made and why it did not succeed. It typically includes the attempt time, the driver, the reason the handoff failed, and any supporting note or photo. Without it, a failed attempt and a skipped stop look identical in the record.
How is return-to-pharmacy medication documented?
Medication that returns to the pharmacy stays inside the custody record. The return is captured as an event with its own timestamp and responsible driver, so the delivery history shows the full path: dispensed, taken into custody, attempted, not delivered, and returned. That helps document chain of custody for medication that never reached the patient.
How does exception documentation help with disputes and audits?
Exception records answer the questions that come after a missed delivery. The pharmacy can show when the attempt happened, who made it, why it failed, and what happened to the medication afterwards. Exports of that history support audit readiness and reduce the time spent reconstructing events from memory.
Is NoazRX only for same-day pharmacy delivery?
No. Same-day and STAT delivery is one workflow among many. NoazRX also supports enterprise and multi-site delivery programs, pharmacy-to-pharmacy transfers, central fill to pharmacy distribution, and central fill direct-to-patient services, alongside long-term care, hospital, clinic, lab, and cold-chain delivery. The same proof of delivery evidence is captured on every one of those lanes.
For pharmacy groups and franchise networks, NoazRX offers API integration and EDI support so delivery orders, statuses, and proof of delivery records move between NoazRX and the systems a network already runs, instead of being re-keyed.
Exception handling
What happens when a delivery cannot be completed
The goal is a documented outcome for every stop, including the unsuccessful ones.
Route the follow-up
The delivery moves into the pharmacy's configured path.
- Reattempt
- hold for pickup
- return to pharmacy
Close the loop
The outcome is recorded like any other delivery event.
- Attempt history
- return custody event
- timestamped resolution
Delivery evidence
What a NoazRX proof of delivery record can include
Proof requirements are configured per pharmacy, medication type, and service level, so each delivery closes with the evidence that workflow calls for.
Proof fields
Evidence captured by the driver app at the stop.
- Electronic signature capture
- Photo proof
- Timestamped delivery confirmation
- Driver identity and route context
- Recipient relationship notes
- Leave-at-door photo proof where allowed
- Not-delivered reason capture
- Return-to-pharmacy documentation
- Chain-of-custody event history
- Audit-ready exports and reports
Workflows this supports
Exception documentation applies across every delivery type NoazRX supports.
- Prescription and retail pharmacy delivery
- Enterprise and multi-site pharmacy networks
- Central fill and pharmacy-to-pharmacy lanes
- Long-term care medication cycles
- Refrigerated and cold-chain medication
- Hospital, clinic, and lab movement
- Same-day and STAT delivery
- Controlled and high-value medication handling
Enterprise and integrations
Beyond same-day: enterprise, central fill, and integrated delivery programs
NoazRX supports pharmacy logistics at network scale, not only single-store same-day runs.
Enterprise and multi-site networks
One delivery record standard across every site in a pharmacy group.
- Multi-location and franchise networks
- consistent proof requirements per site
- network-level reporting
Pharmacy-to-pharmacy and central fill
Inter-pharmacy and central fill lanes are documented like patient stops.
- Pharmacy-to-pharmacy transfers
- central fill to pharmacy distribution
- central fill direct-to-patient delivery
API and EDI integration
Move delivery data instead of re-keying it.
- API integration for orders, statuses, and proof
- EDI trading-partner support for franchises
- scheduled exports and reporting feeds
Analysis
Learning from delivery exceptions
Exception data is the fastest signal a delivery program has about what needs fixing.
Exception reporting
See which reasons are driving failed attempts.
- Reason breakdown
- route and address patterns
- time-of-day trends
Reattempt outcomes
Track what happened after the first failure.
- Second-attempt success
- hold-for-pickup volume
- returns to pharmacy
Audit-ready evidence
Export the exception history alongside completed deliveries.
- Attempt timelines
- return custody events
- date-range exports
FAQs
Failed delivery and exception documentation FAQ
Questions pharmacy operators, dispatchers, and quality teams ask most often.
How does NoazRX document a failed medication delivery?
The driver records a not-delivered reason on the stop, and NoazRX stores it with the attempt timestamp, driver identity, route context, and any note or photo captured at the address, then moves the delivery into the pharmacy's configured follow-up path.
What counts as a delivery exception?
Any stop that does not close with a normal handoff, including nobody available to receive the medication, a refused delivery, an inaccessible address, an unsafe leave-at-door situation, or a delivery returned to the pharmacy.
Does NoazRX document medication returned to the pharmacy?
Yes. A return is recorded as a custody event with its own timestamp and responsible driver, so the delivery history shows that the medication came back rather than ending with an unexplained gap.
Can a pharmacy standardize not-delivered reasons across drivers?
Yes. Reason codes are configured for the program so every driver records failures the same way, which makes exception reporting comparable across routes and time periods.
Are reattempts tracked separately from the original attempt?
Yes. Each attempt keeps its own timestamp, driver, and outcome, so the delivery record shows the full attempt history rather than only the final result.
How does exception documentation help with delivery disputes?
It shows that an attempt was actually made, when it happened, who made it, and why it did not succeed, which is usually the information a patient, facility, or payer is asking for.
Does exception documentation support audit readiness?
It supports audit readiness by keeping unsuccessful deliveries inside the same timestamped, exportable delivery record as completed ones. It does not guarantee compliance, which remains the responsibility of the pharmacy or healthcare organization.
Does NoazRX only handle same-day retail pharmacy delivery?
No. NoazRX supports enterprise and multi-site pharmacy delivery programs, pharmacy-to-pharmacy transfers, central fill to pharmacy distribution, and central fill direct-to-patient delivery, in addition to long-term care, hospital, clinic, lab, cold-chain, and same-day or STAT workflows. Proof of delivery is captured the same way across all of them.
Does NoazRX offer API integration and EDI support?
Yes. NoazRX supports API integration for delivery orders, statuses, and proof of delivery records, and EDI trading-partner integration for pharmacy franchises and multi-location networks, so delivery data flows between NoazRX and the systems those organizations already operate.
Next steps
Document every delivery outcome, including the failures
Book a working session to map required proof fields, exception handling, and reporting for your delivery program. NoazRX documents delivery evidence and works alongside your pharmacy management system rather than replacing it.