The FDA Adverse Event Reporting System (FAERS) is a computerized information database designed to support the FDA's post-marketing safety surveillance program for all approved drug and therapeutic biologic products. It contains Individual Case Safety Reports (ICSRs) submitted by healthcare professionals, consumers, and manufacturers, capturing adverse events, medication errors, and product quality complaints.
Glossary
FAERS

What is FAERS?
The FDA Adverse Event Reporting System is a publicly accessible database containing millions of spontaneous adverse event and medication error reports submitted to the U.S. Food and Drug Administration.
Pharmacovigilance professionals and data scientists mine FAERS using disproportionality analysis algorithms—such as the Proportional Reporting Ratio (PRR) and Empirical Bayes Geometric Mean (EBGM)—to detect statistical associations between drugs and adverse events. These quantitative safety signals then undergo rigorous clinical review and signal validation to determine if a true causal relationship exists.
Key Features of FAERS
The foundational database for post-market drug safety surveillance, containing millions of spontaneous reports that enable signal detection and regulatory action.
Spontaneous Reporting Architecture
FAERS operates as a passive surveillance system that accepts voluntary adverse event and medication error reports from:
- Healthcare professionals (physicians, pharmacists, nurses)
- Consumers (patients, caregivers)
- Manufacturers (mandatory reporting for marketed products)
Reports are submitted via the MedWatch program using Form FDA 3500 (voluntary) or Form FDA 3500A (mandatory for manufacturers). The database contains over 2 million individual case safety reports as of 2024, growing by approximately 1.5-2 million reports annually.
Structured Data Elements
Each FAERS report captures standardized safety information using the ICH E2B (R3) electronic transmission format, including:
- Patient demographics: age, sex, weight (when available)
- Drug information: suspect and concomitant medications with dosage, route, and therapy dates
- Adverse events: coded using MedDRA preferred terms at multiple seriousness levels
- Outcomes: death, life-threatening, hospitalization, disability, congenital anomaly, other serious
- Reporter information: occupation, country, report source
The structured nature enables systematic disproportionality analysis across drug-event combinations.
Quarterly Data Extract Files
FAERS data is publicly released as quarterly ASCII or XML extract files containing:
- DEMO: patient demographic and administrative information
- DRUG: medication details including drug characterization (suspect, concomitant, interacting)
- REAC: adverse event reactions coded to MedDRA preferred terms
- OUTC: patient outcomes for each event
- RPSR: report source information
- THER: drug therapy start and end dates
- INDI: indication for drug use coded to MedDRA
These flat files require significant data normalization and deduplication before analysis due to follow-up reports and multiple submission pathways.
Signal Detection Methodology
FAERS serves as the primary data source for quantitative signal detection using disproportionality algorithms:
- Empirical Bayes Geometric Mean (EBGM): Bayesian shrinkage method using the Multi-item Gamma Poisson Shrinker (MGPS) algorithm
- Proportional Reporting Ratio (PRR): Frequentist measure comparing observed-to-expected reporting rates
- Reporting Odds Ratio (ROR): Case-non-case analysis for drug-event associations
FDA safety reviewers use these statistical scores alongside clinical case review to identify potential safety signals that warrant further investigation through the Signal Management Process.
Limitations and Caveats
Critical limitations must be considered when analyzing FAERS data:
- Underreporting: Estimated that only 1-10% of adverse events are reported
- No denominator data: Cannot calculate true incidence rates without exposure data
- Duplicate reports: Follow-up submissions create duplicate records requiring deduplication
- Confounding by indication: The underlying disease may cause the event, not the drug
- Stimulated reporting: Media attention or litigation can artificially inflate reporting rates
- No causality verification: Reports do not establish causation; they represent suspected associations
These limitations necessitate complementary data sources like Sentinel and claims databases for comprehensive safety assessment.
FAERS vs. Other Pharmacovigilance Databases
A feature-level comparison of the FDA Adverse Event Reporting System against the European EudraVigilance and WHO VigiBase global safety databases.
| Feature | FAERS | EudraVigilance | VigiBase |
|---|---|---|---|
Governing Body | U.S. FDA | European Medicines Agency | WHO (Uppsala Monitoring Centre) |
Primary Jurisdiction | United States | European Economic Area | Global (140+ member countries) |
Report Submission Standard | ICH E2B (R3) | ICH E2B (R3) | ICH E2B (R2/R3) |
Public Data Access | |||
Total ICSRs (approx.) |
|
|
|
Disproportionality Metric | EBGM (MGPS) | ROR | IC (BCPNN) |
Suspected Duplicate Detection | Automated deduplication | Automated deduplication | VigiMatch algorithm |
Direct Consumer Reporting |
Frequently Asked Questions
Concise answers to common technical questions about the structure, statistical methods, and strategic use of the FDA Adverse Event Reporting System for pharmacovigilance signal detection.
The FDA Adverse Event Reporting System (FAERS) is a publicly accessible, passive surveillance database containing millions of spontaneous Individual Case Safety Reports (ICSRs) and medication error reports submitted to the U.S. Food and Drug Administration. It functions as a post-market safety monitoring tool. Reports are submitted by healthcare professionals, consumers, and manufacturers. The database supports disproportionality analysis by allowing safety scientists to compare the observed reporting frequency of a specific drug-event combination against a statistical background of all other drugs and events in the system. Data is structured around the ICH E2B (R3) standard, mapping to the Medical Dictionary for Regulatory Activities (MedDRA) terminology for standardized coding.
Enabling Efficiency, Speed & Accuracy
Intelligent Analysis, Decision & Execution
We build AI systems for teams that need search across company data, workflow automation across tools, or AI features inside products and internal software.
Talk to Us
Search across company data
Give teams answers from docs, tickets, runbooks, and product data with sources and permissions.
Useful when people spend too long searching or get different answers from different systems.

