News

Industry Insights

 

Choosing the Right FDA Product Code: Why It Matters for Submission

Strategy and Development

May 21, 2026 | CAHIR Solutions

 

Case Study Example

For an AI-enabled diagnostic radiology tool, multiple product codes may exist for similar imaging modalities, some specific to AI/ML and others legacy. By systematically comparing intended use and technical characteristics against each candidate code and reviewing associated special controls and precedent clearances, the team can select a code that supports their claims without triggering an unnecessary PMA-level burden. (A case scenario with concise approach and solutions included with this publication.)

 

Why FDA Product Code Selection Matters

FDA product codes are three-letter identifiers that tie your device to a specific regulation, risk class, submission type, and set of expectations, so getting the code right early essentially locks in your regulatory and development roadmap.  For medical devices, the FDA product code is not just a database label; it is a shorthand for how your device will be regulated. Each code links to a classification regulation, device class (I–III), submission route (510(k), De Novo, PMA, exemption), and any applicable special controls or guidance. If you identify the wrong code, you risk misaligned testing, the wrong regulatory strategy, and costly rework late in development.

 

What Is an FDA Product Code?

Within CDRH, product codes are generally three-letter identifiers that group devices with similar intended use and technology under a generic type. In the FDA Product Classification Database, each product code record includes the device name, regulation citation (21 CFR 862–892), class, submission type, and often links to relevant guidance or recognized standards.

 

Classification product codes play a central role in how medical devices are evaluated, tracked, and regulated throughout the FDA premarket process.

 

They are used to group devices by technology and intended use within a broader regulation, helping define subcategories that may require different levels of evidence, specific labeling, or unique review considerations. These codes also apply to unclassified and Class III (PMA) devices and can remain the same or change if a device is reclassified.

 

During premarket submission, manufacturers propose a product code based on similar (predicate) devices, but the FDA reviews and may revise this selection to ensure accuracy. The assigned code helps determine which FDA review team and panel will evaluate the submission.

Beyond review, product codes support internal FDA functions such as adverse event monitoring, compliance actions, and device tracking. They are also referenced in guidance documents to clarify which devices the guidance applies to.

As new codes are created or refined, devices may be reassigned, and manufacturers are formally notified of any updates. Overall, classification product codes provide a structured way to organize devices, guide regulatory requirements, and maintain oversight across a product’s lifecycle.

 

Manufacturers can search the public Product Classification Database to find codes that reflect device intended use and technological characteristics, then review associated regulatory requirements. Once a suitable predicate and product code are identified, subsequent submissions typically reference that code and demonstrate substantial equivalence or justify a De Novo or PMA path if no predicate exists.

 

 

Stepwise Approach to Identifying the Correct Product Code

You can frame this as a repeatable process for founders and design teams:

  1. Clarify intended use and indications for use
    • Draft plain-language statements describing what the device does, for whom, and in what setting (diagnosis, monitoring, treatment, mitigation, etc.).

    • Specify key clinical conditions, user type (HCP vs patient), and use environment; these details often distinguish between similar product codes.

    •  

  2. Identify candidate regulations and medical specialty

    • Map the device to the most appropriate medical specialty and associated regulations under 21 CFR Parts 862–892 using high-level intended use.

    • Resources like the Product Classification Database and CDRH Learn modules walk through identifying classification regulations and associated codes.

    •  

  3. Search the FDA Product Classification Database

    • Use the Product Classification Database “Quick” and “Advanced” search functions by keyword, regulation number, or known similar devices.

    • For each candidate code, review device description, regulation citation, class, submission type, and any indications that don’t match your intended use; discard near-misses.

    •  

  4. Work backwards from similar devices

    • If you know a similar device, search its 510(k), PMA, or De Novo record and note the product code and regulation cited.

    • You can also search the Establishment Registration and Device Listing database to see how comparable products are listed and classified.

    •  

  5. Triangulate with CDRH Learn and guidance documents

    • CDRH Learn modules explicitly show how product codes connect to classification and regulatory requirements and outline common methods for determining classification.

    • For shortlisted codes, check associated guidance and special controls to ensure they align with your technology and risk profile.

    •  

  6. Document your rationale and validate

    • Record why the selected product code best reflects intended use, technology, and risk versus alternatives, including citations to database entries and predicates.

    • For borderline or novel technologies, plan early engagement (e.g., Q-Sub) to confirm code and pathway with FDA before locking major development decisions.

 

