Exempt covers the type, not the use

A product code marked exempt reads like a green light — no 510(k) needed for this generic type of device. FDA’s own regulations say the green light has an edge, and the edge is written into the classification regulation itself, not left to inference.

One exemption, sixteen sections

Most Class I devices, and a number of Class II devices, are exempt from section 510(k) premarket notification — FDA’s classification regulation says so directly, generic type by generic type. The same body of regulations that grants the exemption also limits it, in the same structure repeated across every one of FDA’s device-classification parts, 862 through 892: a numbered section — 862.9, 864.9, and on through 892.9 — titled, in every part, Limitations of exemptions from section 510(k).

What the limitation actually says

21 CFR 862.9 states the boundary in two parts. First, a ceiling: the exemption for a generic type of device applies “only to the extent that the device has existing or reasonably foreseeable characteristics of commercially distributed devices within that generic type” — for an in vitro diagnostic, only to the extent a misdiagnosis from using it “would not be associated with high morbidity or mortality.” Second, two named triggers that pull an otherwise-exempt device back under 510(k): the device is intended for a use different from the intended use of a legally marketed device in that generic type, or the device operates using a different fundamental scientific technology than a legally marketed device in that generic type. FDA supplies its own examples in the regulation’s text: a surgical instrument that cuts tissue with a laser beam instead of a sharpened metal blade, or an in vitro diagnostic that detects an infectious agent with DNA-probe or nucleic-acid hybridization technology instead of culture or immunoassay. Same generic type on paper. Different device under 862.9.

What a lookup actually returns

FDA Radar derives a product’s pathway from the classification record’s own submission_type_id field — the value FDA assigns is 4, and the profile a user confirms at signup renders it as 510(k) Exempt. That value describes the generic type’s status in FDA’s classification database. It is not, and was never built to be, a check of whether this particular device’s actual intended use or actual technology still sits inside the boundary 862.9 and its fifteen counterparts draw around that type. No field in the classification record carries that comparison, because it isn’t FDA’s comparison to make at the database level — it is the manufacturer’s, made once at design and owed again every time the intended use or the underlying technology moves.

The practice

An exempt product code is a statement about a generic type, per what we monitor and how often, and it stays accurate exactly as long as a specific device stays inside that type’s existing and reasonably foreseeable characteristics. The moment a device’s intended use or its underlying technology diverges — a new indication, a new energy source, a new detection method — the exemption the product code still shows no longer describes the device being sold. This is regulatory intelligence and method, never regulatory advice about whether a specific device still qualifies for its generic type’s exemption — that comparison belongs with your regulatory professional, not a product-code lookup.