FDA AEMS: The Adverse Event Monitoring System That Replaces MAUDE, FAERS, and 5 Other Databases

On March 11, 2026, the FDA launched the Adverse Event Monitoring System (AEMS) — the most significant overhaul of the agency's safety surveillance infrastructure in over two decades. AEMS consolidates seven legacy adverse event databases into a single, unified platform covering every product category the FDA regulates: drugs, biologics, vaccines, medical devices, cosmetics, human foods, and animal drugs.

The transition is not optional. By the end of May 2026, the legacy systems — including MAUDE, FAERS, and VAERS — will be decommissioned. If your organization monitors adverse events for any FDA-regulated product, you need to understand what AEMS changes, what stays the same, and how to prepare your workflows before the cutover completes.

This guide covers everything regulatory affairs professionals, quality engineers, and post-market surveillance teams need to know about the FDA AEMS transition.

What Is AEMS and Why the FDA Built It

AEMS is a centralized adverse event reporting and monitoring platform operated by the FDA. It replaces seven separate databases that were built independently over the past 20–30 years, each serving a different product category and maintained by different FDA centers.

The fundamental problem AEMS solves is fragmentation. Under the legacy architecture, a safety signal involving a drug-device Combination Product might generate reports in both MAUDE (for the device component) and FAERS (for the drug component). Those reports lived in separate databases, with separate search interfaces, separate APIs, and separate update schedules. Cross-referencing required manual effort or custom integrations.

AEMS eliminates that fragmentation. Every adverse event report — regardless of product type — now flows into a single system with a unified data model, a single search interface, and a single API.

The Cost Problem

The seven legacy databases collectively cost the FDA approximately $37 million per year to operate and maintain. Each system had its own infrastructure, its own development team, and its own maintenance cycle. Redundant effort was substantial — security patches, compliance updates, and infrastructure upgrades had to be applied independently to each system.

The FDA projects that AEMS will save approximately $120 million over five years through infrastructure consolidation, reduced headcount for database administration, and elimination of duplicated development work.

The Data Problem

Beyond cost, the legacy systems created data silos that actively hindered safety surveillance. A safety signal that spanned product categories — such as an adverse interaction between a medical device and a biologic — required analysts to query multiple databases separately and manually correlate the results. AEMS makes cross-product signal detection possible within a single query.

The 7 Legacy Systems Being Replaced

AEMS consolidates the following seven FDA adverse event databases:

Database	Full Name	Product Scope	FDA Center
MAUDE	Manufacturer and User Facility Device Experience	Medical devices	CDRH
FAERS	FDA Adverse Event Reporting System	Drugs (prescription and OTC)	CDER
VAERS	Vaccine Adverse Event Reporting System	Vaccines	CBER (joint with CDC)
HFCS	Human Food Complaints System	Human foods and dietary supplements	CFSAN
CTPAE	Center for Tobacco Products Adverse Experience	Tobacco and nicotine products	CTP
CAERS	CFSAN Adverse Event Reporting System	Cosmetics and dietary supplements	CFSAN
AVRS	Animal Veterinary Reporting System	Animal drugs and feed	CVM

Each of these systems was purpose-built for its product category. MAUDE was optimized for medical device reports with fields for product codes, device classifications, and PMA/510(k) numbers. FAERS was structured around drug names, NDC codes, and indications. VAERS tracked vaccine lot numbers and administration sites. The data models were fundamentally different.

AEMS introduces a unified data model that accommodates all product categories while preserving the category-specific fields that each community requires. Medical device professionals will still find product codes, device classifications, and MDR report keys in AEMS — the data is restructured, not discarded.

Timeline: March 2026 Launch to May 2026 Full Transition

The AEMS rollout follows a phased approach:

Phase	Date	Milestone
Phase 1: Launch	March 11, 2026	AEMS goes live with real-time ingestion from all 7 source systems
Phase 2: Parallel Operation	March–May 2026	Both AEMS and legacy systems operational; data flows to both
Phase 3: Legacy Redirect	Late May 2026	Legacy interfaces redirect to AEMS; legacy APIs return deprecation headers
Phase 4: Decommission	End of May 2026	Legacy systems taken offline; AEMS becomes sole platform

