FDA AEMS adverse-event dashboard: how to read peptide and GLP-1 reports

01

What FDA launched—and what changed in 2026

FDA announced AEMS on March 11, 2026 as a unified platform for displaying adverse-event reports across regulated product categories. The launch page said systems including the FDA Adverse Event Reporting System for drugs and therapeutic biologics would move into the new platform, with additional product-center data and historical records migrated over time. FDA described real-time publication as a major change from the prior quarterly public-release cycle.

The public interface can improve access, filtering, and trend review. That is useful when a peptide provider cites a report count, says a product has 'no safety signals,' or compares a compounded preparation with an approved brand. A consumer can now go closer to the underlying federal report record instead of relying on a screenshot, social-media thread, or marketing summary.

The technology change does not erase the limitations of spontaneous reporting. AEMS is a surveillance and signal-detection resource. It is not a clinical diagnosis tool, a controlled trial, an exposure registry, a prescribing guide, or an FDA finding that every listed event was caused by the named product.

02

What one dashboard report actually means

An adverse event is a medical occurrence reported while a product was used; the term does not itself establish a causal relationship. A report may come from a consumer, clinician, manufacturer, or another reporting pathway. It can be valuable even when cause is uncertain because multiple reports may help FDA notice an unexpected pattern that deserves investigation.

A single case can contain incomplete product identity, limited timing information, other medications, underlying conditions, or more than one possible explanation. Public dashboard fields also omit some narrative information available to FDA reviewers in order to protect privacy. FDA safety staff may review narratives, remove duplicates, apply consistent case definitions, and combine AEMS with labeling, clinical studies, claims data, and other surveillance sources.

For that reason, a search result should be described as 'reports naming' or 'reports associated with' a product, not as confirmed side effects caused by the product. A death outcome in a report does not establish that the product caused the death. The same restraint applies to hospitalization, disability, or another serious outcome.

03

Why counts cannot show incidence or rank safety

Incidence asks how often an event occurs among a defined number of exposed people over a defined period. AEMS does not provide a reliable denominator for every product, and many events are never reported. Reporting can rise after news coverage, a label change, litigation, a warning, or a product's rapid growth. Older products also have had more time to accumulate reports than newly marketed products.

Duplicate submissions can occur when a consumer reports directly and a manufacturer later submits the same underlying case. Product names and event terms may also be coded or updated over time. FDA's AEMS FAQ warns that even identical products can have widely different monitoring levels, so comparing raw totals is not a valid safety ranking.

A blank or low-count result is not proof that a product is safe. It may reflect a new, obscure, misspelled, compounded, or research-only product that is difficult to identify in the database. Conversely, a high count may partly reflect large use, mandatory manufacturer reporting, older market history, or stimulated reporting—not necessarily a higher event rate.

04

A careful search workflow for peptide and GLP-1 products

Start with exact identity. Record the approved brand, nonproprietary active ingredient, dosage form, and whether the product is FDA-approved, compounded, investigational, or sold outside a prescription pathway. Search both brand and ingredient where the interface allows, but do not merge them silently. A compounded product with a similar ingredient name is not automatically the FDA-approved brand.

Record the filters, date range, event term, outcome category, and date accessed. Then inspect individual case listings when available instead of relying only on a total. Look for repeated case identifiers, multiple suspect products, missing dates, and product names that do not clearly identify the formulation or compounder. Preserve uncertainty when the record cannot resolve identity.

Next, compare the signal with the current FDA-approved label in DailyMed or Drugs@FDA, FDA Drug Safety Communications, safety-labeling changes, recalls, and quarterly potential-signal notices. A provider should not use a dashboard count alone to claim that a compounded peptide is safer than an approved product or that an unapproved product has a proven safety profile.

• →Exact brand and active ingredient
• →Approved, compounded, or investigational classification
• →Date range and event term
• →Case identifiers and possible duplicates
• →Other suspect products and missing details
• →Current label and FDA safety communications

05

How to evaluate a provider's AEMS claim

Ask the provider to link the saved search or identify the exact filters behind any number. A defensible explanation should name the product, time window, event term, and limitations. Statements such as 'zero deaths,' 'fewer side effects,' or 'FDA data prove safety' require more than a dashboard screenshot and may be misleading when the denominator, duplicates, exposure, and causation are unresolved.

Check whether the clinic switched between an approved brand, an ingredient, and a compounded preparation while explaining the result. Also check whether it compared products from different launch dates or levels of use. The dashboard cannot validate the clinic, pharmacy, dose, treatment plan, or quality of a specific dispensed lot.

A provider should be able to discuss known label risks, contraindications, monitoring, and reporting pathways without using AEMS as individualized medical advice. Treatment decisions require an appropriately licensed clinician who knows the patient's history and current evidence. The directory does not interpret a person's symptoms or tell anyone to start, stop, or change a medicine.

06

Reporting a problem and responding safely

FDA's voluntary reporting instructions allow consumers, patients, and health professionals to report suspected serious adverse events and product problems through MedWatch. Proof of cause is not required; suspicion of an association is enough to report. Useful details include the exact product, manufacturer or compounder, strength or concentration, lot when available, dates, other products used, what happened, and relevant medical care.

Reporting is different from browsing. A dashboard search does not submit a report, and a MedWatch submission does not establish liability or causation. Preserve packaging and labels when a compounded or possibly fraudulent product is involved, and separately contact the dispensing pharmacy and prescribing clinician as appropriate.

For severe symptoms or a suspected emergency, seek immediate medical care instead of waiting for a provider message, database result, or FDA response. People should not stop or change a prescribed drug solely because an event appears in AEMS. Clinical interpretation belongs with a qualified clinician; product-quality and regulatory questions can also be reported to FDA and relevant state authorities.