Development Implications of Getting the Product Code Right

Choosing the right product code early influences almost every downstream decision:

  • Regulatory pathway and timelines

    • The product code defines whether your device is Class I, II, or III and points to the expected submission type (exempt, 510(k), De Novo, PMA).

    • This drives your overall development timeline, resource planning, and go-to-market strategy.

    •  

  • Evidence strategy, testing, and validations

    • Each product code ties to specific general and special controls, including expectations for bench, animal, human factors, and clinical data.

    • Misclassification can lead to either under-testing (and rejection) or over-testing (and wasted budget).

    •  

  • Standards, guidance, and design inputs

    • Product codes often link to recognized consensus standards and guidance documents that can be leveraged to de-risk design and streamline review.

    • Incorporating these requirements into design inputs and verification plans early reduces change orders and late-stage redesign.

    •  

  • Labeling, indications, and marketing claims

    • The code anchors how FDA interprets your indications for use and acceptable claims relative to predicates in that generic type.

    • A misaligned code can constrain your label or force you into a different, more burdensome pathway if your claims exceed the established category.

    •  

  • Lifecycle management and portfolio strategy

    • Consistent use of product codes allows you to plan families of devices and incremental changes under a coherent regulatory framework.

    • It also simplifies post market surveillance, MDR trend analysis, and alignment of future submissions with prior decisions.

 

 

 

 

Client Situation

An early‑stage startup developing an AI‑enabled diagnostic radiology tool is uncertain which FDA product code to use. Multiple codes appear relevant: several legacy radiology codes and newer AI/ML‑specific codes that seem to fit parts of their intended use, but not perfectly. The team recognizes that the product code will drive their regulatory pathway, testing expectations, and overall development strategy, but they lack the expertise and bandwidth to confidently make this decision.

Cahir Solutions Proposed Engagement

Cahir Solutions is engaged to lead a focused product code and regulatory pathway assessment. We start by facilitating a structured working session with the client’s clinical, technical, and product leaders to refine the device’s intended use, indications for use, and key technical characteristics, including how the AI algorithm influences diagnostic decision‑making and radiologist workflow. Using this refined profile, we identify and curate a shortlist of potential product codes from FDA databases and prior AI radiology clearances, highlighting the nuances between AI‑specific and legacy codes.

We then perform a detailed side‑by‑side analysis of each candidate code, comparing device descriptions, regulation citations, risk class, and typical submission types. For each option, Cahir Solutions maps out the associated special controls, relevant guidance documents, and typical evidence expectations (bench, clinical, human factors, and algorithm performance). This analysis is translated into practical implications for the client: impact on timelines, data requirements, labeling flexibility, and long‑term product roadmap.

Based on the analysis, Cahir Solutions recommends the product code that best aligns with the client’s intended use and AI technology while preserving a feasible Class II pathway. We prepare a concise decision memo documenting the rationale for the selected code, why alternative codes were rejected, and how this choice supports the client’s desired claims without escalating them into PMA territory. We also outline a high‑level verification, validation, and clinical strategy tied directly to the chosen product code and its special controls.

Where appropriate, we propose and support an early interaction with FDA to confirm alignment on product code and regulatory pathway. Cahir Solutions provides briefing materials and talking points for that interaction and updates the regulatory strategy based on FDA feedback. With the product code decision locked in and fully justified, the client gains a clear regulatory roadmap and can confidently integrate these requirements into design controls, funding plans, and commercialization strategy.

 

 

Cahir Solutions helps medical device companies choose the right FDA early-interaction pathway. When the question is classification or regulatory status, a 513(g) is often the right fit. When the goal is to discuss novel technology, borderline issues, or overall submission strategy, a Pre-Sub is usually more effective. Cahir Solutions guides teams to the right option and helps prepare a focused, strategic request that supports the next stage of development.