If your surveillance relies on MAUDE, keep relying on it. As of November 13, 2026, MAUDE is still where the FDA publishes medical device reports. The FDA's new Adverse Event Monitoring System (AEMS) shows none.
That is not the whole story. The FDA has said AEMS will replace MAUDE. It named a month that has since passed, and it scheduled a change to the system behind device report submission. This article sets out what the FDA has said, what you can check for yourself and what to watch.
Everything below comes from FDA pages read on November 13, 2026. They are listed at the end.
What AEMS Is
AEMS is one platform for adverse event reports across the products the FDA regulates: drugs, biologics, vaccines, devices, tobacco, food, cosmetics and veterinary medicines. The FDA launched it on March 11, 2026.
The reason is consolidation. The launch announcement says the agency had been processing about 6 million reports a year across seven databases. AEMS is meant to hold them in one place behind one public dashboard. The FDA also says AEMS will publish reports in real time instead of quarterly.
What It Replaced
The announcement listed three systems as replaced at launch:
- FAERS, which held reports for drugs, biologics, cosmetics and color additives.
- VAERS, for vaccines. The FDA said it would display VAERS data in AEMS and that VAERS is co-managed with the CDC.
- AERS, two databases for animal drugs and animal foods.
It listed a second group "to be replaced by AEMS in May": MAUDE for medical devices, the Human Foods Complaint System and the tobacco adverse event system. It said AEMS would contain reports for all FDA-regulated products by the end of May 2026.
What That Means for Device Reports Today
The May date passed. Here is what the FDA's pages show now.
The AEMS dashboard has no device reports. Its product tabs are Drugs and Biologics, Cosmetics and Vaccines. You can open it from the AEMS page.
MAUDE is live. The MAUDE search page was last updated on October 30, 2026. It says the database is updated every month with reports received through the end of the previous month. It carries no notice about AEMS.
The bulk files are still MAUDE files. The MDR Data Files page says they are updated monthly. It also says: "In 2026, the data in the MAUDE Database will become available in the FDA's Adverse Event Monitoring System (AEMS)." That is the FDA's current statement on timing. It gives a year and no day.
openFDA still serves MAUDE. The openFDA device event documentation names MAUDE as its source and lists weekly updates. It does not mention AEMS. On November 13 the newest report in the API had an FDA receipt date of October 30, 2026.
There is no AEMS device API. The launch announcement said the FDA would roll out enhanced APIs and gave no date. We found none for devices.
What the FDA Scheduled: Submission
One device change does carry the AEMS name. The FDA's eMDR System Enhancements page lists "eMDR consolidation with Adverse Event Monitoring System (AEMS)". It scheduled an outage from July 22 to July 27, 2026 and production deployment on July 27.
For teams that submit MDRs, the FDA said:
- The electronic MDR submission format and destination address would not change.
- eSubmitter users would not be affected.
- Ack3 error messages would change slightly, without affecting parsing.
- With the consolidation, eMDR would begin rejecting ISO 3166-1 alpha-2 country codes. Submitters should use GENC 3-letter codes.
That page was last updated a week before the deployment date, and we have not found an FDA page confirming the deployment. If you submit through AS2 or the API, your own acknowledgement records since late July will show whether anything changed for you.
Your reporting obligations are the same. The FDA's notice says nothing about the requirements in 21 CFR Part 803.
What Is Not Known
- When device reports will appear in AEMS. "In 2026" is the only current statement.
- How long MAUDE search, the bulk files and the openFDA endpoint will keep running. The announcement says the FDA will "decommission certain legacy systems". It names MAUDE among the systems to be replaced and gives no date for switching off any of the three.
- What an AEMS device API will look like. Nothing published says whether field names and report counts will match MAUDE's.
Several websites report the device move as finished. We could not find an FDA page that says so. Earlier DeviceWatch articles made the same mistake, and they now carry visible corrections.
What to Watch
Four FDA pages will show a change before anything else does:
- The AEMS page and its dashboard. Watch for a device tab.
- The MDR Data Files page. Watch for the AEMS sentence to change tense, and for the files to move or gain a new label.
- The eMDR System Enhancements page. Submission changes are posted here. The FDA says it also emails them to the CDRH Industry list.
- The openFDA device event documentation. Watch the named source, the update frequency and any deprecation notice.
A monthly check is enough. Log the date, the pages and whether anything changed. A dated PDF of each page is evidence an auditor can use a year from now.
What to Do
Keep running surveillance against MAUDE data. Nothing the FDA has published asks you to switch sources.
Keep "MAUDE" in your procedures. Name the source system in one controlled place, so a later change is one edit.
Record the source and retrieval date with every extract. If report counts shift when the data moves, you can show what the source said on the day you used it.
What DeviceWatch Does About It
DeviceWatch reads the FDA's public MAUDE data and says MAUDE in the product, because that is the name on the data.
A scheduled check runs every six hours against four FDA channels: the openFDA device event API, the MAUDE bulk file area, the MDR Data Files page and the AEMS page in the FDA's drugs section. It looks at record contents and file listings as well as timestamps, because a refreshed timestamp does not always mean new reports.
When the FDA publishes device data through AEMS, the change for us is in the ingestion layer. Your monitored products, review history and audit trail do not depend on which FDA system supplied a record. Until then there is nothing for a customer to do.
Sources
All read on November 13, 2026.
- FDA Launches New Adverse Event Look-Up Tool, FDA press announcement, March 11, 2026
- FDA Adverse Event Monitoring System (AEMS), content current as of March 11, 2026
- MDR Data Files, content current as of September 2, 2026
- eMDR System Enhancements, content current as of July 20, 2026
- MAUDE search page, page last updated October 30, 2026
- openFDA device adverse event documentation