The Hidden Regulatory Exposure in Historical Complaint Records
The complaint was closed. The question is whether the reporting decision inside it would still stand up today.
Complaint handling is usually measured by throughput: complaints received, investigated and closed. Reporting obligations are measured differently — by whether the right decision was made, within the right time, from the right starting date. A complaint file can be closed on time and still contain a reporting decision that would not survive scrutiny.
What the requirements say
In the United States, a manufacturer must submit an MDR report no later than 30 calendar days after it receives or otherwise becomes aware of information that reasonably suggests a device it markets may have caused or contributed to a death or serious injury, or has malfunctioned and would be likely to cause or contribute to a death or serious injury if the malfunction were to recur.[1] "Become aware" is defined in terms of when any employee acquires that information — not when the complaint is investigated or closed.[2] Shorter, five-work-day reports apply in defined circumstances, including where remedial action is needed to prevent an unreasonable risk of substantial harm.
Under the QMSR, complaint records for complaints that must be reported under Part 803, or that are investigated, must record the device name, the date received, any UDI or UPC and other device identification, the complainant's contact details, the nature and details of the complaint, any correction or corrective action, and any reply to the complainant.[3] FDA's MDR guidance for manufacturers sets out the agency's current thinking on these decisions.[4] ISO 13485:2016 requires complaint handling to include a determination of whether information must be reported to regulatory authorities.[7]
In the European Union, MDR Article 87 requires serious incidents to be reported immediately and no later than 15 days after the manufacturer becomes aware of them; no later than 10 days in the event of a death or an unanticipated serious deterioration in a person's state of health; and no later than 2 days for a serious public health threat.[5] MDCG 2023-3 explains that the awareness date is day zero, and that where later information changes an incident into a serious incident, the original awareness date should still be identified.[6]
Our interpretation: where historical exposure hides
This is industry interpretation, not legal advice. Reviewing closed complaint populations, the same weaknesses tend to recur:
- "Not reportable" recorded without a rationale that addresses the actual reporting criteria.
- Malfunction complaints assessed only on what happened this time, not on whether the malfunction would be likely to cause or contribute to serious injury if it recurred.
- Awareness dates recorded as the investigation or closure date rather than the date information first reached the organisation.
- Device identification missing, so similar events across lots, products or years cannot be linked.
- Clusters of individually minor complaints that were never looked at together.
- Decisions that predate later information — a new failure investigation, a field action, a similar event — which may change how the original complaint should be read.
Closure measures the complaint process. Reportability measures the decision inside it.
A practical retrospective review
- Define the population and period, and agree the criteria with Regulatory Affairs before anyone starts reading.
- For each complaint, separate the facts in the record from the conclusion drawn from them.
- Check the awareness date against the earliest evidence of receipt, not the workflow dates.
- Re-assess malfunction complaints against the "if it were to recur" test.
- Treat a missing rationale as an open question, never as an implied "not reportable".
- Route anything that may require a late or supplemental report to the people accountable for regulatory decisions — the review produces questions, not conclusions.
Where QMSROOT fits
This section describes QMSROOT, not a regulatory requirement. PMS Radar reviews complaint populations with FDA MDR and EU MDR reporting exposure kept visible, separates what the record states from what is missing, and records every determination as a human disposition. It supports the review; reportability decisions remain with the manufacturer's qualified Regulatory and Quality professionals.
- 1. 21 CFR 803.50 — Individual adverse event reports; manufacturers
- 2. 21 CFR 803.3 — Definitions ("become aware")
- 3. 21 CFR 820.35 — Control of records (complaint records)
- 4. FDA — Medical Device Reporting for Manufacturers, guidance (November 2016)
- 5. EUR-Lex — Regulation (EU) 2017/745 (MDR), Article 87
- 6. MDCG 2023-3 Rev.2 — Questions and Answers on vigilance terms and concepts
- 7. ISO — ISO 13485:2016 (clauses 8.2.2 Complaint handling, 8.2.3 Reporting to regulatory authorities)
Would your historical complaint decisions stand up today?
See how PMS Radar keeps reporting exposure and evidence gaps visible across a complaint population.
Explore PMS Radar