FDA device adverse-event summaries show frequent gaps in MAUDE reporting
A cross-sectional analysis of the FDA’s Manufacturer and User Facility Device Experience database has exposed a basic problem in postmarket surveillance: devices with large numbers of adverse events are being bundled into summary reports, yet the records often fail to satisfy the reporting rules meant to make those submissions usable. The study examined every adverse event summary report filed in MAUDE from July 2019 through June 2025 and asked a simple but clinically important question: do these summaries actually capture the event burden accurately, completely, and on time?
The answer appears to be no, at least not consistently.
In total, 6308 summary reports were submitted to MAUDE and contained 159,503 adverse events. Use of summary reports rose from 808 in 2020 to 1757 in 2024, increasing by a factor of 1.21 per year. Growth in volume alone does not equal better surveillance. In a system built to detect device malfunction, patient harm, and signal emergence, a larger number of reports can still leave regulators and clinicians with fragmented data if the summaries are coded poorly or submitted without the details FDA rules require.
Missing device codes and incomplete event counts weaken surveillance value
The study evaluated several core elements of reporting quality: identification of device problem codes, proper designation as summary reports on the submission form, concordance between the number of events field and the narrative description, and compliance with FDA reporting deadlines. Each of those pieces matters because MAUDE is only as reliable as the structure of the reports entering it. If the device problem code is vague or wrong, the report becomes difficult to categorize. If the event count in the form does not match the narrative, the database loses internal consistency. If deadlines slip, the signal may arrive too late to protect patients exposed to the same device failure pattern.
This is not a clerical nuisance. Device surveillance depends on pattern recognition across thousands of submissions, and those patterns can be obscured when manufacturers compress multiple harms into a summary without preserving enough detail to identify the failure mode. A report that lists a large event total but fails to align the count with the narrative creates uncertainty about whether the database contains one consolidated cluster, repeated similar episodes, or a poorly reconciled account of distinct events. In postmarket oversight, ambiguity can delay action.
Summary reporting can speed paperwork while blurring clinical meaning
Summary reporting exists to reduce burden when a device-related problem generates many similar events. In theory, the format allows manufacturers to avoid filing hundreds or thousands of near-duplicate reports while still preserving the essential safety signal. In practice, the system only works if the summary maintains fidelity to the underlying event stream. Once the narrative and coded fields drift apart, the report becomes less useful for FDA reviewers, epidemiologists, and frontline clinicians trying to determine whether a device is malfunctioning in a reproducible way.
The findings also speak to a deeper tension in adverse-event surveillance. Administrative efficiency and clinical accuracy do not always move together. A streamlined form can reduce manual workload, but it can also encourage compressed descriptions that obscure how often a failure occurred, what type of harm resulted, or whether the problem clustered around a particular design, user action, or batch. In a device database, those distinctions determine whether a safety signal is ignored, investigated, or escalated.
One consequence is immediate. A database filled with incomplete summaries can create false reassurance where a true safety issue is unfolding.
Compliance failures matter because MAUDE feeds regulatory action
The study’s focus on FDA compliance was not bureaucratic housekeeping. Reporting deadlines, correct form designation, and internal consistency are the scaffolding that lets MAUDE function as a regulatory tool rather than a passive archive. When deadlines are missed, regulators may lose timeliness. When the summary designation is incorrect, the report may not be processed as intended. When counts and narratives diverge, reviewers must spend more time reconstructing what happened, and some details may never be recovered.
For patients, these failures can translate into delayed recognition of a device problem that repeats across hospitals, clinics, or user settings. For manufacturers, poor-quality summaries can obscure whether a product issue is isolated or systematic. For regulators, they reduce confidence in the database at the very moment when confidence is most needed. The value of adverse-event surveillance depends not only on volume, but on whether each record can support a reliable chain from event description to risk assessment.
What the MAUDE findings say about device safety monitoring
The data reveal a growing reliance on summary reporting between 2019 and 2025, but they also suggest that expansion has not automatically produced clean reporting. With 6308 summaries representing more than 159,000 adverse events, the scale alone is substantial. The central question is whether the format is being used as intended. If device problem codes are incomplete or inaccurate, if the event totals do not match the narrative, or if filing timeliness erodes, then the aggregate record can look robust while still concealing clinically important detail.
This is especially relevant in device safety because harms are often mediated through mechanical failure, software malfunction, procedural error, wear, or human-device interaction rather than a single biologic pathway. Those failure modes are easier to detect when reports are precise and internally consistent. They become harder to separate when summary narratives are vague or when the database contains incompatible fields that frustrate automated review.
The study strengthens the case for tighter oversight of summary submissions and more rigorous attention to the quality of the underlying reporting process. It also raises a practical issue for surveillance policy: a larger MAUDE database is not necessarily a better one unless the reports inside it remain faithful to the events they are meant to describe. The unanswered operational question is how FDA and manufacturers will close the gap between acceptable volume and acceptable quality in a system that now handles thousands of adverse events through abbreviated summaries rather than individual case reports.