Pharmacy Refill Turnaround Reports for Adult Family Homes

A pharmacy refill turnaround report should measure the full path from a resident-specific refill need through request, pharmacy response, dispensing, delivery, facility receipt, and supply availability. Measuring only “request sent” to “pharmacy completed” can hide failed transmission, unreceived delivery, or medication that never became available for the resident.

This guide covers operational reporting, not pharmacy practice, prescribing, or a universal service-level standard. It was reviewed on August 8, 2026. Providers and pharmacies should validate definitions, responsibilities, privacy, and escalation rules for each relationship.

Define the refill lifecycle

Use explicit states such as:

• Need detected
• Request drafted
• Request sent
• Delivery confirmed to pharmacy
• Pharmacy acknowledged
• Clarification required
• Refill too soon or not authorized
• Prescriber authorization pending
• In process
• Ready or dispensed
• Delivery scheduled
• Delivered
• Facility receipt verified
• Resident supply accepted and available
• Canceled or closed with reason

Do not treat a portal message as pharmacy acknowledgement unless the pharmacy actually confirmed it. Keep transmission, delivery, and business response separate.

The medication refill management guide explains the operational workflow. This article focuses on measuring and reporting it accurately.

WAC 388-76-10475 requires Washington Adult Family Homes to keep applicable daily medication logs current and to document new or changed medications, including written verification and pharmacy receipt elements. A refill report should support that medication system without presenting a request status as proof that a changed medication or resident supply has been received.

Give every request stable identity

Record:

• Refill request ID
• Resident and facility
• Medication order and resident supply
• Pharmacy and authorized facility-pharmacy relationship
• Request reason
• Quantity or days remaining evidence
• Requester and request time
• Priority under facility policy
• Current owner and state
• Cancellation or replacement links

Stable IDs prevent retries from creating duplicate requests. A new request for the same medication should link to the prior request but remain separate when it represents a new refill cycle.

Capture timestamps at each boundary

Turnaround measures depend on distinct times:

• Need detected
• User submitted
• Server accepted
• Pharmacy received or acknowledged
• Clarification opened and resolved
• Prescriber request and response
• Dispensed or ready
• Courier pickup and delivery
• Facility received
• Supply verified and available
• Case closed

Store source and time zone. Do not backfill missing timestamps from later states without labeling the estimate.

For offline actions, preserve event time and synchronization time. Report data-quality limitations.

Measure useful intervals

Calculate intervals such as:

• Detection to request
• Request to pharmacy acknowledgement
• Acknowledgement to clarification
• Time awaiting facility response
• Time awaiting prescriber response
• Pharmacy processing time when supported by reliable states
• Dispensed to delivered
• Delivered to facility verification
• End-to-end time to resident availability

Pause-clock calculations require an agreed definition and evidence. Show elapsed clock time alongside any adjusted business-time measure so the report is transparent.

Do not attribute external waiting time to pharmacy performance when the source data shows the request was waiting on the home, prescriber, payer, or resident decision.

Include supply-risk context

The most important operational question is whether the resident may run out before verified replacement arrives. Link:

• Current resident-supply balance
• Documented usage rate
• Scheduled doses
• Remaining-day estimate and method
• Earliest request date under known constraints
• Expected delivery
• Administration exceptions tied to availability

Label estimates clearly. Do not alter prescribed dosing or advise rationing based on a report.

The medication inventory and count records guide explains resident-supply tracking. The refill report should use its authoritative transactions rather than an editable free-text balance.

Separate request outcomes

Use structured outcome reasons:

• Completed as requested
• Partial fill
• Too soon
• No refills remaining
• Prescriber response required
• Insurance or payer issue
• Product unavailable
• Order discrepancy
• Resident transferred or discharged
• Medication discontinued
• Duplicate request
• Facility canceled
• Other verified reason

Do not count canceled or duplicate requests as completed turnaround successes. Include them in data-quality and workflow reports.

Track clarification loops

One case may have multiple questions. Each clarification event should capture sender, recipient, issue category, time, secure channel, response, resolution time, and effect on the request.

Useful categories include order mismatch, strength or form, directions, quantity, prescriber, resident identity, facility, delivery address, insurance, or supply question.

Do not place resident medication detail in unsecured email. Notifications can link authorized users to the secure request.

Verify facility receipt

Delivery status is not proof the correct medication reached the correct resident supply. Record:

• Facility and resident label match
• Medication, strength, form, and directions comparison
• Quantity received
• Original container and label condition
• Receiver and time
• Accepted, quarantined, rejected, or clarification status
• Supply record created

The pharmacy delivery and medication receipt guide describes this handoff. End-to-end turnaround closes only at the agreed verified state, not at a courier scan alone.

