Common Mistakes: Reporting a Medication Error or Near-Miss
These are the specific ways this task goes wrong on the job — not hypothetical edge cases, but patterns that cause real dispensing errors, insurance problems, or patient safety issues.
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.
How the Quality Checkpoints Prevent These
Every mistake above is caught by one of this task's quality checkpoints — the habit of checking these consistently is what actually prevents the error, not just knowing it exists.
- ✓
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.
Practice the written exam too
The knowledge behind every task is tested in the written PTCE. 500+ free questions.
Take the Practice Test →