Before you can argue that your device is substantially equivalent to a predicate, you have to establish something more basic: what kind of device it is, in FDA’s own taxonomy. That answer lives in a classification entry — three or four lines of database text that quietly determine your device class, your submission type, and which regulation actually governs you. Most people skim past it. It rewards a closer read.
What the classification database actually is
FDA’s Product Classification database is a search tool laid over 21 CFR Parts 862 through 892 — the sixteen medical-specialty panels (clinical chemistry, cardiovascular, general hospital, physical medicine, and so on) that between them classify every device type FDA regulates. Each entry in the database corresponds to one paragraph of the Code of Federal Regulations. The database makes that regulation searchable by device name and product code; it does not replace the regulation as the source of truth.
That distinction matters more than it sounds like it should. The database summary is FDA’s plain-language gloss on a device type. The regulation it cites — the actual 21 CFR section — is where the legal definition, the device class, and any special controls are written down in full. When the two seem to disagree, or when a device sits awkwardly between two descriptions, the regulation wins.
Reading the fields, one by one
- Device class
- Class I, II, or III, as defined in 21 CFR 860.3. Class determines the baseline regulatory controls — general controls for Class I, special controls added for Class II, premarket approval for most Class III devices.
- Product code
- A three-letter code that is the real search key across FDA’s public databases — 510(k), PMA, MAUDE, and recalls are all indexed by it. Learn your device’s code once and every other search gets faster.
- Regulation number
- The 21 CFR citation for the device type. This is the paragraph to actually read; the database description is a summary of it, not a substitute.
- Submission type
- Whether the device type is generally 510(k)-exempt, 510(k)-required, or PMA. “Exempt” is a starting point, not a guarantee — many exemptions carry limitations that pull a specific device back into 510(k) territory.
- Review panel
- Which of FDA’s medical-specialty divisions reviews the device type. Useful context for who you’re writing for, and occasionally a clue that a device has been classified under a panel that doesn’t match how your team talks about it internally.
Why this matters before you pick a predicate
A predicate has to share the device’s classification — same product code, same regulation, in almost every case. If you go looking for a predicate before you’ve nailed down your own classification, you can spend real time chasing a comparison that a reviewer will reject on the first page. Our predicate selection lesson walks through that comparison in full; this is the step that has to happen first. Once you have a shortlist of candidate predicates, reading their 510(k) summaries is the next move — and the product code is what gets you a clean search instead of a device-name guessing game.
- Read the actual CFR section the database cites — not just the plain-language description above it.
- Confirm the regulation number in eCFR still matches; codified numbering occasionally shifts when a part is amended.
- Check any exemption for limitations. “510(k) exempt” in the summary line is frequently followed by conditions in the regulation text itself.
Where practitioners go wrong
Treating the database description as the legal definition
It’s a summary written for searchability, not a substitute for the regulation. When a device’s features sit at the edge of a description, the regulation’s actual text — not the database blurb — is what a reviewer will cite back to you.
Assuming Class II means 510(k)-required
Class generally tracks with control level, not submission pathway on its own. Some Class II device types are exempt from 510(k) with limitations; read the specific regulation rather than pattern-matching from class alone.
Searching by device nickname instead of product code
Marketing names and internal nicknames don’t index consistently across FDA’s databases. The product code does. It’s a small habit that saves real time over a career.
Sources & further reading
- 21 CFR Parts 862–892 — device classification regulations by medical specialty panel ecfr.gov
- 21 CFR 860.3 — definitions of device class ecfr.gov
- Regulatory Academy — How to choose a 510(k) predicate device regulatoryacademy.com
This essay is provided for general educational purposes and reflects the regulatory landscape as of its publication date. It is not legal, regulatory, or career advice.