Design pharmacy and facility views safely

The pharmacy may serve many facilities. Require an explicit active facility selection by authorized name or ID before resident search. The report header and every drill-down should show the active boundary.

Pharmacies should see only requests for facilities that granted current access. Facilities should see only their residents and connected pharmacies. Server-side authorization must protect queries, exports, and cached results.

Switching facilities should clear resident filters, draft notes, recipients, and prior result rows.

Choose metrics that do not distort behavior

Useful metrics include:

• Median and percentile end-to-end time
• Acknowledgement time
• Facility and prescriber waiting intervals
• On-time verified receipt under agreed definitions
• Requests completed before projected runout
• Partial fills
• Clarification frequency by category
• Unacknowledged or stalled cases
• Receipt-verification delay
• Requests linked to unavailable-dose exceptions

Avoid relying only on averages, which can hide a small number of severe delays. Show sample size and excluded or incomplete records.

Do not reward premature state changes. A pharmacy should not improve its score by marking a request completed before dispensing or delivery evidence exists.

Handle reopened and linked cases

A completed request may reopen if the delivery was wrong, partial, damaged, or not received. Preserve the original completion event and add the reopened state, reason, owner, and revised resolution.

Link replacement shipments and corrected orders. Do not overwrite the original request or start an unrelated case that hides end-to-end delay.

For duplicate requests, choose one surviving case and record the relationship without deleting either audit history.

Build practical report filters

Filter by:

• Facility and resident
• Pharmacy
• Medication
• Request and receipt date range
• Current status
• Outcome reason
• Priority
• Owner
• Prescriber-wait state
• Supply-risk level
• Partial fill
• Reopened case

Display active filters and data-through time. A pharmacy comparison report must use comparable definitions and authorized facilities.

Produce clean PDF and CSV outputs

The PDF should show title, facility or authorized portfolio, pharmacy, period, definitions, sample size, summary metrics, stalled cases, and a detailed request table. Use black text, repeated headings, page numbers, and color-independent states.

CSV supports authorized analysis but needs the same server-side scope and audit logging. Do not export sensitive fields unnecessary to the metric.

Report generation should store requester, filters, metric-definition version, data-through time, file identifier, and download history.

When a metric excludes canceled, duplicate, transferred, or incomplete cases, list those counts beside the included sample. A facility should be able to reproduce the result by applying the published definitions to the detailed requests. If the source timestamp is corrected, regenerate the metric under a new report version rather than altering an issued PDF silently.

Reconcile with medication exceptions

Link refill cases to medication-unavailable outcomes and inventory discrepancies without claiming causation automatically. A late refill may not have caused a missed dose; an unavailable dose may involve a different supply problem.

The report should show confirmed links, possible links awaiting review, and no documented administration impact. Avoid retroactively assigning a request to an exception merely because the medication names match.

Test complete and messy lifecycles

Use demonstration records to test:

1. Routine refill completed before projected runout.
2. Pharmacy acknowledgement delayed.
3. Prescriber authorization pending.
4. Partial fill followed by completion.
5. Product unavailable.
6. Courier delivered but facility not verified.
7. Wrong resident package quarantined.
8. Case reopened after damaged delivery.
9. Duplicate request retry.
10. Resident transferred mid-request.
11. Medication discontinued before completion.
12. Missing timestamp excluded from a metric.
13. Pharmacy serving multiple facilities.
14. Cross-facility export denied.
15. PDF metrics reconciled to detailed requests.

Confirm that every calculated interval can be traced to source timestamps and metric definitions.

Frequently asked questions

When does refill turnaround begin?

Define and display it. Useful reports can show both need-detected and request-sent starting points rather than hiding facility preparation time.

When is a refill complete?

Use the agreed state. For resident availability, pharmacy completion or courier delivery alone is insufficient; facility receipt and supply verification may still be pending.

Should prescriber waiting time count against the pharmacy?

Show the interval separately and use transparent adjusted and elapsed measures. Do not attribute time without reliable ownership states.

Can averages summarize performance?

Use median, percentiles, sample size, and stalled-case detail. Averages alone can hide important delays.

How should a partial fill appear?

Record the partial quantity, resident availability, remaining obligation, and final completion. Do not mark the full request complete prematurely.

Measure the path to verified resident supply

A reliable turnaround report connects resident-specific need, secure request, pharmacy response, clarification, dispensing, delivery, facility receipt, supply risk, and reopened exceptions.

Explore AFH Manager to evaluate refill lifecycle timestamps, facility-pharmacy boundaries, supply-risk links, turnaround metrics, stalled-case filters, secure exports, and audit history. Validate definitions with each pharmacy relationship before live use.