Not every signal becomes a recall

openFDA publishes a device’s clearance record, its classification, and its enforcement history — three endpoints, each traced closely on this blog. Some of what CDRH tells the public about a device’s safety never touches any of the three, because the concern hasn’t reached the point any of those records exist to describe.

A policy built to publish before the evidence is settled

FDA finalized its guidance on Emerging Signals on December 14, 2016, after a draft published a year earlier. The policy describes exactly the situation a recall record cannot yet cover: FDA has identified a new causal association, or a new aspect of a known one, between a marketed device and an adverse event; the agency has done an initial evaluation and believes the information could affect patient-management decisions or the device’s benefit-risk profile; and the evidence, while real enough to matter, is not yet fully analyzed, validated, or confirmed. The guidance directs FDA to publish anyway, rather than sit on an unconfirmed signal until certainty arrives.

Not the same gap an Early Alert fills

This blog has already covered CDRH’s Early Alert pilot — a page that posts when FDA believes a specific company’s removal or correction is likely to become the most serious kind of recall, ahead of the classification that would give it a recall number. An Emerging Signal is a different kind of gap. It does not presuppose that any company has taken, or will take, a corrective action at all. FDA can publish one about a device type, a whole category of use, or a pattern across products from more than one firm — a safety concern under evaluation, not a removal already underway. Some emerging signals resolve into a recall later. Many resolve into a label change, updated guidance, or nothing formal at all.

An Early Alert is FDA saying a recall is probably coming. An Emerging Signal is FDA saying it is still finding out whether anything is wrong at all — and telling the public before it knows.

Where it lives, and where it doesn’t

openFDA’s device endpoints — 510(k) clearances, classification, and enforcement — cover exactly the ground their names suggest, and no more. An Emerging Signal carries no recall number, because no recall may ever exist for it; no classification, because CDRH has not classified anything; and no K-number, because it need not concern one specific submission. It is a page on FDA’s own site, updated as the agency’s understanding develops, with no structured endpoint behind it at all. A monitoring pipeline built to poll openFDA for device safety information, however complete against those three endpoints, has no request it can make that would ever return one.

The practice

A product code or device class worth watching for recalls is worth watching for Emerging Signals separately, on FDA’s own schedule for that page, because no downstream feed will surface one for you. Whether a specific emerging signal changes how a specific portfolio or supplier relationship should be handled is a judgment for the regulatory or quality professional holding that file — this is regulatory intelligence and method, about where a category of FDA communication lives, never regulatory advice about what any one signal means for a specific device.

FDA Radar’s recall coverage runs on the openFDA enforcement endpoint, and its Federal Register, warning-letter, and 510(k) coverage each run on the endpoint built for that record, exactly as what we monitor and how often describes. Emerging Signals is not among them — not a gap in how those four are read, but a fifth category FDA never put behind an API to read from at all.