FDA adverse event data can help researchers and other data users examine reported experiences involving drugs and biologic products. The information can support safety surveillance, but it requires careful interpretation. A report records an event reported to the U.S. Food and Drug Administration (FDA); it does not, by itself, establish that a product caused the event.
The FDA is transitioning adverse-event handling from the FDA Adverse Event Reporting System (FAERS) to the FDA Adverse Event Monitoring System (AEMS). The FDA page presents the public dashboard as the AEMS Public Dashboard, formerly FAERS. Because terminology and published materials can change, consult the FDA page for current information.
For anyone working with public healthcare data, the central discipline is to distinguish what a report contains from what it can support as an analytical conclusion.
Table of contents
- What FAERS Reports Represent
- How Drug Safety Reports Are Used in Practice
- A Practical Way to Read One Record
- FAERS and AEMS: Understanding the Transition
- Working with the Data in QOPE
- Limitations That Shape Responsible Analysis
- FAQ
- Explore Adverse Event Records in QOPE
What FAERS Reports Represent
FAERS reports are spontaneous safety reports submitted to the FDA by pharmaceutical industry representatives, healthcare providers, consumers, and other members of the public. The current AEMS dashboard describes information about human adverse events reported to the FDA for drug and biologic products.
A report may include:
- Case identifier and report identifier
- Report type and report source
- Drug and active ingredient
- Route
- Reaction
- Outcome
- Patient demographics
- Country
- Received date
These fields describe the submitted report and its context. They do not turn a report into a confirmed clinical finding. The FDA states that the information reflects the reporter’s observations and opinions. The agency also notes that submitted information has not necessarily been medically verified.
This distinction matters when using FAERS reports or AEMS records for research. Adverse event reporting brings possible safety issues to the FDA’s attention. It is not the same as a controlled clinical study or a system that measures the frequency of an event among every person using a product.
How Drug Safety Reports Are Used in Practice
Researchers can use these reports to identify patterns that may warrant further investigation. For example, analysts may examine reported reactions alongside the named drug, active ingredient, outcome, report source, country, and received date. Reviewing several fields together provides more context than looking at a product name or reaction alone.
A report source helps characterize who submitted the information. The outcome field describes the reported result associated with the case. Patient demographics and country provide recorded context, while the received date places the report within the FDA’s reporting timeline. The drug and active ingredient fields distinguish the named product from the substance identified in the report.
These fields are descriptive evidence about the report, not proof of a biological or clinical relationship. A report involving a drug may reflect an underlying disease, another product taken at the same time, or another cause. The FDA specifically states that the existence of a report does not establish causation.
Duplicate and incomplete reports can occur. A single safety concern may therefore appear in more than one submission, while another report may lack important details. Researchers should understand how the FDA describes the data before drawing conclusions.
A report may support signal detection, hypothesis generation, and contextual research. It cannot independently establish how often an event occurs among product users. Report totals are not incidence rates because these reports alone do not provide the number of people exposed or the full number of events that occurred.
A Practical Way to Read One Record
Consider a single record whose fields identify a drug, an active ingredient, a reaction, an outcome, a report source, a country, patient demographics, and a received date. Suppose the drug field names a product, the active ingredient field identifies the substance, and the reaction field describes an adverse event reported by the submitter.
A careful reading can say:
- The drug field indicates which product was named in the report.
- The active ingredient field identifies the ingredient associated with that product entry.
- The reaction field records the event described by the reporter.
- The outcome field provides the reported outcome associated with the case.
- The report source indicates the source category for the submission.
- The country and patient-demographic fields provide the context recorded for the patient or report.
- The received date places the submission in the FDA’s reporting timeline.
Taken together, these fields support a statement such as: a report was submitted to the FDA describing a reaction in a patient associated in the report with a named drug and active ingredient, along with a reported outcome and contextual information.
The same record does not establish that the drug caused the reaction. It does not show that the reaction would not have occurred without the drug. It does not establish that the drug was the only product involved, that the information was medically confirmed, or that the record represents a unique patient or event. It also does not provide the denominator needed to calculate the rate of the reaction among people who used the product.
The case identifier and report identifier help organize and distinguish the case or submission represented in the dataset. They are not evidence of causation, clinical confirmation, or a unique exposed population. If duplicate reports are present, counting identifiers without understanding the source data can overstate the apparent number of reports.
Related fields should therefore be read together. A drug name alone provides less context than the drug, active ingredient, reaction, outcome, source, and date considered as one report. Even then, the result remains a description of submitted safety information rather than a causal conclusion.
FAERS and AEMS: Understanding the Transition
The FDA is implementing AEMS to consolidate multiple reporting systems used across FDA-regulated product categories. The FDA describes AEMS as covering medical products, vaccines, devices, tobacco, food, cosmetics, and veterinary medicines. The system also has a broader role that includes consumer complaints, regulatory misconduct reports, and whistleblower submissions.
For readers accustomed to the term FAERS, this transition is important. The FDA page labels the public dashboard “FDA Adverse Event Monitoring System (AEMS) Public Dashboard” and identifies it as formerly FAERS. References to FAERS reports may therefore appear alongside current AEMS terminology, depending on the material being reviewed.
The FDA page states that the AEMS Public Dashboard is intended to expand public access to information about human adverse events reported to the FDA. It also describes the dashboard as a tool for querying AEMS data. The page is marked current as of March 11, 2026. Consult the FDA site for current dashboard status, terminology, and published materials before beginning a new analysis.
Working with the Data in QOPE
QOPE brings selected public healthcare datasets into a more accessible environment. On QOPE’s Adverse Events page, the available field categories include case identifier, report identifier, report type, report source, drug, active ingredient, route, reaction, outcome, patient demographics, country, and received date.
These fields can help users orient themselves when reviewing structured adverse event information. QOPE organizes information from authoritative public sources, while the FDA remains the original public source for official verification and current documentation. Users should consult the original FDA source when they need to confirm definitions, limitations, current terminology, or the status of published materials.
A practical workflow begins with a research question that matches the information represented in the dataset. Questions about the content of submitted reports differ from questions about incidence, comparative risk, or clinical causation. The latter require additional study designs, exposure information, clinical context, and methods beyond an adverse event reporting dataset.
Limitations That Shape Responsible Analysis
The FDA states that the existence of a report does not establish causation. A reported event may relate to the underlying disease, another drug taken concurrently, or another reason. The submission is not a medical confirmation or an admission that the drug caused or contributed to the event.
Duplicate and incomplete reports can occur. Researchers should therefore avoid treating every visible report as an independent, fully documented patient experience. Missing information can affect interpretation, while duplicative submissions can affect simple counts.
Report data cannot establish occurrence rates. A count of reports does not reveal the incidence of an event among all users of a drug because the dataset does not, by itself, provide the complete exposed population or all events that occurred. The absence of a report also does not prove that a product is safe.
These limitations define the type of question the data can support. The records are most appropriately read as reports of observations and opinions submitted to the FDA, useful for surveillance and further investigation but insufficient on their own for causal or rate-based conclusions.
FAQ
What Are FAERS Reports?
FAERS reports are spontaneous adverse event reports submitted to the FDA by sources including pharmaceutical industry representatives, healthcare providers, consumers, and other members of the public. The current FDA public dashboard is presented under the AEMS name.
Does an Adverse Event Report Prove That a Drug Caused an Event?
No. The FDA states that the existence of a report does not establish causation, and the information may not have been medically verified.
Can Researchers Calculate Adverse Event Incidence from These Records?
No. The FDA states that occurrence rates cannot be established from the reports alone.
Is FAERS Still the Current Name?
The FDA is transitioning adverse-event handling to AEMS. The FDA’s public page identifies the AEMS Public Dashboard as formerly FAERS. Check the FDA page for current terminology and published materials.
Explore Adverse Event Records in QOPE
QOPE helps users explore structured public healthcare data through selected datasets from authoritative public sources.
QOPE is not affiliated with CMS, the FDA, or any government agency. QOPE organizes selected public healthcare data and does not replace official sources.