A Quick Explainer on FDA's Consolidated Adverse Events Reporting System
The new Adverse Event Monitoring System (AEMS) consolidates decades of fragmented safety reporting. If your company submits adverse event reports to the FDA, here's the scoop.
On March 11, the FDA launched the Adverse Event Monitoring System, or AEMS. It’s a single, unified platform that replaces the patchwork of reporting databases the agency has relied on for years. By the end of May 2026, every adverse event report across every FDA-regulated product category will flow through this one system.
This is one of the bigger infrastructure changes the FDA has made to its postmarket surveillance program in a while.
Here’s what happened, what’s changing, and what it means if you work in quality, regulatory, or pharmacovigilance.
What AEMS replaces
If you’ve ever filed an adverse event report with the FDA (or tried to search one) you maybe know the frustration. The agency has been running seven separate databases, each built for a different product center, each with its own interface, its own quirks, and its own limitations.
The legacy systems being retired or absorbed include:
Already live in AEMS (as of March 11):
FAERS (FDA Adverse Event Reporting System) — drugs, biologics, cosmetics, and color additives
VAERS (Vaccine Adverse Event Reporting System) — vaccines (co-managed with the CDC; FDA will display VAERS data within AEMS)
AERS (Adverse Event Reporting System) — animal drugs and animal foods
Migrating to AEMS by the end of May 2026:
MAUDE (Manufacturer and User Facility Device Experience) — medical devices
HFCS (Human Foods Complaint System) — human foods and dietary supplements
CTPAE (Center for Tobacco Products Adverse Event Reporting System) — ENDS and other tobacco products
That’s drugs, biologics, vaccines, devices, food, cosmetics, tobacco, and veterinary products all under one “data roof.”
Why this is happening
The FDA says its fragmented reporting infrastructure was expensive, hard to use, and created blind spots in post-market surveillance. By the agency’s own numbers, those seven databases processed roughly 6 million adverse event reports per year and cost approximately $37 million annually to operate.
The new system is expected to save around $120 million over the next five years.
Beyond cost savings, the agency is making a transparency play. AEMS will publish adverse event reports in real time rather than on the quarterly cycle most of the legacy systems followed. The FDA expects this will significantly reduce the volume of FOIA requests for adverse event data, since the information will already be publicly accessible through a searchable dashboard.
The agency also plans to migrate historical data from the legacy systems into AEMS and roll out new APIs and data analytics tools, including, notably, AI-based tools for signal detection, redaction, and digitization.
What this means for the industry
If you’re in pharma, biologics, or medical devices, here are the practical implications worth tracking:
Your reporting workflows may need to change. As AEMS absorbs each legacy system, the submission interfaces and data formats will shift. If your adverse event reporting SOPs reference specific legacy system procedures (and they probably do) start planning for updates. The device side (MAUDE migration) is still a few months out, so device companies have a window to prepare.
The data you submit will be more visible and faster. Real-time publication means your adverse event reports will be publicly searchable much sooner than they were under the old quarterly release model. This has implications for how quickly competitors, plaintiffs’ attorneys, journalists, and patient advocacy groups can access your safety data. Quality and regulatory teams should be aware of this compressed timeline.
Cross-product signal detection gets easier for the FDA and for you. One of the structural problems with the old system was that safety signals spanning multiple product categories were hard to spot because the data lived in siloed databases. A unified platform makes cross-product surveillance possible in a way it wasn’t before. This is particularly relevant for combination products and companies with portfolios spanning drugs and devices.
AI-driven analytics are coming. The FDA has signaled that AI tools will play a role in scanning for safety signals within AEMS. Jeremy Walsh, the agency’s Chief AI Officer, described the rollout as the biggest technical transformation in agency history. For regulated companies, this likely means the agency’s ability to detect patterns and clusters in adverse event data will accelerate, which means your internal signal detection and response capabilities need to keep pace.
The data still has limitations. It’s worth noting — and the FDA itself acknowledges this — that AEMS data carries the same fundamental limitations as the legacy systems it replaces. Reports don’t establish causation! Duplicate and incomplete reports exist! Information hasn’t been independently verified! Occurrence rates can’t be derived from the data alone. The platform is better, but the underlying data quality challenges remain.
A note on real-time publication
Not everyone is enthusiastic about the real-time transparency angle. Peter Pitts, president of the Center for Medicine in the Public Interest and a former FDA associate commissioner, has raised a valid concern to RAPS: releasing raw, unvetted adverse event data to the public in real time risks misinterpretation. Without FDA staff reviewing and contextualizing the reports before publication, there’s a real possibility that patients, media, or advocacy groups draw conclusions the data doesn’t support.
This is the tension at the heart of the AEMS rollout: more transparency is generally good, but raw data without expert interpretation can be misleading, especially in the hands of people who don’t understand the limitations of spontaneous reporting systems.
What to do now
A few action items to think about:
Audit your current AE reporting SOPs for references to legacy systems (FAERS, VAERS, MAUDE, etc.) and flag them for revision as AEMS timelines firm up.
Brief your pharmacovigilance and quality teams on the shift to real-time publication and what that means for your internal review and response timelines.
Monitor the AEMS public dashboard to understand how your product data appears in the new system and whether historical migration introduces any data quality issues you need to address.
Evaluate your signal detection capabilities. If the FDA is layering AI tools on top of a unified data set, your internal surveillance should at least match the rigor of what the agency will now be able to do.
Watch for the May migration deadlines, particularly if you’re in medical devices (MAUDE) or food/dietary supplements (HFCS).
Who is The FDA Group?
The FDA Group helps life science organizations rapidly access the industry's best consultants, contractors, and candidates. Our resources assist in every stage of the product lifecycle, from clinical development to commercialization, with a focus on Quality Assurance, Regulatory Affairs, and Clinical Operations.
With thousands of resources worldwide, hundreds of whom are former FDA, we meet your precise resourcing needs through a fast, convenient talent selection process supported by a Total Quality Guarantee. Learn more and schedule a call with us to see if we’re a fit to help you access specialized professionals and execute your projects on time and on budget.