🚧 Under construction — VoTechWorks is being built. A free tech program — complimentary, as our commitment to get America working.
voTechWorksGrade 13 · a vocational technology learning center, by urbanicity
newSchoolWorks.com › VoTechWorks › Health & Personal Services › Pharmacy Technician › Pharmacy Law, Safety and Quality › Lesson 9
HLT-PHAR41-05 · Lesson 9 · 15 clock hours · theory

Error prevention and the types of prescription errors

Objective. Classify prescription errors — wrong drug, dose, patient, directions, quantity, omission — and the checks that stop them before the patient.

⚠ Pending professional review

This lesson, its worked examples and its practice questions has not yet been verified by a licensed pharmacist or by a certification or approval body. It is a study draft and may contain errors. Do not use it to make decisions about any patient or medication. Always follow your instructor, your supervising professional, and current official references and regulations.

VoTechWorks program approval and accreditation are still in progress. Credentials are issued only by the certifying bodies named in each program, after their own exams.

Why Prescription Errors Matter

A prescription error is any preventable event that may cause or lead to inappropriate medication use or patient harm. Even a single digit transposed in a dose or a name misread on a label can send a patient to the emergency room. The pharmacy technician's role in the error-prevention chain is critical: you are often the first person to physically handle a prescription before it reaches the patient, making your attention to detail a direct patient-safety measure.

The Six Major Categories of Prescription Errors

Standard practice organizes prescription errors into six categories. Learning to name and recognize each type helps you catch them at the point of entry.

Wrong drug — The medication dispensed or entered is not what the prescriber ordered. This includes selecting a look-alike or sound-alike (LASA) drug, pulling the wrong strength from the shelf, or misreading handwriting (for example, confusing "Celebrex" with "Cerebyx").

Wrong dose — The correct drug is selected but the amount is incorrect. This includes errors in the strength (e.g., 100 mg instead of 10 mg), the concentration of a liquid, or the calculated quantity of doses prepared during compounding.

Wrong patient — The medication is prepared or dispensed to someone other than the intended patient. In a busy pharmacy this can occur when two patients share similar names, dates of birth, or address information.

Wrong directions (sig error) — The label instructions do not match what the prescriber ordered. A common example is entering "twice daily" when the prescription reads "twice weekly," or omitting the route of administration entirely.

Wrong quantity — The number of units dispensed does not match what was prescribed. Supplying 30 tablets when 90 were ordered, or filling a 30-day supply when 90 days were authorized, are typical examples.

Omission error — A required step or piece of information is left out entirely. Examples include failing to include refill information on the label, not capturing a patient allergy in the profile, or skipping a mandatory drug utilization review (DUR) alert during data entry.

The Verification Chain: How Errors Are Caught

No single check catches every error. Pharmacies layer multiple controls so that a mistake has to pass through several filters before it reaches the patient.

Prescription receipt and data entry — When a prescription arrives, the technician transcribes all information into the pharmacy management system. Careful reading of the prescriber's order — including drug name, strength, dosage form, directions, quantity, and refills — is the first defense. Any unclear item must be clarified with the prescriber before entry, never assumed.

Pharmacist verification (prospective DUR) — After data entry, the pharmacist reviews the entered prescription against the original before any product is prepared. The pharmacist also reviews the patient's medication profile for interactions, allergies, duplicate therapy, and dosing appropriateness. Federal law requires a pharmacist, not a technician, to perform the final verification and patient counseling offer.

Product selection and barcode scanning — When retrieving a stock bottle, the technician compares the NDC (National Drug Code) on the bottle to the NDC on the fill order. Many pharmacies use barcode verification systems that scan the bottle and alert the technician if the wrong product is scanned. This step catches wrong-drug and wrong-strength errors that survive data entry.

Label and product check — Before dispensing, the pharmacist performs a final check comparing the original prescription, the label, and the physical product. For controlled substances additional counting verification is standard.

Point-of-sale counseling offer — Federal law requires every patient or caregiver be offered counseling by the pharmacist when picking up a new prescription. This step can surface discrepancies ("That doesn't look like my usual tablet") that earlier steps missed.

Root-Cause Analysis: Finding Why Errors Happen

