Feature guide

Adverse Event Monitoring: From Single Reports to Trends

By Kieran Redington, Founder of MedFortis Published 29 October 2026 ~6 min read

The FDA's MAUDE database holds millions of adverse event reports for medical devices, and new ones arrive every week. Most device makers know they should be watching it. Fewer have worked out what they're watching for, because a single report rarely tells you anything on its own. What matters is whether something is changing.

Why one report tells you very little

A MAUDE report is a submission, not a finding. Anyone can file one: manufacturers, hospitals, doctors and patients. The FDA says so itself in its notes on the database. The reports can be incomplete, duplicated or wrong, and they can't be used on their own to work out how often a problem happens or whether the device caused it.

So a team that reads every report for its device and reacts to each one ends up busy without getting much safer. One report of a cracked housing might be a dropped device. Twenty in a month, where there used to be two, is something else.

For the mechanics of searching the database itself, see our guide on how to search and monitor FDA MAUDE.

What a real signal looks like

Useful adverse event monitoring asks two questions about each device:

The second test is often the more useful one. Comparing a device with its own history filters out the background level of reports every product has, and shows you the change, which is what you need to act on.

Why manual monitoring falls behind

Doing this by hand means exporting reports, cleaning up device names, counting by month and comparing against last quarter's spreadsheet. It works for one device. It doesn't work for a portfolio, and it doesn't work every week.

The other problem is that adverse events don't only live in MAUDE. Health Canada publishes incident data, the MHRA collects reports through the Yellow Card scheme, and recalls and safety notices in other markets often explain what's behind a rise in US reports. Looking at MAUDE alone gives you half the picture.

How MedFortis handles it

Reports matched to your devices

MedFortis matches adverse event reports to the devices on your list, so you're looking at your products rather than at a keyword search that also catches everything with a similar name. A device lookup shows its adverse events next to the recalls and safety notices about it from other regulators.

Trend alerts

For each device, MedFortis flags when reports go above a threshold you set, or above that device's own normal level. You find out about a rise while it's still small, instead of noticing it when you write next year's PSUR.

A signals inbox, ranked by severity

New adverse events, recalls and safety notices for your devices arrive in one inbox, with the most serious first. Each one waits for someone to assess it and record what they decided and why. That record is what an auditor or notified body will ask for.

Your team decides: MedFortis spots the pattern and ranks the signal. Whether it's a genuine problem, and whether it needs reporting, stays with your team. Every decision is logged with its reason.

Where this fits with MDR trend reporting

Under Article 88 of the EU MDR, manufacturers must report a statistically significant increase in the frequency or severity of incidents that aren't serious incidents, or of expected side effects, where it could affect the benefit-risk analysis. The method and thresholds for spotting those trends belong in your technical documentation.

Trend alerts in MedFortis are an early warning, not an Article 88 decision. The thresholds you use for monitoring won't always match your reporting triggers, and that's fine as long as you document how the two relate. What monitoring gives you is time: you see the rise early enough to investigate before a reporting clock starts. Our guide to EU MDR Articles 83–92 covers the reporting rules in more detail.

See what's being reported about your devices

Book a free 30-minute demo. We'll run MedFortis on your device lines and show you their adverse events, recalls and notices, live.

Book a Demo →

Key takeaways

  • A single MAUDE report can't tell you how often a problem happens or what caused it. Watch for change, not individual reports.
  • Two useful tests: has a device crossed a threshold you set, and is it above its own normal level?
  • Adverse events also come from Health Canada, the MHRA and others, and recalls elsewhere often explain a rise.
  • MedFortis matches reports to your devices, flags rises early and logs every decision your team makes.
  • Monitoring thresholds are an early warning. Article 88 reporting decisions stay with your team.
This article is provided for general information only and is not legal or regulatory advice. Regulatory requirements are summarised and paraphrased; always refer to the official texts and guidance, and consult a qualified regulatory professional for your specific devices and markets.