Automate internal workflows
Use AI to route work, draft outputs, trigger actions, and keep approvals and logs in place.
Useful when repetitive work moves across multiple tools and teams.

Add AI to products and internal tools
Build assistants, guided actions, or decision support into the software your team or customers already use.
Useful when AI needs to be part of the product, not a separate tool.
Related Terms
Mastering FAERS requires understanding the statistical methods, regulatory standards, and data formats that transform raw adverse event reports into actionable safety intelligence.
Disproportionality Analysis
The core statistical engine for signal detection within FAERS. This methodology quantifies whether a specific drug-event pair is reported more frequently than expected by chance.
- Proportional Reporting Ratio (PRR): A frequentist measure comparing observed vs. expected reporting rates.
- Reporting Odds Ratio (ROR): Calculates the odds of an event being reported with a specific drug versus all other drugs.
- Empirical Bayes Geometric Mean (EBGM): A Bayesian metric that applies shrinkage to correct for instability in low-count pairs, reducing false positives.
MedDRA
The Medical Dictionary for Regulatory Activities is the standardized international terminology used to code adverse event reports in FAERS. It provides a hierarchical structure for precise medical encoding.
- Structure: Five levels from System Organ Class (SOC) down to Lowest Level Terms (LLT).
- Purpose: Enables consistent aggregation and retrieval of safety data across global regulatory submissions.
- Standardised MedDRA Queries (SMQs): Pre-defined groupings of terms designed to identify cases related to specific syndromes, such as anaphylactic reaction or acute pancreatitis.
E2B (R3) Transmission Standard
The ICH E2B (R3) standard defines the electronic format for transmitting Individual Case Safety Reports (ICSRs) to databases like FAERS. It ensures structured, interoperable data exchange.
- Format: XML-based messaging using HL7 ICSR standards.
- Content: Encodes patient demographics, suspect drugs, adverse events, and medical history in a machine-readable schema.
- Automation: Enables pharmaceutical companies to submit thousands of reports programmatically, eliminating manual data entry errors.
Signal Validation & Causality
A statistical association in FAERS does not equal a causal link. Signal validation is the rigorous process of confirming a new safety finding.
- Causality Assessment: Evaluates the likelihood that a drug caused an event using factors like temporal relationship and dechallenge/rechallenge data.
- Confounding by Indication: A critical bias where the treated disease, not the drug, causes the event. Disentangling this requires clinical review.
- Seriousness Criteria: Events are classified as 'serious' if they result in death, hospitalization, disability, or congenital anomaly.
Global Safety Databases
FAERS is part of a global ecosystem of spontaneous reporting databases. Cross-referencing these systems strengthens signal detection.
- EudraVigilance: The European Medicines Agency's centralized database for adverse reactions within the European Economic Area.
- VigiBase: The WHO's global ICSR repository, maintained by the Uppsala Monitoring Centre, containing over 30 million reports.
- Data Mining: Modern pharmacovigilance applies NLP to simultaneously mine these databases alongside unstructured literature and social media for emerging safety signals.

About the author
Prasad Kumkar
CEO & MD, Inference Systems
Prasad Kumkar is the CEO & MD of Inference Systems and writes about AI systems architecture, LLM infrastructure, model serving, evaluation, and production deployment. Over 5+ years, he has worked across computer vision models, L5 autonomous vehicle systems, and LLM research, with a focus on taking complex AI ideas into real-world engineering systems.
His work and writing cover AI systems, large language models, AI agents, multimodal systems, autonomous systems, inference optimization, RAG, evaluation, and production AI engineering.
Partnered with leading AI, data, and software stack.
How We Work
Custom AI workflows for your Business
One-fit-all AI don't work for modern businesses. At Inferensys, we aim to understand your business & custom requirements; which we use to define most efficient agentic workflows, the data, and the tools for your business.
01
Review the use case
We understand the task, the users, and where AI can actually help.
Read more02
Pick the right approach
We define what needs search, automation, or product integration.
Read more03
Build the first useful version
We implement the part that proves the value first.
Read more04
Improve from there
We add the checks and visibility needed to keep it useful.
Read moreThe first call is a practical review of your use case and the right next step.
Talk to Us