FDA Medical Device Product Codes: Assignment and Responsibility
For regulatory and clinical affairs teams, understanding how FDA medical device product codes are assigned is foundational to accurate device classification, predicate selection, and submission strategy. A product code determines the regulatory pathway, applicable special controls, and the review panel that will evaluate a submission—making it one of the earliest and most consequential classification decisions in a device's regulatory history.
This analysis examines the mechanism by which FDA product codes are created and maintained, the specific organizational body responsible for their assignment, and the data elements that accompany each code in the FDA Product Classification Database. It draws on FDA's own classification records, De Novo decision summaries, and automatic-classification letters to establish how new generic device types and their associated codes come into existence.
Want to ask Rhizome your own regulatory questions? Try it for free.
How FDA medical device product codes are assigned, and who is responsible
What a product code actually is
An FDA product code is a three-letter identifier that points to a single entry in FDA's device classification system. It is not a free-standing label. Each code is bound to a specific generic device type and carries a defined set of attributes 123.
Using product code QZS as a worked example, a classification record contains 76:
| Field | Value for QZS |
|---|---|
| Product code | QZS 76 |
| Generic device name | Software-Aided Adjunctive Diagnostic Device For Use By Physicians On Lesions Suspicious For Skin Cancer 76 |
| Device class | Class II 76 |
| Classification regulation (21 CFR) | 878.1830 76 |
| Medical specialty / review panel | General, Plastic Surgery (SU) 76 |
| Submission type | 510(k) 76 |
| Definition | Prescription software device that analyzes optical or other physical properties of a skin lesion and returns a classification, for adjunctive second-read use 76 |
| GMP exempt | No 76 |
| Implant | No 76 |
| Life-sustaining/supporting | No 76 |
| Third-party eligible | No 76 |
The same structure repeats across the database. Every code maps to one classification regulation number, one of the three device classes, and one medical specialty panel 124. For example, QRN (Radiation Therapy Marking Device) sits under 21 CFR 892.5785 in the Radiology (RA) panel as Class II, while LEK (Transilluminator) is Class III under 892.1990, also Radiology 14. The device class and panel are properties of the classification entry the code represents, not attributes assigned to an individual manufacturer's product 124.
Who is responsible
Product codes are created and maintained by FDA, specifically CDRH (for most devices) as part of the device classification process. The classification records pair each code with its regulation, class, and review panel, and it is FDA that populates and controls those entries 1276. In the classification and De Novo decision documents, the determinations are issued by FDA, and several of the automatic-classification letters are signed out explicitly by CDRH 60636466.
Two points of nuance the source records support:
- The medical specialty / review panel field (for example, SU, RA, EN, GU) identifies the FDA specialty area responsible for reviewing that device type. The records show the panel as the responsible specialty, but they do not state that the panel itself assigns the three-letter code 124.
- The classification records confirm what a code is linked to, but they do not spell out who inside FDA keys in the letters or the rule for choosing them. What the records do establish is that these are FDA-controlled classification entries 1276.
How a code gets assigned in practice
There are two common situations.
1. An existing device type already has a code
Most devices fit an existing generic type. In that case the applicant does not get a "new" code; the device is matched to the product code that already describes its generic type, which in turn fixes the applicable regulation, class, and review panel 124. This is the routine path behind most 510(k) clearances, where the submission is filed under the product code that matches the device's generic type 76.
2. A novel device type needs a new code (classification and De Novo)
When a device does not fit any existing classification, a new generic type, a new classification regulation, and a new product code are created through a classification action. The De Novo decision summaries are explicit about this sequence 505152:
- FDA states it will "classify the device," and that "this classification shall be the initial classification of the device" 505152.
- The order then identifies a generic type of device and gives it a generic name, and concludes the class (for example, "FDA concludes that this device should be classified into Class II") 505152.
- A new regulation number and product code are assigned to that newly classified generic type. Concrete examples from the decision records:
These determinations are made by FDA. In the De Novo summaries the decision is attributed to FDA ("FDA has determined," "FDA concludes"), and in the older automatic-classification letters the issuing office is named as CDRH 50515260636466. Once the De Novo is granted, the newly created generic type, with its regulation and product code, becomes available in the classification database and can serve as a predicate framework for later 510(k) submissions in that category 505152656770.
Why the product code matters for a submission
Because the product code is tied to the classification regulation, device class, review panel, and submission type, identifying the correct code effectively sets the regulatory pathway for a device 1276. The submission type field on the record signals the expected route (for example, 510(k) for QZS), and the flags (implant, life-sustaining/supporting, GMP exemption, third-party review eligibility) carry additional regulatory consequences that also travel with the code 76. Choosing the wrong code, or assuming a novel device fits an existing one, can put a submission on the wrong pathway, which is why product code selection is an early, deliberate step in device regulatory strategy rather than a clerical one 1276.
Limitations and good follow-ups
- The classification records confirm the structure and linkages of product codes but do not publish the internal convention FDA uses to pick the three letters 1276.
- This article covers the US system. EU nomenclature (EMDN) under MDR/IVDR is a separate scheme and would be worth a dedicated look.
- Useful next questions to put to Rhizome: how to search the classification database to find the right code for a specific device; how a 513(g) Request for Information is used to get FDA's view on classification and the applicable code; and how to read a De Novo decision summary to reuse a newly created product code as the basis for a 510(k).