In March 2026, the FDA announced the launch of a new unified platform for monitoring and analyzing adverse events, the Adverse Event Monitoring System (AEMS). The platform is designed to replace and integrate existing systems, including FAERS and VAERS, overcoming a fragmented architecture based on multiple applications. For pharmaceutical companies, the question arises naturally: what actually changes from an operational perspective? The answer is straightforward, but requires a broader interpretation.
How the new FDA AEMS platform works and which systems it replaces
AEMS (Adverse Event Monitoring System) is the FDA’s new unified platform for the collection, monitoring and analysis of adverse event reports across the full spectrum of regulated products (drugs, vaccines, medical devices, food and others).
It represents a significant architectural shift: legacy systems will be progressively unified within this new platform, including FAERS (reports related to drugs, biologics, cosmetics and color additives), VAERS (reports related to vaccines, co-managed with CDC), AERS (databases for animal drugs and animal food), MAUDE (reports related to medical devices), HFCS (reports related to food and dietary supplements) and CTPAE (reports related to tobacco products and Electronic Nicotine Delivery Systems).
The new platform introduces tools that make data access, export and querying more structured and easier to manage. It also supports the analysis of available information.
This is not simply an update, but a rationalization and strengthening of the pharmacovigilance data ecosystem.
Immediate operational changes for companies with the new FDA platform
From the perspective of pharmaceutical companies and service providers, the new platform does not introduce operational changes in the short term. Submission workflows remain unchanged, no new regulatory obligations are introduced, and no system upgrades are required. The management of ICSRs, as well as submission and compliance processes, remains the same.
Regarding submission methods, companies that do not have a direct gateway (ESG) to the FDA can continue to use existing alternative channels, such as the Safety Reporting Portal (SRP).
While operations do not change, the context in which data is used does. With AEMS, pharmacovigilance data does not change in nature, but becomes more accessible and easier to query within an integrated environment. This shift has a concrete effect: it reduces the gap between data availability and its actual usability, making analysis, case comparison and safety evaluation activities more efficient.
Why the new FDA platform requires greater control over pharmacovigilance data quality and structure
More accessible data is also more observable: errors, inconsistencies or incompleteness can directly impact the robustness of data analysis. Using a safety database designed to ensure data integrity, compliance and end-to-end traceability makes it possible to feed the AEMS ecosystem with reliable data, enabling more accurate, consistent and trustworthy analyses.