FDA AEMS Guide (2026): MAUDE Replacement & Adverse Event Search

FDA AEMS Guide (2026): Everything Medical Device Teams Need to Know

On March 11, 2026, the U.S. Food and Drug Administration announced the launch of the Adverse Event Monitoring System (AEMS) — a unified platform for analyzing and publishing adverse event reports across FDA-regulated product categories. For medical device teams, the headline is simple: the fragmented public look-up experience associated with MAUDE and other center-specific databases is being consolidated into one modernization program.

This article sticks to what FDA has stated publicly (especially the March 11, 2026 news release and FDA AEMS topic pages) and translates that into practical monitoring guidance. Where details are still evolving (exact API contracts, exact decommission dates for every interface), we say so rather than invent endpoints or features.

What Is AEMS?

AEMS is FDA’s consolidated adverse event monitoring / look-up system. FDA describes it as consolidating multiple disparate reporting and publication systems used across product categories — including medical products, vaccines, devices, tobacco, food, cosmetics, and veterinary medicines — into a more unified architecture.

In the March 11, 2026 news release, FDA framed AEMS as:

• a single, more intuitive platform for agency scientists, researchers, and the public
• a path to real-time publication of adverse event reports (subject to privacy rules against releasing individually identifiable patient/consumer information)
• a modernization that should reduce the friction of searching outdated, fragmented systems

FDA also stated that AEMS will serve as a centralized platform not only for adverse event reports but, over time, for related safety intelligence workflows described on FDA AEMS pages (including case processing modernization and analytics). Treat product-center pages as the source of truth as features roll out.

Why FDA Built It (Numbers FDA Published)

According to the March 11, 2026 FDA news release:

• The agency historically processed about 6 million adverse event reports per year across a patchwork of seven databases.
• Those platforms collectively cost approximately $37 million per year to operate.
• With AEMS efficiencies, FDA expects to save approximately $120 million over five years.
• Real-time publication is expected to reduce FOIA demand for unreleased adverse event reports that previously sat behind slower release cycles.

Commissioner Marty Makary’s quote in the release emphasized that prior systems were “outdated and fragmented,” wasted money, and created blind spots across product types. Chief AI Officer Jeremy Walsh called the delivery schedule aggressive and described AEMS as a major technical transformation for the agency.

These figures are FDA’s own projections and cost estimates, not third-party audits. Use them as context for why the agency is forcing consolidation — not as guarantees about your internal monitoring costs.

Launch Scope vs Later Product Centers

This is the most common place industry blogs over-claim. FDA’s March 11 release was explicit about phasing:

Available / displayed at launch (March 11, 2026)

Adverse event reports submitted for:

• drugs
• biologics
• vaccines (with a VAERS note — see below)
• cosmetics
• animal food

(Animal drugs are addressed via the AERS consolidation path described in the same release.)

could be displayed in a single streamlined dashboard at launch.

To be brought in next (FDA: “in May” / “by the end of May 2026”)

FDA listed legacy systems to be replaced by AEMS in May including:

• 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

FDA also stated that by the end of May 2026, AEMS would contain real-time adverse event reports for all FDA-regulated products, consistent with privacy obligations.

Legacy systems called out as replaced “now” (at the March announcement)

The release listed systems already in the consolidation path at announcement time, including:

• FAERS — drugs, biologics, cosmetic products, and color additives (as described in the release)
• VAERS — vaccines; FDA will display VAERS data in AEMS; VAERS remains co-managed by FDA and CDC
• AERS — animal drugs and animal foods (FDA’s wording in the release for the animal systems consolidated on the “now” path)

Device-team takeaway: Do not write SOPs that claim “on March 11 every MAUDE record was already in AEMS.” FDA’s own launch narrative put device/MAUDE migration in the May wave. By August 2026 you should verify current public dashboard coverage for your product codes rather than relying on launch-day assumptions. Note also that submission systems (for example eMDR pathway communications) and public look-up cutovers may not share a single calendar day — track the specific FDA page your process depends on.

What About MAUDE Specifically?

Yes — FDA identified MAUDE as a legacy system to be replaced by AEMS as part of the May wave in the March 11, 2026 announcement.

What that means operationally:

1. Public look-up for device adverse events is intended to move to the AEMS experience rather than the old MAUDE-centric access path.
2. Historical data migration is part of the program (FDA said it will migrate historical adverse event data to AEMS). Exact field-for-field mapping and how long dual access paths remain available can change — confirm on current FDA AEMS / device pages.
3. Mandatory reporting rules under 21 CFR Part 803 (Medical Device Reporting) are not rewritten by a database modernization announcement. Manufacturers, importers, and user facilities still have the same core obligations and timelines unless FDA separately amends those regulations or guidance.

For how to search and interpret device reports in the pre-AEMS / transitional mental model, see our deeper FDA MAUDE database guide. Update internal bookmarks and training to the current FDA AEMS public dashboard URLs published on fda.gov.

What Stays the Same for Regulatory Obligations

AEMS is primarily a systems and transparency modernization. For most RA/QA workflows:

• Who must report device deaths, serious injuries, and malfunctions under Part 803 remains a regulatory question, not a UI question.
• Report content expectations (what you know, when you know it, follow-ups) still flow from regulation and guidance.
• Recall / correction / removal processes remain distinct from adverse event database look-up (see recall monitoring and recall classification).
• Combination products still require careful thinking about which center and which report type applies — unification of publication does not erase classification complexity.

What Actually Changes for Monitoring Teams

1. One primary public look-up surface (goal state)

Instead of teaching new hires five different adverse event websites, FDA’s direction is a unified dashboard with progressive product-center coverage.

2. Faster public visibility (FDA’s stated intent)

