Patient Safety and Quality Assurance
Reporting a Medication Error or Near-Miss
Recognizing an error (or a near-miss caught before it reached the patient) and reporting it through the correct internal and, when applicable, external channels — a Patient Safety & Quality Assurance task.
Note:the PTCE has no hands-on or oral evaluation component — this guide describes the real on-the-job task so you understand the knowledge the written exam tests, not a skills test you'll be scored on in person.
Step-by-Step Procedure
- 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
- ✓
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.
Common 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.
On-the-Job Tips
- →
A culture that treats near-miss reporting as valuable (not punishable) catches more future errors — if your workplace treats every report as a hunt for someone to blame, that itself is a quality problem worth naming internally.
- →
Write incident reports the same day, while details are fresh and accurate, rather than reconstructing them later from memory.
Also study the exam domain
The written PTCE tests the knowledge behind this task in multiple-choice format — use the study guides to reinforce it.
Browse All PTCE Study Guides →Practice the written exam
Free practice questions with instant feedback and explanations.
Take a Practice Test →