Medical Device Adverse-Event Reporting: The Decision Not to Report

Medical device adverse event reporting fraud hides reportable deaths, serious injuries or dangerous malfunctions from the Food and Drug Administration while keeping a device in use. A whistleblower case connects that concealment to government payments for the device or the care in which it was used. The company may already have the complaint, the test result and the internal warning. For someone in quality, regulatory affairs or clinical support, the telling document may be the decision that kept those facts inside the business.

The manufacturer sits at the center of much of the reporting system. Hospitals and importers send it information about failures, and it evaluates whether those events require a report. That is why the complaint file matters as much as the report the agency eventually receives.

Who Has the Medical Device Reporting Duty?

Manufacturers, importers and device user facilities have different duties under the Food and Drug Administration’s medical device reporting rules. The event, the recipient and the clock depend on the reporting role.

• Manufacturers generally report to the agency within 30 calendar days after becoming aware of information reasonably suggesting that a marketed device may have caused or contributed to death or serious injury. They also report a malfunction likely to cause or contribute to death or serious injury if it recurred in that device or a similar device they market.
• Importers report deaths and serious injuries to the agency and the manufacturer within 30 calendar days after becoming aware of a reportable event. They send reports of qualifying malfunctions to the manufacturer within that same period.
• Device user facilities report device-related deaths to the agency and the manufacturer, if known, within 10 workdays after becoming aware of a reportable event. Serious-injury reports go to the manufacturer, or to the agency when the manufacturer is unknown. The same deadline applies.

User facilities include hospitals, ambulatory surgical facilities, nursing homes and outpatient diagnostic or treatment facilities. Physician offices are excluded from that definition.

A serious injury includes a life-threatening injury or illness, permanent impairment or damage, or an event requiring medical or surgical intervention to prevent permanent impairment or damage. For manufacturers and importers, a dangerous malfunction can trigger reporting before a patient suffers that injury. The question includes what would happen if the failure occurred again.

When the Manufacturer Learns About the Event

For an ordinary manufacturer report, awareness begins when any employee receives information reasonably suggesting a reportable event. The first receipt can precede the date regulatory affairs opens its review. A sales representative’s account, an engineering test or a customer complaint can therefore establish an earlier point in the company’s knowledge.

The expedited manufacturer deadline is five workdays when a reportable event requires remedial action to prevent an unreasonable risk of substantial harm to public health, or when the Food and Drug Administration requests expedited reporting in writing. For the remedial-action trigger, the awareness rule reaches managers supervising regulatory, scientific or technical work and employees responsible for collecting and reporting adverse events. A trend analysis can supply that knowledge.

That puts the company’s own complaint trends beside the individual event. The same recurring failure that engineering can see may be the information that requires a faster report.

The Decision Not to Report Leaves a File

The Food and Drug Administration requires manufacturers, importers and user facilities to retain their deliberations about whether an event was reportable. The file includes the decision to report and the decision not to report. It can refer to engineering reports, medical records and other underlying material, and it must retain the submissions and the agency’s electronic acknowledgments.

The written procedure describes how a complaint should move through the business. The actual complaint, its routing history, the investigation and the final conclusion show what happened when the procedure met a difficult event. Who received the information, who evaluated it and what they relied on are separate parts of that account.

A manufacturer’s investigation reaches information already in its possession, information obtainable from the initial reporter, and information obtainable by analyzing or testing the device. The reporting rules require an explanation of missing information and the efforts to obtain it. Newly obtained required information belongs in a supplemental report within 30 calendar days of receipt.

User error is included in the Food and Drug Administration’s definition of an event caused or contributed to by a device. A conclusion that the device did not contribute to a death or serious injury, or that a recurring malfunction would not be likely to do so, rests on a qualified medical judgment. The supporting information belongs in the event file. The useful comparison is between that conclusion and the testing, clinical account and risk assessment behind it.

Corrections and removals have a separate reporting clock. The rule covers action initiated to reduce a health risk posed by a device or to remedy a violation that may present a health risk, with a deadline of 10 workdays from initiation. Customer letters, changed instructions and the decision to correct the product can show when the company acted on a problem it had already investigated.

Medical Device FDA Reporting Exemptions and Missing MAUDE Reports

Medical device FDA reporting exemptions can change the frequency or form of a manufacturer’s reports. A company’s authorization, its conditions and its reporting history establish which route applied. The Food and Drug Administration can grant an exemption, variance or alternative in writing, impose replacement reporting requirements, and later modify or revoke the authorization.

The exemption letter therefore belongs beside the complaint file. Its coverage, applicable period and reporting conditions explain what the company was required to send. The question becomes whether the company reported the event through the route it was authorized to use.

Alternative Summary Reporting and Voluntary Malfunction Summary Reporting Overlapped

The Alternative Summary Reporting program operated from 1997 through June 2019, when the Food and Drug Administration ended it and revoked its exemptions. The agency’s account of its legacy data explains that these reports were incompatible with public MAUDE and were not publicly available before 2019.

The agency required companion reports beginning in 2017. Adding the Alternative Summary Reporting events to those companion reports can count some events twice.

