The malfunction report that never reaches FDA

An importer files exactly the report the rule asks for, on the clock the rule sets, to the address the rule names. For one entire category of event, that address was never FDA — not eventually, not as a matter of routing, by the rule’s own design.

Two names, one role, two parts

21 CFR Part 807 — establishment registration and device listing — names this party the initial importer, defined at 807.3: the importer that moves a foreign-made device from the manufacturer toward the person who makes final delivery to the end user. 21 CFR Part 803 — medical device reporting — never uses that term. Its own definitions section, 803.3, calls the same functional party simply the importer. Same job, same person in the supply chain, two different words, assigned in two different parts of the same subchapter for two different compliance programs.

803.40 forks on what happened, not on who’s asking

21 CFR 803.40 splits the importer’s own reporting duty by event type, and the two branches don’t end at the same place. 803.40(a) covers a death or serious injury: the importer reports it to both FDA and the manufacturer, within 30 calendar days of becoming aware. 803.40(b) covers a malfunction that would likely cause or contribute to death or serious injury if it recurred: the importer reports it to the manufacturer only. Nothing in 803.40 routes that report to FDA, on any clock, from the importer’s own hand.

A death reaches FDA from the importer directly. A malfunction, filed by the same importer under the same section, reaches FDA only if the manufacturer later decides, under its own separate duty, that the event belongs in a report of its own.

What that means for the record you’re reading

An importer’s malfunction report never becomes its own entry in FDA’s device event data under the importer’s name — by rule, it can’t, because the rule never sent it there. Whatever eventually surfaces in FDA’s own record for that malfunction arrives later, if at all, filed under the manufacturer’s own duty, on the manufacturer’s own clock, worded in the manufacturer’s own account of the event. A reviewer reading device-event volume as a complete inventory of what every importer in a supply chain currently knows about malfunctions is trusting a pipe that, on that branch, the rule never connected to FDA at all.

The practice

This is a description of where 803.40 requires a report to go, never a judgment about whether a specific malfunction was serious enough to have warranted one, or about what a specific importer should have filed on a specific device. That determination belongs with the regulatory or quality professional reading the event against the device’s own facts.

FDA Radar’s five monitored sources don’t reach device-event reports at all — see what we monitor and what we deliberately don’t. The reporting duty described here, and the gap it leaves in FDA’s own record, runs whether or not any tool is reading it.