A provider letter doesn't need a recall

A device safety notice can reach every hospital in the country without ever touching a recall, a correction report, or an enforcement database row — because FDA built a channel for exactly that gap, and some weeks FDA writes the letter in it itself.

A page, not a database row

FDA’s Letters to Health Care Providers channel posts device-safety notices to clinicians and facilities, indexed by year on fda.gov, separate from the Medical Device Recalls database and from 21 CFR Part 806 correction-and-removal reporting. The drug side has an older, better-documented version of this — FDA’s 2014 final guidance on Dear Health Care Provider Letters governs manufacturer-written letters about drugs and biologics — but that guidance’s own scope never reaches devices. For devices, the letters aren’t reliably manufacturer-written either. FDA’s own Import Alerts for Certain Olympus Medical Devices Manufactured in Japan letter, first posted June 24, 2025 and broadened again in October 2026 to cover certain enteroscopes and an ingestible telemetric gastrointestinal capsule imaging system, carries FDA’s own byline, not Olympus’s.

What travels this channel and nothing else

Some of what moves through it runs beside a recall without being one. A May 6, 2026 letter notified providers of a supply disruption in neurosurgical patties, sponges, and strips — product code HBA — after Medline recalled its branded neurosponges over elevated endotoxin levels, a Class II action FDA’s enforcement database does carry. But the letter is not that recall, filed separately, written by FDA, and doing a different job: naming the product code added to FDA’s Medical Device Shortages List, and giving conservation and sourcing guidance — reserve supply for intracranial cases, avoid stockpiling, diversify suppliers — that no recall notice is built to carry. A team pulling the recall feed for that product code sees Medline’s action. It does not see FDA’s.

The recall database answers what was removed or corrected. This channel answers a question the recall database was never built to carry.

A count Congress now requires

Congress made the gap countable. Section 3307(b) of the Consolidated Appropriations Act, 2023 (Pub. L. 117-328) ordered HHS to report on postmarket device safety-related communications by September 30, 2023, and every two years after. FDA’s most recent report, covering January 1, 2023 through December 31, 2024, counts 51 such communications in total — 27 CDRH Medical Device Safety Communications, 23 CDRH Letters to Health Care Providers, and one CBER communication — tallied as separate categories because they are, functionally, separate instruments: one is FDA’s clinical analysis of an issue and what to do about it, the other is a narrower notice FDA wants on the record quickly.

The practice

Neither category has an openFDA endpoint. There is no structured feed to query by product code, firm, or date — only the year-indexed pages FDA maintains by hand, for the same reason Form 483s have no feed: none exists to build one from. For a product code or firm you track closely, that page is a manual check, on its own cadence, that no API replaces. Whether a specific letter changes anything about how you handle a specific device is a judgment for your own regulatory and clinical team, reading that letter’s own text against your own facts; this is a description of where the letters live and what FDA’s own count of them says, never a determination about any one notice. FDA Radar’s five monitored sources — Federal Register, warning letters, enforcement and recalls, 510(k) clearances, and the classification database — don’t reach this channel either, for the same reason the page itself still has to be read by hand: there is no structured source yet to point a feed at. See what FDA Radar monitors and how often for the rest of the pipeline.