Voluntary Malfunction Summary Reporting began in 2018, before the older program ended. It permits quarterly summaries of certain device malfunctions, with separate reports for each combination of brand, model and problem codes. Each summary identifies the number of reportable malfunctions, and the summaries are public in MAUDE. Individual death and serious-injury reporting continues.

An eligible device type and a manufacturer’s participation are different facts. The product-code eligibility list identifies types that can participate. The manufacturer’s reporting history establishes its use of the program. The older program’s closure left the agency’s broader exemption authority in place, including case-specific summary reporting for events found in registries, electronic health records and claims.

What the Public Database Can Show

MAUDE supplies reports of suspected device-associated events. Its passive reporting system depends on information from device users and other sources, with missing, inaccurate or unverified information and incomplete reporting. It also lacks the frequency-of-use information needed to turn event counts into a device’s adverse-event rate.

The internal file supplies a different view: what the company received, what it investigated and what it decided to send. Comparing that file with the applicable exemption and the actual submission history is how we examine a missing public report.

The government’s October 2009 audit of device reporting found late reports and weak documentation of the Food and Drug Administration’s own reviews. It also found that incomplete and unusable information hindered analysts. That historical finding puts another question beside whether a report arrived: what useful information did it contain?

What Reporting Failures Have Been Charged?

Concealed reportable malfunctions, misleading accounts of when a defect became known, and safety information withheld from the Food and Drug Administration all appear in device enforcement cases. The cases show where the evidence sat inside the company.

Ancure Failures Reached Company Officials

Endovascular Technologies, a Guidant subsidiary, made the Ancure endograft for abdominal aortic aneurysms. The criminal information said it filed 172 medical device reports. In its guilty plea, the company admitted failing to file an additional 2,628 required reports. The Justice Department’s account of the criminal case explains why the company knew about the failures: a sales representative attended each surgery as a condition of Food and Drug Administration approval, and failure reports were repeatedly tabulated and distributed to company officials.

The criminal information to which the company pleaded guilty described sales representatives teaching doctors to break the delivery-system handle when it became stuck, allowing the catheters to be removed individually. The technique had not been tested, and the product instructions did not explain it. After a patient died during a procedure using the technique, employees concluded that the agency needed to be informed. The company failed to do so while representatives continued describing it during surgeries. Patients and doctors faced risks the company had kept from them.

The same announcement describes a separate $49 million civil settlement of claims that the company’s conduct caused Medicare, Medicaid and the Veterans Affairs Program to pay millions of dollars for adulterated and misbranded devices.

Magellan Changed the Instructions Before Telling FDA

Magellan Diagnostics learned during clearance testing that its LeadCare Ultra device could produce falsely low lead results from venous blood samples. According to court documents described in the company’s criminal case, Magellan launched the device without telling customers or the Food and Drug Administration about the malfunction.

Customers subsequently discovered inaccurate results and complained. Magellan then advised them to wait 24 hours before running their tests, contradicting the approved instructions. The agency learned of the malfunction and that instruction change later. The company’s own testing had also indicated that the same problem affected LeadCare II with venous samples.

Magellan pleaded guilty to distributing misbranded devices. The evidence connected the test results, customer complaints, revised instructions and delayed reporting. The company knew enough to tell customers to change how they used the test before it gave the agency the same account.

Can a Whistleblower Take Legal Action Against a Medical Device Company?

Yes. A False Claims Act case can pursue a manufacturer that knowingly causes false claims for payment, including claims submitted by health care providers. Our review connects the manufacturer’s conduct to the physician’s device decision, the institution’s bill and why the concealed information mattered to government payment.

The payment often sits inside the procedure. Medicare generally packages implant costs into hospital procedure payments, so the relevant claim may be the hospital’s bill for the care in which the device was used. Product records and provider records connect the device to that bill.

A 2020 paper in the Journal of Forensic and Investigative Accounting examines payment claims made misleading by omitted facts. Its point is whether the missing information mattered to the government’s decision to pay.

For device reporting, that means following the withheld safety information through the business: who knew, what clinicians were told, which product they used and what the provider billed. The complaint file explains the reporting decision. The clinical and payment records explain its connection to public money.

A whistleblower case under the False Claims Act can pay 15% to 30% of what the government recovers.

What Kind of Proof Is Needed to Be a Whistleblower?

Useful medical device whistleblower evidence connects the original failure information with the company’s response and the affected claims. Complaint records, engineering results, reportability decisions, customer communications and submitted reports each show a different part of that sequence.

The device identity matters throughout: model, lot or serial number, the event and the date the company learned about it. A changed account of the same failure can be especially revealing. Magellan’s criminal case connected prior knowledge with later customer instructions, while the Guidant complaint alleged a deliberate choice about who would learn of the defect.

You may have seen the complaint before it changed, performed the test that contradicted the conclusion, or received the instruction to keep a finding out of a report. We work with that firsthand knowledge to examine the reporting decision and its connection to a government-funded device or procedure.

When You Know What Stayed Inside the Company

If you know why a serious device problem disappeared between the complaint file and the FDA report, we can connect what you saw to the device’s use and the government payment. We stay beside you through the process and bring in medical device whistleblower lawyers who understand safety-reporting cases. Speak with our whistleblower experts about building your strongest case from what the company kept inside.