Executive Summary

Product codes for medical devices are assigned by the U.S. Food and Drug Administration (FDA) as part of the device classification and premarket review process. Within FDA, the Center for Devices and Radiological Health (CDRH)—through device-specific offices and divisions—determines the appropriate classification regulation (under Title 21 of the Code of Federal Regulations) and assigns the corresponding product code. FDA also maintains the public product code database used by submitters and reviewers; third party review organizations may reference these codes but do not assign them ^{8485828683273277274285}.

Who Is Responsible

• The FDA’s CDRH assigns and manages product codes. Historical and current documents show this responsibility across CDRH structures such as:
  • Office of Device Evaluation (ODE) and the Office of In Vitro Diagnostic Device Evaluation and Safety (OIVD), with divisions like the Division of Clinical Laboratory Devices and the Division of Immunology and Hematology Devices ^{8485868283122118666568}.
  • Division of Radiological Health and related radiology divisions for imaging devices ^{26273026426626552514953}.
  • Office of Product Evaluation and Quality (OPEQ) and device-focused divisions (e.g., cardiovascular) in more recent letters ^19920291.
• FDA maintains the product code classification database and updates it; Third Party Review Organizations use product codes to conduct reviews and make recommendations but do not assign or finalize product codes ^273274277.

How Product Codes Are Assigned (Process in Practice)

1. Pre-submission identification of candidate code(s)

• Submitters consult FDA’s product code/classification database to identify the likely generic device category and product code aligned to the intended use and technology. Related guidances (e.g., The 510(k) Program) and FDA resources are used to ensure proper device identification; Q-Submission interactions may also be used for feedback ²⁷³.

2. Premarket submission and review

• In a 510(k), the manufacturer presents the device’s intended use, technological characteristics, and comparison to a predicate to demonstrate substantial equivalence. FDA reviews the submission and determines the device’s classification regulation and risk class, then confirms/assigns the corresponding product code. This assignment is recorded in the FDA decision letter and the public databases ^{8485828683273274}.

3. Code maintenance and public listing

• FDA maintains and periodically updates the product code database to reflect classification decisions, device eligibility, and any updates necessary for regulatory clarity ²⁷³²⁷⁴.

Note: While the documents consistently show product code assignment integrated into 510(k) review and device classification, they do not provide a separate, stand‑alone step-by-step procedure unique to product code assignment. Instead, product code designation follows from the classification regulation determined during review under 21 CFR ^{8485828683285}.

Criteria FDA Uses to Determine/Assign Product Codes

Across device types, the analyzed records show the following factors drive product code determination:

• Intended use and indications for use: central to identifying the generic device category and comparator devices ^{8485828683273274}.
• Technological characteristics/device type: software vs. hardware, imaging vs. IVD, material composition, etc. ^{8482838586134135136}.
• Regulatory classification (Class I, II, III) and applicable classification regulation in 21 CFR: codes are tied to specific regulations and panels ²⁸⁵; class designation often narrows the code ^217218219216.
• Substantial equivalence to predicate devices (in 510(k)): matching intended use and technology helps confirm the product code ^8485828683.
• Additional considerations reflected in review programs: device complexity, need for multi-disciplinary expertise, implant status or life-support role, and safety signals (these factors influence eligibility and review pathway decisions and align with how codes reflect category and risk) ²⁷⁶²⁷⁴.

In short, intended use + technology + risk class + classification regulation together determine the product code.

Concrete Examples from Multiple Device Areas

• In vitro diagnostics (IVD) – controls and calibrators

  • Hematology quality control mixtures under 21 CFR 864.8625 have codes like JPK; FDA assigned JPK based on intended use and device class during 510(k) review ^{217218219216122118119117121666568}.
  • Chemistry calibrators under 21 CFR 862.1150 carry JIX; FDA (OIVD/CDRH) assigned JIX for multi‑analyte calibrators after reviewing intended use and classification ^{244245247246249}.
  • Drug-specific calibrators under 21 CFR 862.3200 may carry DLJ; this reflected intended use for cyclosporine assays and Class II risk ⁴⁵⁶.
  • Quality control materials under 21 CFR 862.1660 (e.g., JJX) were assigned based on intended use as specified analyte controls and classification ^{2021222324173170174}.

• Radiology and imaging software/hardware

  • Picture Archiving and Communications Systems under 21 CFR 892.2050 commonly carry LLZ; FDA divisions in radiology assigned LLZ based on intended use and technology as image processing/storage systems ^{123127190187191949598264261263265262}.
  • Magnetic resonance diagnostic devices under 21 CFR 892.1000 were assigned MR-related codes such as LNH, LNI, MOS based on intended use and technology; Division of Radiological Health handled the classification and code assignment ^131128129130.
  • Medical image analyzer software under 21 CFR 892.2070 used MYN, reflecting intended use of automated image analysis and Class II risk ^{134135136137138139}.

• General hospital/urology

  • Urethral catheters under 21 CFR 876.5130 (Class II) received EZD; the code follows from the classification regulation and intended use ^33313235.

• General hospital pumps

  • Elastomeric infusion pumps under 21 CFR 880.5725 received MEB; assignment reflected intended use, technology, and Class II risk during 510(k) review ^7781788079.

These examples show the consistent linkage between classification regulation, device description/technology, and product code assignment as documented in FDA clearance letters.

Role of FDA’s Product Code Database and Guidance

• FDA maintains a publicly accessible classification and product code database used by submitters to identify candidate categories and by reviewers to ensure consistent classification. The database is updated to reflect device eligibility and classification status ²⁷³²⁷⁴.
• Third Party Review Organizations (3P510k ROs) use product codes to scope their reviews and identify comparable devices, but they do not assign codes; FDA retains final responsibility for product code and classification decisions ^277275273274.
• Related guidances and resources commonly referenced during submissions include The 510(k) Program guidance, applicable device-specific guidances, and Title 21 CFR Parts covering classification, registration/listing, labeling, MDR, and quality systems ²⁷³²⁸⁵.

What the Assignment Means and How It’s Used

• Once assigned, the product code anchors the device to a specific classification regulation, risk class, and oversight controls (e.g., general and special controls). It is used for registration and listing (21 CFR Part 807), labeling considerations (21 CFR Part 801), MDR (21 CFR Part 803), and quality systems applicability (21 CFR Part 820) ^{8485828683285}.
• Practically, codes help manufacturers and reviewers find similar devices and relevant predicates, and they influence eligibility for specific review programs (e.g., third party review), consistent with risk and complexity considerations documented in FDA policies ^273274276.

Key Takeaways

• Responsibility: FDA’s CDRH assigns and maintains medical device product codes; divisions vary by device area (e.g., radiology, IVD, cardiovascular). Third party reviewers do not assign codes ^{848582868326426626552514953199202277274}.
• Process: Product code assignment occurs within the 510(k) (or other premarket) review as FDA determines the correct classification regulation and risk class; the code corresponds to that regulation and reflects intended use and technology ^{8485828683273285}.
• Criteria: Intended use, technological characteristics, risk class, and substantial equivalence to predicates drive classification and therefore product code assignment; additional factors (e.g., complexity, implant/life-support status) inform review pathways and align with code selection ^273274276.

If you are determining a code for a new submission, start with the FDA product code/classification database and relevant guidances to identify the most appropriate category and regulation, and be prepared for FDA to confirm or adjust the code during review based on your device’s intended use and technology ²⁷³²⁸⁵.