During the parallel operation phase (March through May 2026), both the old and new systems are receiving data. This is the window for organizations to validate that their monitoring pipelines produce consistent results from AEMS before the legacy systems go dark.

If you have not started validating your AEMS integration, the window is closing. The end-of-May decommission deadline is firm.

Historical Data Migration

All historical records from the seven legacy databases have been migrated into AEMS. This includes the full MAUDE archive dating back to the 1990s, the complete FAERS dataset, and historical records from all other systems. Legacy report identifiers (MDR Report Keys for MAUDE, ISR numbers for FAERS, VAERS IDs) are preserved as cross-reference fields in AEMS, so existing analyses and bookmarks can be mapped to the new system.

What Changes vs. What Stays the Same

What Changes

Aspect	Legacy Systems	AEMS
Number of databases	7 separate systems	1 unified platform
Search interface	Separate web UI per database	Single unified search
Update frequency	Varied (monthly for MAUDE, weekly for FAERS)	Real-time for all product types
Cross-product queries	Not possible without manual correlation	Native cross-product search
API	openFDA with separate endpoints per product type	AEMS API with unified endpoint
Data model	Different schema per database	Unified schema with product-specific extensions
Operating cost	~$37M/year across 7 systems	Significant reduction (~$120M savings over 5 years)
Report format	Varied by system	Standardized across all product types

What Stays the Same

Not everything changes. The regulatory obligations that generate adverse event data remain untouched:

• MDR reporting requirements under 21 CFR Part 803 remain identical. Manufacturers, importers, and user facilities still have the same reporting obligations with the same deadlines (30-day standard, 5-day expedited, 10-day for user facilities).
• MedWatch forms (3500, 3500A) remain the primary submission mechanism for voluntary and mandatory reports.
• Report content — event descriptions, device information, patient outcomes, manufacturer narratives — carries over to AEMS without changes to what must be reported.
• Historical data from MAUDE and all other legacy systems is fully preserved and searchable in AEMS.
• Product codes, device classifications, and 510(k)/PMA numbers continue to be used as device identifiers within AEMS.
• openFDA API compatibility — the FDA has committed to maintaining backwards-compatible endpoints during and after the transition, though new AEMS-native endpoints offer additional capabilities.

Impact on Medical Device Teams Specifically

For teams whose primary concern is medical devices, AEMS changes the monitoring landscape in several concrete ways.

Real-Time Access to Device Reports

MAUDE was updated on a monthly cycle, with occasional longer delays. By the time a report appeared in the public MAUDE Database, weeks or months could have passed since the event. AEMS provides real-time updates, meaning adverse event reports become searchable shortly after they are submitted. For organizations that need to detect emerging safety signals quickly — which is to say, most device manufacturers — this is a substantial improvement.

Cross-Product Visibility

Combination products (drug-device, biologic-device) have always been a monitoring challenge. A report about a prefilled syringe failure might appear in MAUDE (device malfunction) or FAERS (drug-related adverse event) depending on how the reporter classified it. With AEMS, both reports are in the same system, searchable with a single query. This eliminates a blind spot that has existed for decades.

New Dashboard and Analytics

AEMS includes built-in analytics capabilities that MAUDE's legacy interface lacked:

• Signal detection algorithms that flag unusual report volume patterns automatically
• Trend visualization showing report volumes over time by product code, event type, or manufacturer
• Geographic distribution of reports, enabling identification of region-specific safety issues
• Customizable alert configuration — set thresholds and receive notifications when they are exceeded

Unified Manufacturer Portal

AEMS introduces a single submission portal for manufacturers. Rather than navigating different submission systems for different report types, manufacturers can submit all adverse event reports — regardless of product category — through one interface. For companies that market both devices and drugs (or combination products), this reduces administrative overhead.

