AEMS dashboard · public data limits
The page formerly presented as the FAERS Public Dashboard now identifies the FDA Adverse Event Monitoring System, or AEMS. Its reports support surveillance; they cannot establish event rates, causation or a ranking of drug safety.
What changed in the source
The queue’s original FDA URL redirects to the AEMS Public Dashboard page, which labels AEMS as formerly the FDA Adverse Event Reporting System, or FAERS. FDA describes AEMS as a platform intended to consolidate reporting systems across regulated product categories.
This naming change is itself time-sensitive metadata. A responsible article preserves “FAERS” where it describes historical searches or the old page name, while using “AEMS” for the current interface and recording the retrieval date.
Four limitations must travel with every result
- A report does not mean its medical details have been confirmed.
- Submission does not establish that a product caused or contributed to an event.
- Reports may be incomplete, duplicated or affected by reporting behavior.
- FDA states that report information cannot be used to estimate event incidence.
Therefore, “more reports” is not the same as “higher risk.” Products differ in use, time on market, publicity, mandatory reporting and the populations receiving them.
Prescription counts, sales or web interest are not automatically compatible exposure denominators. A risk estimate requires a study design built for that question.
A reproducible dashboard note
- Record the system name and retrieval timestamp.
- Save the exact product and event terms entered.
- State the date range and filters.
- Explain any case-level deduplication or exclusions.
- Report counts as reports, not patients or proven reactions.
- Link the FDA limitations beside the result.
What a valid conclusion looks like
A dashboard pattern can justify further investigation or a search for stronger evidence. It cannot establish individual diagnosis, comparative safety, a treatment recommendation or an FDA regulatory conclusion. Check for an FDA safety communication, labeling action or other formal agency source before describing regulatory meaning.
For operational questions involving surgery or anesthesia, use the Surgical Workforce and Care Access hub to separate surveillance data from verified local capacity.