FDA Adverse Event Reporting: MedWatch and FAERS

FDA adverse event reporting encompasses two interconnected systems — MedWatch and the FDA Adverse Event Reporting System (FAERS) — that together form the backbone of postmarket safety surveillance for drugs, biologics, and medical devices in the United States. This page explains how both systems are defined, how reports move from submission to database entry, which situations trigger mandatory versus voluntary reporting, and where the boundaries of each system's jurisdiction lie. Understanding these mechanisms is essential for healthcare professionals, manufacturers, and patients navigating postmarket safety obligations under FDA authority.

Definition and scope

Adverse event reporting under FDA jurisdiction is the formal process by which information about harmful or unexpected outcomes associated with medical products — including prescription drugs, biologics, over-the-counter drugs, dietary supplements, cosmetics, and medical devices — reaches the agency for analysis and regulatory action.

MedWatch is the FDA's Safety Reporting Portal, established under authority granted by the FDA Safety and Innovation Act. It serves as the submission front end, accepting both mandatory reports from industry and voluntary reports from healthcare professionals and consumers via Form FDA 3500 (voluntary) and Form FDA 3500A (mandatory).

FAERS — the FDA Adverse Event Reporting System — is the downstream database where submitted reports are stored, coded, and made available for public query. FAERS replaced the earlier AERS database and holds millions of individual case safety reports. As of data published by the FDA FAERS Public Dashboard, the database contained over 29 million reports as of 2023. FAERS uses the Medical Dictionary for Regulatory Activities (MedDRA) coding system to standardize terminology across reports.

The statutory authority governing adverse event reporting for drugs derives primarily from 21 C.F.R. Part 314 for new drug applications and 21 C.F.R. Part 600 for biologics. Device adverse event reporting operates under 21 C.F.R. Part 803, which governs Medical Device Reporting (MDR) requirements.

How it works

The reporting pipeline from initial observation to database entry follows a structured sequence:

  1. Event observation — A patient, caregiver, healthcare professional, or manufacturer observes an adverse outcome potentially associated with a regulated product.
  2. Report submission — Voluntary reporters submit via MedWatch Form FDA 3500; mandatory reporters (manufacturers, importers, device user facilities) submit via Form FDA 3500A, either electronically through the FDA Electronic Submissions Gateway or in paper format.
  3. Receipt and triage — FDA staff receive and screen reports for completeness. Expedited 15-day reports — required for serious and unexpected drug adverse events under 21 C.F.R. § 314.81 — are prioritized.
  4. MedDRA coding — Events are coded using standardized MedDRA terminology to enable cross-database analysis.
  5. FAERS entry and signal detection — Coded reports enter the FAERS database. FDA uses data mining algorithms, including the Empirical Bayes Geometric Mean (EBGM) method, to detect disproportionality signals — statistical patterns suggesting a product-event association stronger than background rates.
  6. Regulatory action assessment — Detected signals are evaluated by the FDA Center for Drug Evaluation and Research (CDER) or Center for Biologics Evaluation and Research (CBER), potentially resulting in label changes, Risk Evaluation and Mitigation Strategies (REMS), or product withdrawal.

FAERS data is publicly accessible through the FAERS Public Dashboard and through quarterly downloadable files, enabling independent pharmacovigilance research.

Common scenarios

Adverse event reports arise across a range of product categories and reporter types. The most frequent scenarios include:

For broader context on how adverse event reporting connects to the full FDA enforcement and oversight framework, reviewing the agency's postmarket surveillance programs alongside premarket approval pathways provides a complete picture of the product safety lifecycle.

Decision boundaries

The most consequential distinction in adverse event reporting is between mandatory and voluntary reporting obligations, which vary by reporter type and product category.

Mandatory reporters include:
- Prescription drug and biologic manufacturers, applicants, and license holders
- Medical device manufacturers, importers, and user facilities (hospitals, nursing homes)
- Dietary supplement manufacturers (for serious adverse events only, under 21 U.S.C. § 379aa-1)

Voluntary reporters include:
- Healthcare professionals (physicians, pharmacists, nurses)
- Patients and consumers
- Lawyers and other third parties with product safety information

A second critical boundary separates serious from non-serious adverse events, which determines reporting timelines:

Event type Drug/biologic timeline Device timeline
Serious and unexpected 15 calendar days (expedited) 30 calendar days
Serious requiring immediate remedial action 15 calendar days 5 calendar days
Non-serious Periodic (quarterly/annual) reports Not required via MDR
Death or serious injury (device user facility) 10 calendar days to manufacturer and FDA

A third boundary concerns device user facilities — defined under 21 C.F.R. § 803.3 as hospitals, ambulatory surgical facilities, nursing homes, outpatient diagnostic and treatment facilities, and outpatient treatment facilities — which carry MDR reporting obligations distinct from those of manufacturers. Physician offices are explicitly excluded from the user facility definition under 21 C.F.R. § 803.3.

FAERS data carries a documented limitation: it cannot establish causality between a product and an adverse event, and submission rates are not uniform across products or reporter populations. FDA guidance consistently notes that FAERS report volume alone does not indicate incidence rates or product risk levels — a caveat that shapes how signal detection outputs are interpreted in postmarket safety reviews. The fda-enforcement-actions-and-recalls page details how confirmed signals translate into regulatory enforcement steps.