SOP templatesPharmacy

Dispensing Error Reporting SOP Template

A ready-to-use SOP for responding to a dispensing error or near miss, covering patient safety, correction, documentation, root cause review and follow-up.

FreeNo sign-upWord, PDF, Excel & CSV
Ilia PirozhenkoReviewed by Ilia Pirozhenko, Founder, Perfect WikiUpdated September 15, 202612 steps4 roles3 min read
Standard operating procedureSOP-PHA-008 ยท Rev 1.0
Owner
Pharmacist in Charge
Effective date
September 15, 2026
Review cycle
Every 12 months

1.Purpose

To respond to dispensing errors and near misses in a way that protects the patient first, corrects the record, and uses a non-punitive review to prevent repeat errors.

2.Scope

Applies to any dispensing error or near miss discovered by staff, the patient or the prescriber, whether the medication has already been picked up or is caught before release.

Definitions

Near miss
An error caught and corrected before the medication reached the patient.
Dispensing error
A discrepancy between what was prescribed and what was actually filled, labeled or handed to the patient.
Root cause analysis
A structured review to identify the underlying process or system factors that allowed an error to occur.

3.Responsibilities

Pharmacist
Assesses patient safety risk, corrects the record and leads the root cause review.
Pharmacy Technician
Reports errors or near misses observed and assists with correction under pharmacist direction.
Pharmacist in Charge
Reviews significant errors, decides on required external reporting and tracks corrective actions.
Patient
Reports suspected errors and provides information needed to assess and correct the issue.

RACI matrix

ActivityPharmacistPharmacy TechnicianPharmacist in ChargePatient
Assess immediate patient safety riskR/AIIC
Contact patient about a dispensed errorR/AIIC
Document the error or near missRRA-
Conduct root cause analysisRCA-
Report to prescriber or external body if requiredRIAI

R = Responsible, A = Accountable, C = Consulted, I = Informed

4.Materials and PPE

Materials, tools and systems

  • โ†’Incident and near-miss report form
  • โ†’Patient contact log
  • โ†’Root cause analysis worksheet
  • โ†’Corrective action tracker
  • โ†’Pharmacy dispensing system audit trail

5.Procedure

  1. 5.1

    Recognize and stop the process

    Pharmacy Technician

    As soon as an error or suspected error is identified, pause the related workflow so no further steps compound the issue while it is assessed.

  2. 5.2

    Assess immediate patient safety risk

    Pharmacist

    Determine whether the medication has been taken, and evaluate the potential clinical impact of the error before deciding next steps.

    Checkpoint: Patient safety risk is assessed and documented before any other corrective step begins.

  3. 5.3

    Notify the pharmacist in charge for significant errors

    Pharmacist

    Notify the pharmacist in charge immediately for any error with clinical significance or that has already reached the patient.

  4. 5.4

    Contact the patient if medication was dispensed

    Pharmacist

    Call the patient promptly to explain the error, advise on any needed action, and arrange correction or medical follow-up as appropriate.

    Warning: Do not delay patient contact while internal paperwork is completed; patient safety comes first.

  5. 5.5

    Correct the prescription record

    Pharmacist

    Correct the electronic record and any physical label or product still in the pharmacy's possession to reflect the accurate prescription.

  6. 5.6

    Document the error or near miss

    Pharmacy Technician

    Complete the incident report form describing what happened, how it was caught, and the immediate action taken, regardless of whether the patient was affected.

  7. 5.7

    Classify the error type and severity

    Pharmacist

    Categorize the error, such as wrong drug, wrong strength, wrong patient or labeling error, and rate its severity using the pharmacy's classification scale.

  8. 5.8

    Conduct root cause analysis

    Pharmacist

    Review the workflow steps involved to identify the underlying cause, such as a look-alike product, a workflow gap or a distraction, rather than stopping at individual blame.

  9. 5.9

    Notify the prescriber if applicable

    Pharmacist

    Contact the prescriber's office when the error could affect the patient's therapy plan or requires their awareness for follow-up care.

  10. 5.10

    Report externally if required

    Pharmacist in Charge

    Report the error to the state board or another required body if it meets the threshold set by local law or pharmacy policy.

  11. 5.11

    Review with staff in a non-punitive huddle

    Pharmacist in Charge

    Share the root cause and any process change with the team in a blame-free huddle so everyone understands how to help prevent a repeat.

  12. 5.12

    Track corrective actions to closure

    Pharmacist in Charge

    Log any process, training or system change identified in the corrective action tracker and confirm it is implemented and effective.

6.Quality checks

  • โ†’Every error and near miss is documented, regardless of severity.
  • โ†’Patient safety risk is assessed and, where dispensed, the patient is contacted the same day.
  • โ†’Root cause analysis looks at process factors, not just individual blame.
  • โ†’Corrective actions are tracked until confirmed complete.

7.Records

  • โ†’Incident and near-miss reports
  • โ†’Patient contact log
  • โ†’Root cause analysis worksheets
  • โ†’Corrective action tracker

8.KPIs

  • โ†’Number of near misses reported per month (higher can mean better reporting culture)
  • โ†’Number of errors reaching the patient per month
  • โ†’Average time from discovery to patient contact
  • โ†’Percentage of corrective actions closed within the target timeframe

9.Common mistakes

  • โ†’Correcting the record without documenting the error at all.
  • โ†’Delaying patient contact until an internal report is finished.
  • โ†’Treating root cause analysis as a way to assign blame rather than fix the process.
  • โ†’Not tracking whether a corrective action was actually implemented.

10.Revision history

RevisionDateDescriptionReviewed by
1.0September 15, 2026Initial releaseIlia Pirozhenko

This is a template. Adapt it to your organization, equipment and local regulations before use.

Ask this SOP

Nobody opens a PDF in the middle of a task. They ask.

Add this SOP to Perfect Wiki and your team gets answers in the chat app they already use, with a link to the exact step. Ask from ChatGPT, Claude or Copilot too.

Perfect Wiki AIExample answer

I caught a wrong-strength error before the bag was handed over, do I still need to report it?

Yes. Even though it never reached the patient, this is a near miss and should be documented the same way, since patterns in near misses often reveal a process gap before it causes real harm.Source: step 5.6 ยท Document the error or near miss
Ask your own question about this SOPโ€ฆSign up to keep asking
Word file vs Perfect Wiki

A downloaded SOP starts going out of date the day you save it.

Screen recorders like Scribe and Tango capture clicks. Perfect Wiki holds the whole procedure, including your recorded guides, and answers questions about it.

Word or PDFPerfect Wiki
Finding itDig through folders and email threadsAsk in Teams, Slack, kChat or Mattermost
Keeping it currentEmail a new version and hopeEdit once with AI, everyone sees the update
Everything in one placeText and imagesEmbed Scribe and Tango guides, SharePoint files and videos
Who can change itAnyone with the fileEditors you choose, everyone else reads
Common questions

Frequently asked questions

Didn't find what you're looking for? Contact our support โ†’

Your SOP library

Keep every SOP where your team can ask it.

Perfect Wiki is the knowledge base for Microsoft Teams, Slack, kChat and Mattermost. Store your SOPs, embed your Scribe and Tango guides, and let AI answer questions with a link to the right step.

No credit cardSetup in under 10 minutesCancel anytime