4.2 Adverse Event Reporting, REMS, and Continuous Quality Improvement

Key Takeaways

  • MedWatch and FAERS collect adverse drug event reports for drugs and devices; VAERS collects vaccine adverse events.
  • REMS programs (e.g., isotretinoin iPLEDGE, clozapine) impose extra safety steps before dispensing.
  • Root cause analysis (RCA) investigates errors to fix the system, not to blame the individual.
  • NIOSH and USP <800> govern safe handling, storage, and quarantine of hazardous drugs.
  • Continuous quality improvement (CQI) uses non-punitive error reporting to drive ongoing system change.
Last updated: June 2026

Adverse Event Reporting, REMS, and Continuous Quality Improvement

This section completes the Medication and Patient Safety domain by covering what happens after a safety event: how adverse events are reported, how high-risk drugs are managed through REMS, how errors are investigated, and how pharmacies build a culture of continuous improvement.

Adverse Drug Events vs Adverse Drug Reactions

TermDefinition
Adverse drug event (ADE)Any harm associated with a medication, including errors
Adverse drug reaction (ADR)Harm from a drug used correctly (e.g., a true side effect)
Side effectA known, often predictable secondary effect

Key Point: Every ADR is an ADE, but not every ADE is an ADR. An ADE can result from an error, whereas an ADR occurs even with correct use.

Reporting Systems You Must Know

The ExCPT tests which system receives which type of report. Memorize these three.

SystemWhat It CollectsRun By
MedWatchAdverse events for drugs, biologics, and devicesFDA
FAERSFDA Adverse Event Reporting System databaseFDA
VAERSVaccine adverse eventsCDC and FDA

Exam Tip: If the question is about a vaccine reaction, the answer is VAERS. For a drug or device adverse event, the answer is MedWatch / FAERS. This single distinction is frequently tested.

REMS - Risk Evaluation and Mitigation Strategies

A REMS is an FDA-required safety program for drugs with serious risks. It can require special enrollment, monitoring, or documentation before dispensing.

REMS ExampleRequirement
Isotretinoin (iPLEDGE)Prescriber/pharmacy/patient registration; pregnancy testing; 7-day dispense window
ClozapineMonitoring of white blood cell counts before dispensing
Certain opioidsPrescriber education and patient counseling materials

The technician verifies that REMS requirements are met (registration, lab results, dispense window) before the prescription is released.

Root Cause Analysis and Error Investigation

When an error or near miss occurs, the pharmacy performs a root cause analysis (RCA) to find the underlying system failure rather than blaming one person. Tools include workflow analysis and the "five whys."

PrincipleMeaning
System focusFix the process, not the person
Non-punitive reportingStaff report freely without fear
DocumentationRecord the error, near miss, and corrective action
Follow-upVerify the fix prevents recurrence

Worked Example: A wrong-strength error traces back to two strengths stored in adjacent unlabeled bins. RCA fixes the system by adding shelf labels and barcode scanning, not by disciplining the technician.

NIOSH and Hazardous Drug Safety

The National Institute for Occupational Safety and Health (NIOSH) publishes the list of hazardous drugs and handling requirements that pair with USP <800>. Requirements include quarantine of certain agents, dedicated storage away from other medications, PPE, and spill procedures. The technician follows quarantine, proximity, and handling rules to protect staff and prevent contamination.

Continuous Quality Improvement (CQI)

CQI is an ongoing, data-driven effort to improve safety and service. It depends on a non-punitive culture so that errors and near misses are reported and analyzed. Pharmacies also perform routine quality-assurance checks of inventory: removing expired or recalled stock, securing unsecured medications, and verifying emergency kits.

Exam Tip: The goal of error reporting and CQI is system improvement, not punishment. A correct answer about error culture will emphasize a non-punitive, system-focused approach.

Documentation and Record-Keeping for Safety Events

Every error and near miss must be documented so the pharmacy can analyze trends and prove corrective action. Documentation is itself a blueprint knowledge item.

RecordPurpose
Incident/error reportCaptures what happened and when
Near-miss logReveals weak points before harm
Corrective action recordDocuments the fix and follow-up
Adverse event reportSent to MedWatch/FAERS or VAERS

Key Point: Reporting is most effective when it is timely and non-punitive. Trends across many reports reveal system problems a single report would hide.

Sanitation, Cross-Contamination, and the Clean Work Area

Patient safety also depends on a clean dispensing environment. Technicians follow sanitization procedures and steps to avoid cross-contamination, especially when counting drugs that commonly cause allergy or are hazardous.

PracticeWhy It Matters
Dedicated counting tray for penicillin/sulfaPrevents allergen cross-contamination
Routine cleaning of trays and countersReduces residue transfer between drugs
Hand hygiene and PPEProtects staff and patients
Separate equipment for hazardous drugsPrevents hazardous residue spread

Exam Tip: A separate, dedicated counting tray (often cleaned between uses) is the standard safeguard against transferring traces of high-allergy drugs like penicillin to another patient's medication.

Quality-Assurance Inventory Checks

CQI extends to the shelf. Routine QA checks confirm that expired and recalled products are removed, controlled substances are secured, emergency kits are complete and sealed, and returns are processed correctly. These checks close the loop between inventory management and patient safety, ensuring that what reaches the patient is current, correct, and secure.

Worked Example: During a monthly QA check the technician finds an emergency kit with a short-dated epinephrine. They replace it, document the swap, and verify the kit seal, preventing a dangerous gap when the medication is needed urgently.

Tracking and Trending to Prevent Recurrence

A single error tells you little; a trend tells you where the system is weak. Pharmacies aggregate reports to spot patterns such as a recurring LASA mix-up or a particular high-alert drug appearing repeatedly in near misses, then target those points with new safeguards.

Trend SignalLikely System Fix
Repeated LASA confusionTall Man labels, separate storage
Frequent wrong-strength picksBarcode scanning, shelf labeling
Same drug in many near missesAdd to high-alert protocol/double-check
Pickup errorsStrengthen two-identifier verification

Exam Tip: The purpose of aggregating and trending reports is proactive system improvement, the heart of continuous quality improvement, not assigning blame for any single event.

The Technician's Place in the Safety Culture

In a strong safety culture, the technician is encouraged to speak up, stop a questionable fill, and report freely. Because technicians touch nearly every step of the dispensing process, they are often the first to catch a near miss. The ExCPT expects you to choose the answer that reports, documents, and improves the system rather than hiding the event.

Loading diagram...
From Adverse Event to System Improvement
Test Your Knowledge

A patient experiences a serious reaction to a vaccine administered at the pharmacy. This should be reported to:

A
B
C
D
Test Your Knowledge

The purpose of a root cause analysis (RCA) after a medication error is to:

A
B
C
D
Test Your Knowledge

Isotretinoin's iPLEDGE program, which requires registration and pregnancy testing before dispensing, is an example of a:

A
B
C
D
Congratulations!

You've completed this section

Continue exploring other exams