Which Medical Device Complaints Are Reportable, and Which Authority Should Be Notified?
A complaint may involve no actual injury and still require regulatory reporting. Another complaint can involve a real product defect but not be a reportable event.
That is the key to good medical device complaint management. It is not just about “Did we get a complaint?” It is about whether the information constitutes an event that fulfills the report criteria in any markets where reporting is required.
Every complaint therefore needs appropriate review, but not every complaint needs to be submitted to a regulatory authority. Reportability depends on factors such as the patient or user outcome, the device’s possible contribution, the nature of any malfunction or deficiency, and what could happen if the event occurred again.
For companies operating internationally, the assessment does not necessarily stop with the country in which the event occurred. The same underlying event may need to be evaluated under multiple regulatory frameworks, sometimes with different reporting conclusions.
Key distinction: A complaint is an input into the quality and post-market system. “Reportable event,” “serious incident,” “incident,” and “adverse event” are regulatory classifications or terms used under different market frameworks. They should not be treated as a single globally interchangeable definition.
If your organization requires independent help in evaluating complaints, investigating, deciding reportability, or cross-market vigilance, explore our Medical Device Complaint Handling and Vigilance Review Services.
What is medical device reporting?
Medical device reporting is the process of submitting qualifying device-related events or incidents to the appropriate regulatory authority under the requirements applicable to that market.
The terminology and criteria differ by jurisdiction. In the United States, FDA’s Medical Device Reporting regulation under 21 CFR Part 803 requires manufacturers to report information reasonably suggesting that a device may have caused or contributed to a death or serious injury, as well as certain malfunctions that would be likely to cause or contribute to death or serious injury if they recurred. Importers and device-user facilities have their own reporting responsibilities.
On the other hand, EU MDR uses terms such as incident and serious incident. The vigilance requirements of Great Britain are handled by the Medicines and Healthcare products Regulatory Agency (MHRA). Canada makes use of the term reportable incidents under its Medical Devices Regulations, and Australia uses medical-device adverse-event reporting requirements.
That is why a global procedure should not rely on one generic definition of a “reportable complaint.”
How does a complaint become a reportable event?
A complaint is the broader quality-system input. It may allege a problem involving device quality, safety, performance, reliability, effectiveness, labeling, packaging, servicing, or another device-related characteristic.
Complaints can reach the manufacturer through patients, healthcare professionals, distributors, importers, service teams, sales personnel, clinical partners, or other channels. FDA, for example, explicitly links complaint handling and MDR evaluation and states that complaints need to be evaluated to determine whether they represent reportable adverse events.
A reportable event, by contrast, is the outcome of applying the relevant jurisdiction’s reporting criteria to the available event information.
Not every complaint is reportable. Every complaint should, however, receive an appropriate reportability assessment where the information could potentially meet applicable reporting criteria.
Importantly, not every reportable event necessarily originates through a conventional customer complaint. A manufacturer may identify potentially reportable information through testing, service data, literature, trend analysis, regulatory communication, or other post-market sources.
Is this medical device complaint reportable?
There is no reliable global yes/no shortcut. A stronger approach is to work through the event systematically.
1. What actually happened?
Begin with the determination of the facts surrounding the event. Was there an equipment failure or an alleged failure? How was the device used? How did it perform? Was diagnosis, monitoring, or treatment affected?
Do not start by trying to prove that the device caused the outcome. Start by establishing what is known and what remains uncertain.
2. What was the patient or user outcome?
Determine whether the event involved death, potentially serious injury or deterioration in health, medical or surgical intervention, impairment, delayed treatment, or no actual injury.
Hospitalization or medical intervention can be highly relevant, but should not automatically be treated as satisfying every jurisdiction’s definition of serious injury. The applicable regulatory definition still needs to be applied.
3. Did the device cause or contribute?
The question is often broader than confirmed causality.
For FDA MDR purposes, a device may have “caused or contributed” even when it was only a factor in the death or serious injury. FDA’s reporting framework therefore does not require manufacturers to wait for absolute proof of causality before considering reportability.
Assume direct failure, missed diagnosis or treatment, incorrect findings, failure during use under critical conditions, label problems, or other circumstances in which the device may have contributed.
4. Was there a malfunction or device-related deficiency?
Assess hardware, software, alarms, sensors, power systems, safety features, components, labeling and other relevant functions.
For U.S. manufacturers, a malfunction can be reportable without an actual injury if recurrence would likely result in death or serious injury.
5. What could happen if it happened again?
This is where apparently minor events can become regulatory concerns.
Ask whether recurrence could result in death, serious deterioration, delayed critical treatment, an incorrect diagnosis or another serious consequence. Also consider whether intervention, a backup device or simple good fortune prevented a more serious outcome this time.
MHRA guidance similarly recognizes incidents in which serious harm was avoided because of intervention or the particular circumstances and requires assessment of what might happen if the event occurred again.
6. Which market rules apply?
Once the team understands the event, it can conduct jurisdiction-specific assessments.
Which medical device complaints may be reportable?
Certain scenarios should prompt particularly careful review.
Deaths and potentially device-related serious outcomes
All cases in which there is an involvement of death need immediate analysis of whether the device was responsible for the occurrence or not. The uncertainty about the involvement of the device at the beginning of the analysis does not mean that the start of the reportability assessment should be delayed until the root cause is known.
Serious injury or serious deterioration in health
Situations in which there is a threat to life, deterioration, impairment, intervention to prevent serious harm, or serious consequences of diagnosis and treatment might meet the reporting requirements.
The specific criteria vary from place to place; hence, the phrase “serious injury” needs to be evaluated according to the market criteria.
Malfunctions without actual injury
No injury does not automatically mean no report.
FDA mandates that manufacturers report certain malfunctions due to the possible result of the malfunction if it were to occur again. The UK framework also captures incidents that might have resulted in death or serious deterioration, including situations where the outcome was avoided by intervention.
A failed alarm, loss of a safety-critical function or power failure during critical use can therefore require more scrutiny than the observed outcome alone might suggest.
Incorrect diagnostic or monitoring results
False-negative results, false-positive results, delayed alarms, incorrect measurements, missed detection and software calculation errors should be evaluated in their clinical context.
For example, an incorrect measurement that has no meaningful effect on clinical management may have a different regulatory consequence from the same technical error when it delays treatment or produces an inappropriate intervention.
Labeling, packaging and use-related events
Labeling or packaging problems can also have reportability implications when they contribute to serious outcomes or create the potential for serious harm.
Examples include loss of sterility because of packaging failure, instructions that contribute to serious misuse, or labeling that leads to inappropriate treatment.
Which complaints may remain non-reportable?
This might include cosmetic damage that does not affect either safety or performance, shipping damage discovered prior to usage of the device, user dissatisfaction without any identified deficiencies in the device, and finally, some minor performance problem for which all the facts support the conclusion that any future recurrence would not create reportable consequences.
Those examples are not automatic exemptions. The full context still needs to be assessed.
More importantly, non-reportable does not mean no further action. A complaint may still require investigation, trend analysis, CAPA, supplier action, risk-management review, labeling changes or product improvement.
Where recurrence or systemic failure is suspected, see when medical device complaints should trigger CAPA and Elexes’ CAPA management support.
Why can the same battery failure lead to two different reporting conclusions?
Consider a battery-operated blood-pressure monitor that intermittently loses power.
Scenario A - Routine home monitoring:
The problem is noticed by the user, the test is repeated using another device, and no treatment decision is delayed. This event may, in the end, be determined to be non-reportable based on all the facts. But regardless of the final determination, the problem will need to be investigated, especially when the recurrence suggests a battery, supplier or broader product-quality problem.
Scenario B - Urgent clinical use:
A healthcare professional uses the monitor in order to take a reading, make a decision about the treatment, but is unable to get a reading because the monitor loses power, thus causing treatment to be delayed because of serious deterioration.
The technical defect is the same. The clinical context is not.
That difference can materially change the assessment of device contribution, foreseeable recurrence and potential harm.
Which medical device regulator should be notified?
Start with the affected market, but do not stop there. Determine where the device was supplied, where the event occurred, which device configuration was involved and which regulated entity holds the applicable reporting responsibility.
FDA imposes different reporting obligations on the manufacturer, importer and device-using facility. EU manufacturers report serious incidents via the appropriate vigilance procedure to the respective competent authority. Manufacturers in Great Britain need to report qualifying vigilance cases to the MHRA. Health Canada guidelines require incident reporting by manufacturers and importers, where applicable. In Australia, mandatory reporting requirements exist for sponsors related to device adverse events and mandatory incident reporting by health care facilities started on 21st March 2026.
For detailed reporting windows rather than authority selection, see Medical Device Incident Reporting Timelines: FDA, EU, UK, Health Canada and TGA.
The person who receives the complaint may not be the person who reports it
A distributor may receive the original customer complaint. A field-service engineer may discover the failure. An importer may first learn about an incident.
That does not necessarily mean that the entity owns every formal reporting obligation.
Effective medical device reporting for manufacturers therefore depends on escalation pathways that move potentially reportable information quickly to the correct regulated entity and responsible regulatory team.
Can an incident in one country affect another market?
Yes, potentially – but it does not automatically mean the same report must be filed everywhere.
A manufacturer should consider whether the same device, design, software version, component, supplier, intended use or failure mechanism exists in other markets.
This is not merely theoretical. The FDA’s reporting guidance covers the issue of adverse events that take place outside the U.S. and notes that foreign events may qualify as being reportable if they involve U.S. cleared or approved devices or certain similar U.S. devices.
Canada also contains specific provisions addressing certain incidents occurring outside Canada and separate foreign-risk notification obligations, illustrating why cross-market assessment cannot be reduced to “report only where the complaint occurred.”
For example, a battery failure reported in Australia may justify assessment of devices using the same power system in the United States, EU, Great Britain and Canada.
A practical global approach is to maintain:
⦿ one consistent underlying event record;
⦿ market-specific reportability assessments;
⦿ clearly assigned reporting owners;
⦿ separate jurisdiction-specific reporting clocks; and
⦿ documented rationale for each market decision.
The facts should remain consistent even where the regulatory conclusions differ.
Seven medical device reporting mistakes that weaken the decision
1. Assuming no injury means no report.
Potential recurrence and near-miss scenarios can be critical.
2. Waiting for the investigation to finish before assessing reportability.
Investigation and reporting assessment should proceed in parallel where appropriate.
3. Reviewing only the country in which the complaint was received.
Other marketed versions or jurisdictions may require assessment.
4. Using a checklist without considering clinical context.
The same malfunction may have very different consequences in different use environments.
5. Ignoring the consequence of recurrence.
This is particularly important for malfunction and near-miss scenarios.
6. Recording “non-reportable” without the reasoning.
A conclusion is much easier to defend when the evidence and decision logic are clear.
7. Failing to route the event to the correct regulated entity.
A strong complaint procedure must address both assessment and communication responsibilities.
Elexes’ perspective: Complaint systems often fail at the handoff points. The complaint may be logged and investigated correctly, yet the event never reaches the person responsible for vigilance, cross-market review, CAPA, supplier quality or risk management. Effective complaint handling therefore depends as much on downstream decision architecture as it does on the initial complaint record.
A defensible reporting decision starts with the event, not the complaint label.
Not every medical-device complaint needs to be reported to a regulator. Every potentially relevant complaint does, however, need a disciplined assessment.
A defensible decision considers what happened, the patient or user outcome, whether the device may have contributed, whether a malfunction occurred, what recurrence could cause, and which market-specific rules apply.
The analysis should not end once an event is classified as non-reportable. Complaint information may still need to feed CAPA, trend analysis, risk-management review, supplier quality, post-market surveillance, or product change decisions.
Elexes can independently review selected complaint files, investigation adequacy, reportability rationale and cross-market vigilance assessments, helping your team identify gaps before they become reporting, audit or post-market issues.
Explore Medical Device Complaint Handling and Vigilance Review Services
FAQs
Does every medical device complaint need to be reported?
No. Complaints need to be evaluated against the applicable reporting criteria, but only events meeting those criteria require mandatory regulatory reporting. FDA, for example, distinguishes the broader complaint population from complaints that qualify as MDR-reportable events.
Can a medical device malfunction be reportable if nobody was injured?
Yes. Under FDA MDR requirements, manufacturers must report certain malfunctions when recurrence would be likely to cause or contribute to death or serious injury. There are other regulatory systems that consider the same situation where death or serious injury might have resulted but was averted.
Does a reportable incident in one country need to be assessed in other markets?
Potentially. The manufacturer should evaluate whether the affected or similar device, component, software, labeling or failure mechanism exists in other markets and then apply each jurisdiction's requirements separately. A foreign event can, for example, have U.S. MDR implications in circumstances described by FDA guidance.
