Report errors and improve the system

What you will learn

• Distinguish a near miss, medication error and adverse event.
• Recognize the purposes of MedWatch and VAERS.
• Propose a concrete improvement based on an event's contributing conditions.

Before you start

Reporting describes what happened; it does not require inventing certainty about the cause. Protect patient privacy and use the site's approved reporting process. Urgent patient care comes before completing a report.

Separate event, outcome and cause

A medication error is a preventable mistake in the medication-use process. A near miss is an error caught before it reaches the patient. An adverse event is an unwanted medical occurrence; its presence alone does not prove a medication caused it or that an error occurred.

Imagine the wrong strength is selected but caught during checking. That is a near miss worth reporting internally. Change only the timing: the product reaches the patient before the mismatch is found. The event now requires the site's response to an error that reached the patient, including prompt pharmacist involvement.

Whether harm occurred is another question. “No harm was reported” is not the same as “nothing happened.” A near miss can reveal the same weak process that might cause a harmful error next time.

Pause and predict

A patient develops a symptom after taking a medicine. Does the sequence alone prove that the medicine caused it?

Know the external reporting pathways

FDA MedWatch receives reports about safety problems involving FDA-regulated medical products, including serious adverse events, product-quality problems and medication-use concerns. VAERS is the Vaccine Adverse Event Reporting System for events after vaccination. It is an early-warning system; a VAERS report alone does not establish that a vaccine caused the event.

Some reporting is voluntary and some is required under specific rules. Follow the responsible professional's process and current requirements. Do not assume that an internal incident report automatically satisfies every external duty.

For an invented example, a patient reports an event after vaccination. Preserve the vaccine name, lot if known, timing and reported symptoms for the appropriate clinical and reporting process. Do not rewrite “occurred afterward” as “definitely caused by.”

Improve the step, not just the instruction to concentrate

Root-cause analysis asks how conditions and steps contributed to an event. Continuous quality improvement means making a targeted change and checking whether it works. Neither is simply assigning blame to the last person in the chain.

Suppose two fictional strengths share a shelf bin, and the small strength label is obscured. A concrete improvement is to separate the strengths and make the distinguishing information visible. “Everyone should pay more attention” leaves the physical confusion unchanged.

Now change the case: the shelf was correct, but an outdated electronic shortcut selected the wrong directions. Rearranging the shelf would not address that cause. The proposed correction must match the evidence.

Try it without the walkthrough

1. A wrong quantity is caught before pickup. Is it worth recording even though the patient never receives it?
2. A vaccine event is reported to VAERS. Does the existence of that report prove causation?
3. A near miss arose because an obsolete template inserted old directions. Name a targeted corrective action and one way to check it.

Keep this pattern

Describe facts, separate causation from timing, choose the right reporting path and fix the contributing condition.