How a firm told you is a field too
openFDA's recall data carries a field for how a firm first notified the public — telephone, letter, press release — kept separate from the field that says why it recalled at all. FDA Radar's own ingestion reads it and doesn't carry it into the record yet.
By Connor Griggs — Regulatory & Quality Strategist
A device recall answers two different questions, in two different fields, and only one of them tends to get read. reason_for_recall says why. A separate field, initial_firm_notification, says how the firm told anyone at all — and it is telling you something the reason for recall never does.
The field, and what it isn’t
openFDA defines initial_firm_notificationas the method or methods by which a firm first notified the public or its consignees of a recall — the practical answer to whether word went out by telephone, by letter, by press release, by email, or some combination filed as a single string. It has been part of the device enforcement report only since the underlying data format changed in June 2012; a record published before that date won’t carry it, and openFDA’s own account of the change doesn’t explain why it happened, only that it did. The field is not a measure of severity, and it is not the recall classification. A Class III recall announced by press release and a Class I recall announced by a letter to three named accounts both fit the field exactly as designed.
Why the method is its own signal
How a firm chooses to notify says something about how it expects the news to travel, and that is not the same fact as how serious the underlying defect is. A press release reaches the trade press — and, often, a monitoring feed — before a specific customer’s own paperwork does. A letter to named consignees reaches exactly the accounts on that list, on whatever schedule the mail runs, and no one else. A recall a Federal Register or enforcement digest surfaced this week, filed under a notification method of Letter, may not yet have reached a specific consignee reading the same feed — not because the recall is quiet, but because the channel the firm chose is slower than the one that told you first.
What FDA Radar does with it today
FDA Radar’s enforcement ingestion reads the field FDA publishes — it arrives in the same payload as recall_number and reason_for_recall— and does not carry it into the record a reviewer or a reader sees today. The reason-for-recall prose, the firm, the classification: those make the trip into the item’s stored facts. The notification method doesn’t, which means a habit built on the assumption that every field FDA Radar fetches is a field FDA Radar kept would be wrong about this one specifically.
The practice
Until that changes, the method is worth pulling directly from openFDA’s own record for anything under close triage — not to second-guess a classification, but to gauge how much lead time a firm’s channel choice bought, or cost, the people downstream of its notice. Per what FDA Radar monitors and how often, that is regulatory intelligence about how a record was built, never regulatory advice about what a specific recall means for your specific device.
Primary sources
- FDA — Enforcement Report Information and Definitions
- openFDA — Device Enforcement: Understanding the API Results
- openFDA — Device Enforcement overview
- FDA Radar — what we monitor and how often
Regulatory intelligence, not regulatory advice. This post describes method and published FDA records as of its date; decisions about a specific device belong with your regulatory professional.