Nationwide doesn't mean your building
openFDA's recall records carry a distribution_pattern field describing where a firm first shipped a device — and the field's own definition says plainly that what happens after that first shipment isn't in it.
By Connor Griggs — Regulatory & Quality Strategist
A recall record reads “Nationwide” in its distribution field, or names six states that don’t include yours, and the read is tempting either way: either the whole country should assume exposure, or a state absent from the list is a state that’s clear. openFDA’s own definition of that field says neither read is safe on its own, and it says so in the field reference, not in a caveat buried somewhere else.
What the field actually measures
distribution_pattern is openFDA’s device enforcement field for the general area of initial distribution— wherever the recalling firm’s own records show the product first went once it left the firm. At its most precise it reads like a shipping manifest: FDA’s field reference gives “Distributors in 6 states: NY, VA, TX, GA, FL and MA; the Virgin Islands; Canada and Japan” as an example of the format. At its most common it reads like one word. Both are the same field, measuring the same thing: where the firm itself shipped first, not where the product is now.
Nationwide is a defined term, and it isn’t universal
Even the common case has a specific definition behind it. openFDA defines “Nationwide” to mean the fifty states or a significant portion of them— not a certification that every state received product, just the broadest bucket the field has. A recall that reads Nationwide is telling a reader the distribution was broad, not that it was total.
The gap the field states outright
The sharper limit is the one FDA’s own reference volunteers without being asked: subsequent distribution by the consignees to other parties may not be included. A firm reports where it shipped a device first — to a distributor, a group purchasing organization, a regional dealer. What that distributor did with it next, which hospitals or clinics or second-tier resellers it reached, is a layer of the supply chain the field was never built to capture. A reader two or three hops downstream from the recalling firm can be looking straight at the correct record and still find nothing that names them, by the field’s own definition of what it covers.
distribution_pattern answers where a firm shipped first. It does not answer, and says it does not answer, where the product ended up.
Where the real answer actually lives
The question distribution_pattern can’t settle — did a specific downstream account actually receive the recalled units — is exactly what 21 CFR 7.42’s recall strategy is built to answer, on the recalling firm’s side. That rule has the firm set a depth of recall— how far down the chain, to the wholesale, retail, or user level — and run effectiveness checks confirming that consignees at that depth were actually notified and acted. That process runs firm-to-consignee, directly, and its outcome doesn’t feed back into the enforcement report’s distribution_pattern field, which is typically filed at the point the recall is first reported. The authoritative answer to “did we get one” is the firm’s own recall notice to its direct accounts, not a summary field written before that notification process even finished.
The practice
Use distribution_pattern to widen a search, not to close one. A state or region named in the field is a clear signal to investigate. A vague or absent field, or a position several links downstream from the recalling firm in the supply chain, is not a signal of safety — it’s the field admitting it wasn’t built to reach that far. FDA Radar’s recall corpus mirrors openFDA’s device enforcement records exactly as published, distribution_pattern included; per what we monitor and how often, that record is a starting point for the question, never a substitute for confirming receipt directly with a supplier or distributor — regulatory intelligence and method, not a determination for any specific facility, which is a judgment for whoever owns that supply relationship.
Primary sources
- openFDA — Device Enforcement field reference
- openFDA — Device Enforcement overview
- eCFR — 21 CFR 7.42, Recall strategy
- eCFR — 21 CFR Part 7, Subpart C, Recalls (Including Product Corrections)
- FDA — Recalls, Corrections and Removals (Devices)
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.