An actual recall is a poor time to discover that staff can search a medicine name but cannot distinguish its batches. A pharmacy recall drill tests whether the team can connect an official notice with stock, movements and the required response records.
Use a fictional exercise and clearly mark every document as a drill. Actual actions must follow the relevant authority or supplier notice and the responsible professional's procedures. This worksheet is not a universal recall rule for all countries.
Start with an authentic source route
Define where staff obtain alerts, who reviews them and who covers absences. Save the notice reference and version so a later update does not get confused with the original instruction.
The FDA drug-recall page is an official US source example. Pharmacies in other markets must use the applicable local sources; a US notice is not automatically a local instruction for a differently supplied product.
Match more than the display name
Build a fictional notice with product identifier, strength, form, manufacturer and affected batch information. Ask staff to identify matching records without assuming that every similarly named product is affected.
Record the exact matching criteria. If the system search is broad, have the responsible reviewer distinguish confirmed matches from candidates requiring investigation. Where identifiers differ between packaging levels, verify the mapping instead of equating a carton code with an individual saleable-unit code.
GS1's healthcare identification guidance explains how identifiers and production data can support traceability. Do not infer that scanning a barcode alone authenticates a medicine or satisfies every market's requirements.
Reconstruct the quantities
Consider an exercise beginning with 120 received units. Records show 70 supplied, ten returned through a documented route and 40 currently on site. The arithmetic reconciles to 120, but the drill still needs to establish locations, references and any stock in transit or segregated status.
If the records instead explain only 116, assign the four-unit gap for investigation. Do not fill the difference with an invented adjustment to make the exercise appear complete.
Keep customer or transaction information restricted to authorised people. Patient-facing contact and professional advice must follow the actual notice and applicable procedures; a drill should not send simulated recall messages to real customers.
Track the response as a case
Use fields for drill reference, notice received time, reviewer, identified stock locations, quantities, movements checked, unresolved records, escalation reference and authorised closure. Measure time to locate the records separately from time to complete the professional review.
Assess whether staff can protect affected stock from ordinary allocation under the approved procedure and retain its status history. An expired-stock flag and a recall status may represent different reasons for unavailability and should not be conflated.
After the exercise, choose two or three concrete fixes: missing batch capture at receipt, an undocumented branch transfer or an unreliable alert handover. Repeat the relevant part of the drill to confirm the change worked.
For developers, store identifiers and batch data through the transaction trail, not solely on the current product record. Editing today's product description should not rewrite the evidence describing a historic movement.
Evaluate RunMyPharmacy's inventory workflow and batch/expiry records against this acceptance checklist. Confirm actual recall-status, historic tracing and export support rather than assuming automated alerts or complete regulatory traceability.
Disclosure: created for the RunMyPharmacy team with AI drafting assistance and checks of examples, sources and product links. We build the linked product. Numerical examples are hypothetical.
Top comments (0)