Reporting a Medication Error or Near-Miss — Practice Checklist
Walk through all 6 steps in order. Use this to build the habit until the sequence is automatic.
Step-by-Step Procedure (6 steps)
- 1.
Recognize that near-misses (errors caught before reaching the patient) are reportable events, not just completed errors that reached a patient — most quality-improvement systems depend on near-miss data to prevent future harm.
- 2.
Immediately inform the pharmacist of any error or near-miss, regardless of how minor it seems — this is not optional and is not a step to delay or skip out of embarrassment.
- 3.
If the error already reached the patient, support the pharmacist-led response: this typically includes contacting the patient, assessing for any harm, and correcting the dispensed medication.
- 4.
Complete your pharmacy's internal incident report accurately and factually — describe what happened without assigning blame, focusing on the sequence of events and any contributing factors (interruption, look-alike packaging, a mislabeled bin, etc.).
- 5.
For reportable adverse events (not just internal process errors), understand that your pharmacy or pharmacist may also submit a report to the FDA's MedWatch program — this is separate from your internal incident report.
- 6.
Participate honestly in any follow-up root-cause analysis or continuous-quality-improvement (CQI) review — the goal is to find and fix the system-level cause, not to find someone to blame.
Quality Checkpoints (4)
Confirm each of these before considering the task complete.
Near-misses are reported with the same seriousness as completed errors, not dismissed because "nothing happened."
The pharmacist is informed immediately, not after the shift or "when things calm down."
The incident report is factual and sequence-focused, not blame-focused.
Any required external reporting (e.g., MedWatch) is understood as a pharmacist-level responsibility the technician supports, not something the technician decides to skip.
Avoid These Mistakes
- ⚠
Not reporting a near-miss because "it didn't actually happen" — near-miss data is exactly what most error-prevention programs rely on.
- ⚠
Delaying disclosure to the pharmacist out of fear of getting in trouble, which delays any needed patient follow-up.
- ⚠
Writing an incident report that focuses on blaming a coworker rather than describing the sequence of events and contributing factors.
- ⚠
Assuming a reporting system (like MedWatch) is something only the pharmacist needs to know exists — technicians should understand it exists even if they don't submit it themselves.
Also prep for the written exam
500+ free PTCE practice questions with instant explanations.
Take the Practice Test →