API Migration: openFDA to AEMS API

The API transition is the most technically impactful change for organizations with automated monitoring pipelines.

Current State (openFDA)

The existing openFDA API serves adverse event data through product-specific endpoints:

• /device/event — MAUDE device adverse events
• /drug/event — FAERS drug adverse events
• Other endpoints for recalls, enforcement reports, etc.

AEMS API

The new AEMS API provides:

• Unified /adverse-events endpoint — query across all product types with a single call
• Product-type filtering — narrow to devices, drugs, biologics, etc. using a product_type parameter
• Enhanced search syntax — support for complex boolean queries, nested field searches, and proximity matching on narrative text
• Real-time data — reports appear in API results shortly after submission, replacing the weeks-long lag of the MAUDE/openFDA pipeline
• Webhook subscriptions — register for push notifications when reports matching your criteria are submitted, eliminating the need for polling
• Higher rate limits — the AEMS API offers increased throughput for authenticated users with API keys

Migration Path

The FDA has committed to maintaining backwards compatibility for existing openFDA endpoints through at least the end of 2026. Here is the recommended migration sequence:

1. Now (May 2026): Register for an AEMS API key at the FDA developer portal
2. Parallel testing: Run your existing openFDA queries alongside equivalent AEMS API queries and compare results
3. Validate field mapping: AEMS uses a unified schema — confirm that device-specific fields (product code, device class, MDR Report Key) map correctly
4. Switch primary source: Once you have validated consistency, point your monitoring pipeline at the AEMS API
5. Retire openFDA calls: After confirming stable operation, remove openFDA dependencies
6. Adopt AEMS-native features: Implement webhook subscriptions, cross-product queries, and enhanced search capabilities that have no openFDA equivalent

Example: openFDA vs. AEMS API Query

openFDA (legacy):

GET https://api.fda.gov/device/event.json?search=device.product_code:"ABC"+AND+event_type:"Death"+AND+date_received:[20260101+TO+20261231]&limit=100

AEMS API (new):

GET https://aems.fda.gov/api/v1/adverse-events?product_type=device&product_code=ABC&event_type=death&date_received=2026-01-01..2026-12-31&limit=100

The AEMS API uses a cleaner query syntax with explicit parameter names rather than Lucene-style search strings. Responses follow a consistent JSON schema across all product types.

How to Prepare Your Monitoring Workflows

Whether you monitor adverse events manually or through automated systems, the AEMS transition requires preparation. Here is a practical checklist.

For Teams Using the MAUDE Web Interface

1. Bookmark the AEMS portal. The legacy MAUDE web interface at accessdata.fda.gov will redirect to AEMS by end of May 2026.
2. Familiarize yourself with the new search interface. AEMS search works differently — take time to run test queries against your key product codes and manufacturers before the old interface disappears.
3. Update your SOPs. Any standard operating procedure that references "MAUDE" or the MAUDE web URL needs to be updated to reference AEMS.
4. Retrain your team. Anyone who runs MAUDE searches as part of their role should receive training on the AEMS interface before the transition completes.

For Teams Using the openFDA API

1. Register for AEMS API access at the FDA developer portal.
2. Map your existing queries to the AEMS API schema. Document every openFDA query your organization runs and identify the AEMS equivalent.
3. Run parallel queries during the remaining parallel operation window to validate data consistency.
4. Update field references in your code — while most fields carry over, some field names and paths have changed in the unified schema.
5. Test webhook subscriptions for your most critical monitoring criteria. Webhooks can replace polling-based monitoring with event-driven alerts.

For Teams Using Third-Party Monitoring Tools

If you use a regulatory intelligence platform (such as MedFlux) for adverse event monitoring, the transition may already be handled for you. Check with your provider to confirm:

• Are they already ingesting data from AEMS?
• Is historical MAUDE data preserved in their system?
• Have they validated data continuity through the transition?
• Do they leverage AEMS-native features (real-time updates, cross-product search)?

Update Your QMS Documentation