FDA contrasts real-time publication with older quarterly or lagged release patterns for some data. For signal detection, fresher public data can shorten the gap between industry awareness and public awareness — which raises the bar for how quickly you triage competitor and portfolio signals.

3. Cross-product visibility (especially combination products)

A long-standing pain point was correlating device-side and drug/biologic-side narratives for combination products. A unified platform is designed to reduce that blind spot. You still need disciplined search strategies (brand names, product codes, manufacturers, date ranges).

4. APIs and analytics (directional — verify before you code)

FDA’s March release said the agency will roll out enhanced APIs and data analytics tools as part of the program. That is not the same as documenting a stable public OpenAPI contract in a blog post.

Do this instead of trusting third-party sample URLs:

1. Use official FDA AEMS pages and developer communications for current access methods.
2. If you automate, design adapters behind an interface so endpoint and schema changes do not rewrite your whole QMS tool chain.
3. Keep openFDA device event integrations on a deprecation watch until FDA publishes a clear retirement schedule for any endpoints you depend on.
4. Validate any third-party monitoring vendor (including MedFlux) on data continuity for your product codes across the transition.

We intentionally do not publish unverified example aems.fda.gov query strings or webhook specs here. Invented API examples are a common source of bad SOPs.

Practical Checklist for Device Manufacturers (August 2026)

People and process

• Update PMS / complaint / signal-detection SOPs to name AEMS as the primary FDA public adverse event look-up destination going forward (confirm current MAUDE file/dashboard availability on fda.gov for any process that still depends on legacy downloads).
• Retrain staff who still only know the legacy MAUDE UI.
• Add AEMS review cadence to management review inputs for high-risk products.
• Align AR/importer communication so global teams are not searching retired bookmarks.

Data and systems

• Confirm current coverage for your product codes and manufacturers in the live AEMS public dashboard.
• Inventory every automation that hits openFDA /device/event or scrapes MAUDE pages.
• Require vendors to document AEMS vs legacy source mapping and downtime runbooks.
• Preserve historical analyses with legacy identifiers (for example MDR report keys) and map them when FDA provides cross-reference fields.

Quality system links

• Ensure CAPA and Risk Management procedures accept AEMS/public AE outputs as potential inputs.
• Connect AE monitoring to recall monitoring — AE clusters and corrections/removals often move together.
• For EU dual-market products, remember EUDAMED Vigilance module status is a separate timeline from FDA AEMS (see EUDAMED guide).

AEMS vs MAUDE (Conservative Comparison)

Topic	MAUDE (legacy public device database)	AEMS (FDA 2026 modernization)
Primary focus historically	Medical device adverse event reports	Multi-center adverse event monitoring / look-up
FDA March 2026 statement	Listed among systems to be replaced in the May wave	Unified platform launched March 11, 2026
Public access goal	Center-specific, older UX	Single streamlined dashboard
Publication cadence (FDA intent)	Often lagged / batch-oriented in practice	Real-time publication goal for regulated products
Cost narrative	Part of ~$37M/year multi-system spend (FDA)	Expected multi-year savings (~$120M / 5 years, FDA)
Reporting law	Fed by MDR and other report streams	Same underlying reporting obligations unless separately changed

Frequently Asked Questions

What does AEMS stand for?

Adverse Event Monitoring System — FDA’s unified platform for adverse event report analysis and public look-up modernization.

When did AEMS launch?

FDA announced the launch on March 11, 2026.

Does AEMS replace MAUDE?

FDA stated that MAUDE is among the legacy systems to be replaced by AEMS (May wave in the March 11, 2026 release). Confirm operational cutover details on current FDA pages for the interfaces your team uses.

Did AEMS include devices on day one?

At launch, FDA highlighted drugs, biologics, vaccines, cosmetics, and animal food on the unified dashboard, with remaining product centers (including devices via MAUDE) described as following in the subsequent months, with an end-of-May 2026 goal for real-time reports across all FDA-regulated products.

Do MDR reporting obligations change because of AEMS?

Not by default. Database modernization does not itself rewrite 21 CFR Part 803. Continue to follow the regulation and applicable guidance for reporting responsibilities and timelines.

Is VAERS gone?

FDA said it will display VAERS data in AEMS and noted that VAERS is co-managed by FDA and CDC. Do not assume CDC/FDA vaccine safety processes disappear; assume publication and access paths are what AEMS primarily unifies.

Where do I find the official AEMS dashboard?

Start from FDA’s official AEMS pages under fda.gov (Safety / Drugs surveillance sections link the public dashboard). Prefer fda.gov links over third-party mirrors.

How MedFlux Fits

Building and maintaining a reliable multi-source adverse event pipeline — AEMS public data, historical MAUDE continuity, recalls, and non-US vigilance — is expensive for most RA teams. MedFlux monitors FDA safety and regulatory sources alongside 27 regulators so teams can focus on triage and CAPA, not scraper maintenance. Pair this article with the MAUDE guide and free FDA recall lookup.

Primary Sources

• FDA news release (March 11, 2026): FDA Launches New Adverse Event Look-Up Tool
• FDA AEMS topic pages on fda.gov (Safety / Drugs surveillance — confirm current dashboard links)
• 21 CFR Part 803 — Medical Device Reporting (reporting obligations)

Related Resources

• FDA MAUDE Database Guide — Device AE search workflows and transition notes
• FDA Recall Monitoring — Corrections, removals, and recall databases
• FDA Recall Classification — Class I / II / III explained
• FDA QMSR 2026 Guide — Quality system inspection changes (postmarket quality context)
• FDA Recall Lookup Tool — Free firm/product recall search
• Glossary: AEMS | MAUDE | Adverse Event