The product code that doesn't exist yet
FDA's classification database has no row for a device type until a De Novo request is granted — the product code, the regulation number, even the classification itself are created by the grant order, not looked up before it. A watch keyed to "your product code" cannot fire on a category that is still being invented.
By Connor Griggs — Regulatory & Quality Strategist
Type a product code into a portfolio setup form for a device with no predicate, and the lookup comes back empty — not because the form is broken, but because FDA has not yet written the row that code would occupy. For a genuinely novel device, the product code does not predate the regulatory decision. The decision creates it.
Every other pathway starts with a code that already exists
A 510(k) submission cites a predicate, and a predicate already has a product code — the applicant is arguing equivalence to something FDA classified previously. A PMA for an existing device type slots into a classification that is likewise already on the books. Both pathways presuppose the row in FDA’s classification database that a lookup like FDA Radar’s own product-code lookup reads at signup: one three-letter code in, eleven fields out — device class, regulation number, review panel, the rest — because the code has been sitting in openFDA’s classification API since whichever earlier decision first assigned it.
De Novo is the pathway that has nothing to look up
21 CFR Part 860, Subpart D governs the alternative: a device with no legally marketed predicate, low or moderate enough risk that general or special controls provide reasonable assurance of safety and effectiveness, can request classification directly rather than arguing equivalence to something that doesn’t exist. FDA has 15 calendar days to tell the requester whether the request is accepted for review, and up to 120 days from acceptance to issue an order — granting the request under 21 CFR 860.260, or declining it. Nothing about a product code appears anywhere in the request itself. There is nothing to cite, because the classification being requested has never existed.
Every other submission argues into an existing category. A De Novo request argues that the category should exist at all.
What the grant order actually does
The order granting a De Novo request is the event that creates the row. FDA assigns a new three-letter product code, establishes the classification regulation the device will sit under — a new section, not a borrowed one — and, for a device classified into Class II, publishes the special controls that will govern it and every device that follows it into the same code. The device that requested the classification becomes, from that date, the first entry under it — and the first available predicate for anyone who follows with a 510(k) into the category the grant just opened. None of that exists a day earlier. The product code is a consequence of the order, not an input to it.
What a portfolio tool honestly does with the gap
A lookup built on openFDA’s classification API cannot return a code that doesn’t exist in it yet, and the honest behavior is to say so rather than to guess. FDA Radar’s own product-code lookup treats an empty result as an answer, not an error: no such code, stated plainly, rather than a best guess dressed up as a match. For a device moving through De Novo review, that is the correct answer for as long as the request is pending — there is nothing yet to derive a profile from, because FDA itself has not yet decided what the profile is.
The practice
A portfolio built around a first-in-category device has to watch a different document during the gap: the De Novo request itself, and FDA’s public decision summaries for granted requests in the relevant specialty area, rather than a product-code filter that has nothing to match against yet. The day the grant order posts is the day the product code, the regulation number, and the classification all come into existence at once — and it is also the earliest date any watch keyed to that code could possibly have fired. Setting up the watch before that date accomplishes nothing; checking for the grant itself is the only thing that does.
Whether a specific device qualifies for De Novo rather than a 510(k), and what a competitor’s granted De Novo means for your own predicate strategy, is a determination for a regulatory professional working the file — this describes a mechanism in how classifications come to exist, not a reading of any specific submission. Once a code exists, FDA Radar treats it exactly like any other: a lookup, not a promise, joined against your portfolio the same day it becomes real.
Primary sources
- eCFR — 21 CFR Part 860, Subpart D, De Novo Classification
- FDA — De Novo Classification Request
- Federal Register — Medical Device De Novo Classification Process (final rule)
- openFDA — Device Classification 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.