The following documents likely reference MAUDE by name and need updating:

• Post-market surveillance plans
• Complaint handling procedures
• CAPA procedures (where MAUDE monitoring is a data source)
• Management review inputs
• Risk Management files (ISO 14971)
• Periodic Safety Update Reports (PSURs) for EU MDR compliance

AEMS vs. MAUDE: Feature Comparison

Feature	MAUDE (Legacy)	AEMS (New)
Product scope	Medical devices only	All FDA-regulated products
Data freshness	Monthly batch updates	Real-time
Search interface	Basic web form	Modern dashboard with filters and analytics
Cross-product search	Not available	Native support
Signal detection	Manual analysis required	Built-in algorithmic detection
Trend visualization	Not available (export to Excel)	Built-in charts and dashboards
API	openFDA /device/event	AEMS unified API with webhooks
Geographic analysis	Not available	Built-in geographic distribution
Alert notifications	Not available	Configurable threshold alerts
Historical data	MAUDE records only	All 7 legacy databases merged
Report identifiers	MDR Report Key	AEMS ID + legacy cross-reference keys
Submission portal	eMDR / eSubmitter	Unified AEMS manufacturer portal
Bulk data export	Annual ZIP files	Streaming API + bulk export
Maintenance cost	Part of $37M/year for 7 systems	Consolidated single-platform cost

Frequently Asked Questions

What does AEMS stand for?

AEMS stands for Adverse Event Monitoring System. It is the FDA's new centralized platform for collecting, storing, and analyzing adverse event reports across all FDA-regulated product categories.

When did AEMS launch?

AEMS launched on March 11, 2026. It entered a parallel operation phase alongside legacy systems, with full transition and legacy decommission scheduled for end of May 2026.

Does AEMS replace MAUDE?

Yes. MAUDE is one of seven legacy databases being decommissioned as part of the AEMS rollout. All historical MAUDE data has been migrated into AEMS, and all new medical device adverse event reports flow into AEMS.

Does AEMS replace FAERS and VAERS too?

Yes. AEMS replaces all seven legacy systems: MAUDE, FAERS, VAERS, HFCS, CTPAE, CAERS, and AVRS. All product categories — drugs, devices, vaccines, biologics, cosmetics, food, and animal drugs — are covered by the single AEMS platform.

Do my MDR reporting obligations change under AEMS?

No. The regulatory requirements under 21 CFR Part 803 remain unchanged. Reporting deadlines, report content requirements, and who must report are all the same. Only the system that receives and stores the reports has changed.

Will my openFDA API integrations break?

The FDA has committed to maintaining backwards-compatible openFDA endpoints through at least the end of 2026. However, organizations should migrate to the AEMS API during this grace period, as openFDA endpoints will eventually be retired.

Can I still search for historical MAUDE data in AEMS?

Yes. All historical records from MAUDE (and the other six legacy databases) have been migrated into AEMS. Legacy identifiers like MDR Report Keys are preserved as cross-reference fields, so you can look up specific historical reports using the same identifiers you used before.

How do I get access to the AEMS API?

Register for an API key at the FDA developer portal. During the transition period, the same API key works for both openFDA and AEMS endpoints.

What product types does AEMS cover?

AEMS covers all FDA-regulated product categories: prescription and over-the-counter drugs, medical devices, biologics, vaccines, cosmetics, human foods and dietary supplements, tobacco products, and animal drugs and feed.

Is AEMS data truly real-time?

AEMS provides near-real-time updates. Reports become searchable shortly after submission — a dramatic improvement over MAUDE's monthly batch update cycle. The exact latency depends on report type and submission method, but it is measured in hours rather than weeks.

---

MedFlux integrates directly with AEMS to deliver real-time adverse event intelligence for medical devices across 27 global regulators. Instead of building and maintaining your own AEMS monitoring pipeline, MedFlux surfaces emerging safety signals, recall precursors, and competitive intelligence — filtered to your specific device portfolio and delivered to your team automatically. Learn more about MedFlux →