Pre-production brief
- Role
- Founder, operator, or first regulatory hire trying to understand U.S. classification clues before paying for review
- Scenario
- The team is preparing a U.S. market-entry discussion and internal stakeholders are using product code, class, and pathway as if they were interchangeable.
- Concrete problem
- They do not know what each FDA term actually does, which source answers which question, and when the issue should be escalated to qualified review or a formal 513(g) request.
- Available inputs
- Product description, intended-use draft, claim language, existing similar-device notes, and any internal assumption about likely class or submission type.
- Useful output
- A plain-language comparison, source-backed question list, and consultant handoff note that separates intended use, classification clues, and formal determination options.
- TrueMedDevice role
- Translate official FDA public guidance into a reusable comparison pack without making the classification or pathway determination.
The terms are related, but they do different work
| Term | What it means | What question it helps answer |
|---|---|---|
| Intended use / indications for use | The starting description of what the product does and for whom. | Does this product even look like a device, and which existing classification clues might fit? |
| Regulation number | The Title 21 Code of Federal Regulations section that describes the classified device type. | What does FDA say this generic device type is, and what class is it in? |
| Device class | Class I, II, or III risk category tied to increasing regulatory control. | What level of control and broad submission framework is usually involved? |
| Product code | The classification code used to identify the generic category in the FDA database and listing workflows. | Which generic category am I comparing against, and what related records should I review? |
| Submission clue | The likely premarket path or exemption signal connected to the classification. | Does this look exempt, 510(k), De Novo, PMA, or still uncertain pending qualified review? |
This comparison is a handoff tool, not a formal determination. Its job is to make the next review conversation precise.
Workflow: how to turn the confusion into a usable consultant brief
- 1. Start with intended use and indications for use. FDA says this is part of determining whether the product meets the device definition. Do not begin with "we are probably Class II."
- 2. Search the Product Classification Database broadly. FDA explicitly recommends multiple keyword searches. Capture candidate product codes and note which entries best match the intended use.
- 3. Open the linked regulation number. The regulation number and the CFR section tell you how FDA describes the generic device type and what class it is in.
- 4. Separate class from submission clue. Some Class I and certain Class II devices are exempt from 510(k). Others are not. So "Class II" does not automatically mean the whole strategy is already decided.
- 5. Add similar-device evidence. FDA's device-determination page points users to legally marketed similar devices and public authorization letters as classification aids. Bring those examples into the handoff pack.
- 6. Escalate uncertainty deliberately. If public-source clues and qualified review still leave material uncertainty, note whether a 513(g) request should be discussed as the formal escalation path.
Workload and cost framing
The expensive mistake here is not just the FDA fee. It is using paid review time to untangle vocabulary that should have been sorted before the call.
FDA's classification page says there is a user fee for a 513(g) request, and the user-fee page treats 513(g) as a fee-bearing submission type with a cover sheet. That makes 513(g) a real escalation decision, not a casual fallback. Teams should first exhaust the public-source classification clues and document the remaining uncertainty clearly.
Source ledger
- FDA says the first step is to determine how the FDA has classified your device and that devices fall into Class I, II, or III based on risk, with different regulatory controls and submission types.Official source
- FDA says you should define intended use and indications for use before determining whether a product meets the device definition, and then determine whether an appropriate product classification exists.Official source
- FDA's Product Classification Database contains device names and associated product codes, and the product code identifies the generic category of a device for FDA.Official source
- FDA's classification page explains that once you find the classification regulation, the CFR section describes the device and states its class, and that the three-letter product code in the database is also used on the Medical Device Listing form.Official source
- FDA says some Class I and certain Class II devices are exempt from 510(k), but teams still need the correct classification to understand the applicable controls and exemption limits.Official source
- FDA says that if you would like a formal device determination or classification from FDA, you should consider submitting a 513(g) request, and that there is a user fee for a 513(g) request.Official source
- FDA's product-code guidance says the classification product code helps reviewers determine what information to verify for regulatory requirements and notes that the import-entry code used by ORA is formatted differently from the three-letter classification code used by CDRH.Official source
- FDA's user-fee page lists 513(g) requests as a fee-bearing submission type that requires a Medical Device User Fee Cover Sheet.Official source
FAQ
Is a product code the same thing as device class?
No. FDA's public classification materials separate the generic device type, the regulation number in Title 21 Code of Federal Regulations, the device class, and the product code used in classification and listing workflows. They are related clues, but they are not interchangeable labels.
If I find a product code in the database, does that decide my pathway?
No. The product classification can indicate the generic category and often points to the likely submission type or exemption, but intended use, design, exemption limits, and similar-device evidence still matter. A consultant or qualified RA/QA reviewer still needs to judge whether the classification clue really fits your product.
When should a team consider a 513(g) request?
FDA's classification page says that if you want a formal device determination or classification from FDA, you should consider a 513(g) request. That is the escalation path when public-source clues and qualified review still leave material uncertainty.
Does TrueMedDevice determine FDA classification or pathway?
No. TrueMedDevice does not determine FDA classification, product code, regulation number, 510(k) applicability, De Novo fit, PMA need, predicate suitability, substantial equivalence, compliance status, safety, effectiveness, clearance outcome, or legal obligations. We organize source-backed evidence so qualified RA/QA professionals or consultants can review and decide.
Boundary statement
This is not regulatory, legal, or compliance advice. TrueMedDevice does not determine FDA classification, submission pathway, predicate status, substantial equivalence, compliance, safety, or effectiveness. We prepare a source-backed evidence pack from public FDA sources so qualified RA/QA professionals or regulatory consultants can review and decide.