A safety count is a starting point for a question
A headline saying that a medicine has hundreds of reports can sound like a count of confirmed injuries. It is not. A report says someone submitted information about an event involving a product; the cause may still be uncertain. That distinction does not make a patient’s experience unimportant. It defines what the dataset can answer. I would look for the reporting system, dates, product definition and event definition before interpreting a total. Without those details, two apparently precise numbers may describe different searches rather than different levels of risk.
Older FAERS studies and the current AEMS platform
FDA announced its new adverse-event lookup tool in March 2026 and describes AEMS as consolidating reporting systems across its regulated product categories. Older papers can still analyze historical FAERS extracts; changing the platform name does not change the study they conducted. Keep the collection period and dataset version beside a result. I would not call every historic FAERS analysis a live view of today’s submissions, or assume an announced migration milestone establishes that every database field is comparable across time. The method used to assemble a count matters as much as the current dashboard interface.[2]
Why reports do not establish that the product caused the event
FDA’s AEMS limitations explicitly state that a submitted report does not establish causation and that report information may be incomplete, duplicated or unverified. An underlying illness, another medicine or another cause may explain an event. That is why the report itself and a clinical causality assessment are different pieces of evidence. A careful article should describe a suspected or reported event without silently changing it into a confirmed drug effect. The same caution applies when a report involves hospitalization or death: seriousness does not independently establish which exposure caused the outcome.[1]
| What the data contain | What should not be inferred |
|---|---|
| A submitted suspected event | Proof that the product caused it |
| An incomplete case description | A confirmed clinical diagnosis |
| Several submissions | Necessarily several distinct patients |
| A total number of reports | An incidence rate among all users |
FDA explicitly warns that reports may be duplicated, incomplete or unverified, do not establish causation and cannot estimate occurrence rates. This table paraphrases those limits; it does not rank medicines or dismiss reported experiences. Source: FDA: AEMS public dashboard and data limitations.
The missing denominator prevents a risk calculation
A report count alone does not tell you how many comparable people used the product, for how long, or how consistently events were captured. FDA has long cautioned that FAERS cannot calculate incidence. Imagine two products with different patient populations, years on the market and reporting patterns: dividing one total by the other does not produce a meaningful safety ratio. Even adding prescription counts may not create a valid comparison if reporting completeness and event definitions differ. I would look for an appropriately designed trial or comparative epidemiological study before making a statement about how often an event occurs.[3]
Underreporting and duplicate reports can coexist
It may seem contradictory that a system can miss events and contain duplicates, but they are different problems. Some experiences never reach a reporting system, while one episode can generate multiple submissions or follow-up information. You cannot correct both by applying a guessed multiplier to a dashboard total. Nor does an absence of reports show that a product has been proven safe. For a particular claim, ask how researchers handled duplicate records, missing detail and changing reporting practices. Those questions should remain visible rather than disappearing behind a chart that presents a count as an exact measure of harm.
Branded and compounded report totals cannot rank products
FDA distinguishes approved products from compounded preparations and describes concerns including fraudulent labeling, shipment conditions and dosing-related problems. Those are important product-specific issues, not permission to calculate comparative safety from raw reports. A product described only as semaglutide may still leave questions about source, formulation or labeling. I would not compare a branded product’s total with a compounded category’s total and announce a safer option. Approval status, the actual preparation and the quality of the evidence must remain explicit. A similar ingredient name does not make the underlying products or reporting pathways equivalent.[4] Our branded versus compounded guide explains the product-status distinction.
A report can still help identify a problem worth investigating
Safety surveillance is useful because patterns can prompt further review even when an individual report cannot prove cause. FDA’s launch announcement describes the new tool as supporting detection of potential safety signals. That is a different job from predicting a patient’s risk. If you experience a suspected problem, obtain appropriate clinical care and retain the product details privately for your clinician and any report. Reporting is not a substitute for treatment, and medical advice should not wait for a dashboard count to change. A careful account can acknowledge both the value of reporting and its statistical limits.[2] For the reporting process, see our MedWatch guide; avoid sharing personal medical details in public comments.
How I would check a safety headline
I would ask four questions: is this a report count or a measured rate, what exact product and period were searched, what evidence supports causation, and what do current official warnings say? If those answers are missing, pause before forwarding the number or changing a medicine. Bring a specific concern to the treating clinician. When comparing care services, examine how they handle symptoms and identify the dispensing pharmacy; do not choose a platform because its name appears rarely in a spontaneous-report search. The absence of a company name is not a clinical safety certification. Use the online-pharmacy verification guide for practical checks. Our LifeMD review describes service and billing information, not an adverse-event rate or safety ranking.
Put the questions to work
Compare our researched providers or build your provider checklist.
Continue your research
Sources & scope
Sources checked October 28, 2026. This guide explains published information and consumer research questions; it is not a clinical evaluation.
- FDA: AEMS public dashboard and data limitations
- FDA: March 2026 launch of the new adverse-event lookup tool
- FDA: historical FAERS dashboard explanation and interpretation limits
- FDA: current concerns with unapproved GLP-1 medicines
Prices and terms can change. Confirm your specific offer directly with the provider.