When an error or near-miss occurs, the goal is not to assign blame but to understand the system failure that allowed the error. Root-cause analysis (RCA) is a structured method for tracing an error back to its underlying causes. A common RCA tool is the fishbone (Ishikawa) diagram, which organizes contributing factors into categories such as people, processes, equipment, environment, and materials. For example, a wrong-drug error might trace to poor lighting at the dispensing counter (environment), look-alike packaging from the manufacturer (materials), and insufficient barcode scanning (process).

The findings from RCA lead to corrective actions — changing a workflow, adding a physical alert (tall-man lettering, shelf stickers, color coding), or retraining staff. Reporting errors through internal systems and, where appropriate, to external databases such as the FDA MedWatch program supports industry-wide learning.

Technician Scope and Safety Boundaries

Technicians must recognize the edge of their scope. If a DUR alert fires, if a dose seems clinically unusual, or if a patient reports an unexpected reaction, the correct action is always to stop the workflow and involve the pharmacist. Proceeding past an unresolved alert to keep a queue moving is one of the most common contributing factors in serious dispensing errors. Patient safety takes priority over speed every time.

Key terms10

Prescription errorAny preventable event during the medication-use process that may cause or lead to inappropriate medication use or patient harm.
Look-alike/sound-alike (LASA) drugsDrug pairs whose names appear similar in print or sound similar when spoken, creating a heightened risk of wrong-drug selection.
Omission errorAn error in which a required step, piece of information, or medication dose is left out entirely.
Drug utilization review (DUR)A pharmacist's evaluation of a patient's medication profile for interactions, allergies, duplicate therapy, and dosing concerns before a prescription is dispensed.
National Drug Code (NDC)A unique three-segment number assigned by the FDA that identifies the manufacturer, drug product, and package size of every commercially distributed drug.
Root-cause analysis (RCA)A structured process used after an error or near-miss to identify the underlying system factors that allowed the event to occur, rather than placing blame on individuals.
Fishbone (Ishikawa) diagramA visual RCA tool that organizes contributing causes of a problem into categories such as people, process, equipment, environment, and materials.
Near-missAn error that was caught and corrected before reaching the patient; also called a good catch, it is a valuable source of safety data.
Tall-man letteringA risk-reduction technique that uses mixed upper- and lower-case letters to highlight the dissimilar portions of LASA drug names (e.g., hydrALAZINE vs. hydrOXYzine).
Prospective DURReview of a new prescription against a patient's existing medication profile before the medication is dispensed, as opposed to retrospective review after dispensing.
In class: Error classification drill · Root-cause fishbone · Barcode verification practice
Materials: Error case files
Check: Quiz ≥ 75%

Practice check8

Answer each question, then check it. Nothing is recorded; this is your own practice.

Patient Safety and Quality Assurance
1. A technician retrieves amLODIPine 5 mg tablets when the prescription clearly reads amLODIPine 10 mg tablets. Which error category best describes this event?
Patient Safety and Quality Assurance
2. Two patients with the last name 'Williams' pick up prescriptions on the same day. The technician bags each order under the correct name but later discovers the bags were handed to the wrong individuals. Which error category occurred?
Patient Safety and Quality Assurance
3. A prescription label reads 'Take 1 tablet twice daily' but the original prescription states 'Take 1 tablet twice weekly.' What type of error has occurred?
Patient Safety and Quality Assurance
4. A technician enters a new prescription but does not document a penicillin allergy flagged by the patient during drop-off. The pharmacist later dispenses amoxicillin without an allergy alert. Which error category is most directly illustrated by the failure to document the allergy?
Patient Safety and Quality Assurance
5. During barcode verification, the scanning system alerts the technician that the NDC on the stock bottle does not match the fill order. What is the most appropriate immediate action?
Patient Safety and Quality Assurance
6. A fishbone diagram used after a dispensing error would most accurately be described as a tool for:
Federal Requirements
7. Under federal law, which of the following tasks must be performed by the pharmacist rather than the pharmacy technician?
Patient Safety and Quality Assurance
8. A pharmacy receives a prescription for metFORMIN 500 mg but the technician selects metroNIDAZOLE 500 mg from the shelf. Which two error-prevention strategies would most directly reduce the likelihood of this specific error?
Record this lesson on my transcript. Sign in with your key and enrollment email to record lessons (enroll free if you have no key). This page stays open to read and practise.