eduKateSG · Why Science?
Turn a device name into a regulatory classification map
Use FDA product-classification records through generic device types, three-letter product codes, regulations, panels, classes, exemptions, submission routes, standards and guidance.
Medical-device names can be surprisingly slippery. A familiar trade name may cover several models, while FDA classification begins with a generic device type and a three-letter product code connected to a regulation, panel and class.
The Product Classification Database gives students a structured route into regulatory context. It can show premarket submission type, exemptions, recognised standards, guidance and review organisation alongside the category.
Did you know? The three-letter CDRH product code is different from the longer FDA product code used for import line items. Both help identify products, but they belong to different coding systems and should be labeled clearly.
This guide explains classification records for science learning. It does not determine the status of a particular marketed device without its exact submission, UDI and current FDA records.
Chapter index
Chapters 1–9: product code, regulation, panel and class
- 1. The generic device type is the starting object
- 2. A three-letter product code identifies the category
- 3. The regulation number connects to federal rules
- 4. The medical specialty panel organises review context
- 5. Device class reflects regulatory controls
- 6. Class I commonly relies on general controls
- 7. Class II commonly adds special controls
- 8. Class III can require premarket approval
- 9. Premarket submission type is a separate field
Chapters 10–17: submission routes, exemptions, flags and evidence links
- 10. Exemption fields require exact interpretation
- 11. GMP exemption is another distinct field
- 12. Implant and life-support flags provide context
- 13. Recognised standards are linked evidence tools
- 14. Guidance documents add current expectations
- 15. Unclassified or proposed entries need caution
- 16. CDRH codes differ from import product codes
- 17. Classification literacy supports device engineering
CHAPTER 1 OF 17 · Find the generic type
1. The generic device type is the starting object
A product code becomes useful when it stays attached to the device name, regulation, panel and class. FDA classification records describe a generic type of device rather than every commercial model using a similar name. This gives students a map of regulation without turning the class number into a complete risk score.
Try this
Evidence question: Which generic device name is actually classified? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Write the generic name above any trade-name examples. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Keep the identifier, retrieval date and source page in the note so the route can be repeated.
Evidence checkpoint
Record the evidence object for the generic device type is the starting object, its identifier or version context, and one limit that must remain visible.
CHAPTER 2 OF 17 · Find the generic type
2. A three-letter product code identifies the category
FDA groups medical devices into regulatory categories that help determine controls and premarket expectations. CDRH assigns a three-letter product code to a generic device type for classification and information management. It also separates CDRH three-letter product codes from FDA import product codes.
Try this
Evidence question: Which exact code supports the lookup? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Preserve all three letters and the linked record. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. If a field is missing, write “not shown” and follow the official documentation rather than inventing a value.
Evidence checkpoint
Record the evidence object for a three-letter product code identifies the category, its identifier or version context, and one limit that must remain visible.
CHAPTER 3 OF 17 · Find the generic type
3. The regulation number connects to federal rules
The public classification database links a generic device type with review and regulatory information. Many records link the device type to a section in 21 CFR Parts 862 through 892 containing the classification regulation and description. The regulation and database access date preserve context.
Try this
Evidence question: Which regulation section is cited? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Follow it and compare its wording with the database. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Before comparing two records, check that their object types, methods, versions and units really align.
Evidence checkpoint
Record the evidence object for the regulation number connects to federal rules, its identifier or version context, and one limit that must remain visible.
CHAPTER 4 OF 17 · Find the generic type
4. The medical specialty panel organises review context
One trade name can cover variants, so the generic type and intended use need careful reading. Classification records associate device types with panels or medical specialties such as cardiovascular, radiology or clinical chemistry. Specific devices still require their own clearance, approval, exemption or other record.
Try this
Evidence question: Which panel owns the category? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Use the panel as context, not a clinical endorsement. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Finish by naming one supported statement and one stronger statement that still needs another evidence layer.
Evidence checkpoint
Record the evidence object for the medical specialty panel organises review context, its identifier or version context, and one limit that must remain visible.
CHAPTER 5 OF 17 · Read class and controls
5. Device class reflects regulatory controls
A product code becomes useful when it stays attached to the device name, regulation, panel and class. Class I, II and III are regulatory categories related to the controls needed to provide reasonable assurance of safety and effectiveness. This gives students a map of regulation without turning the class number into a complete risk score.
Try this
Evidence question: Which class and controls apply to this generic type? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Record the class without converting it into a numerical risk score. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Keep the identifier, retrieval date and source page in the note so the route can be repeated.
Evidence checkpoint
Record the evidence object for device class reflects regulatory controls, its identifier or version context, and one limit that must remain visible.
CHAPTER 6 OF 17 · Read class and controls
6. Class I commonly relies on general controls
FDA groups medical devices into regulatory categories that help determine controls and premarket expectations. Many Class I devices are subject to general controls, though exemptions and special circumstances require checking the actual record and regulation. It also separates CDRH three-letter product codes from FDA import product codes.
Try this
Evidence question: Is this device exempt from premarket notification? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Verify the exemption field instead of assuming. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. If a field is missing, write “not shown” and follow the official documentation rather than inventing a value.
Evidence checkpoint
Record the evidence object for class i commonly relies on general controls, its identifier or version context, and one limit that must remain visible.
The public classification database links a generic device type with review and regulatory information. Class II devices generally require general and special controls; many also use the 510(k) pathway unless exempt or otherwise specified. The regulation and database access date preserve context.
Try this
Evidence question: Which special controls or guidance are linked? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Follow the record’s guidance and submission fields. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Before comparing two records, check that their object types, methods, versions and units really align.
Evidence checkpoint
Record the evidence object for class ii commonly adds special controls, its identifier or version context, and one limit that must remain visible.
CHAPTER 8 OF 17 · Read class and controls
8. Class III can require premarket approval
One trade name can cover variants, so the generic type and intended use need careful reading. Class III devices generally require PMA unless another legal status or transitional situation applies. The specific classification record controls the answer. Specific devices still require their own clearance, approval, exemption or other record.
Try this
Evidence question: What submission type is shown? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Connect the code to the PMA or applicable pathway. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Finish by naming one supported statement and one stronger statement that still needs another evidence layer.
Evidence checkpoint
Record the evidence object for class iii can require premarket approval, its identifier or version context, and one limit that must remain visible.
CHAPTER 9 OF 17 · Check exemptions and standards
9. Premarket submission type is a separate field
A product code becomes useful when it stays attached to the device name, regulation, panel and class. The database may identify 510(k), PMA, exemption or another review route. Device class alone does not supply every submission detail. This gives students a map of regulation without turning the class number into a complete risk score.
Try this
Evidence question: Which route does the record name? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Keep class and submission route in separate columns. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Keep the identifier, retrieval date and source page in the note so the route can be repeated.
Evidence checkpoint
Record the evidence object for premarket submission type is a separate field, its identifier or version context, and one limit that must remain visible.
CHAPTER 10 OF 17 · Check exemptions and standards
10. Exemption fields require exact interpretation
FDA groups medical devices into regulatory categories that help determine controls and premarket expectations. A 510(k) exemption can be limited by regulation and device characteristics; exemption from one requirement does not mean exemption from all FDA controls. It also separates CDRH three-letter product codes from FDA import product codes.
Try this
Evidence question: What is exempt and under which conditions? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Cite the precise field and regulation. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. If a field is missing, write “not shown” and follow the official documentation rather than inventing a value.
Evidence checkpoint
Record the evidence object for exemption fields require exact interpretation, its identifier or version context, and one limit that must remain visible.
CHAPTER 11 OF 17 · Check exemptions and standards
11. GMP exemption is another distinct field
The public classification database links a generic device type with review and regulatory information. The database can state whether a generic device type is exempt from current good manufacturing practice requirements, subject to applicable limits. The regulation and database access date preserve context.
Try this
Evidence question: Is GMP exemption shown independently of 510(k) exemption? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Do not combine the two fields. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Before comparing two records, check that their object types, methods, versions and units really align.
Evidence checkpoint
Record the evidence object for gmp exemption is another distinct field, its identifier or version context, and one limit that must remain visible.
CHAPTER 12 OF 17 · Check exemptions and standards
12. Implant and life-support flags provide context
One trade name can cover variants, so the generic type and intended use need careful reading. Records may indicate whether a category is implanted or life-sustaining or supporting. These flags have regulatory meanings and need the source definition. Specific devices still require their own clearance, approval, exemption or other record.
Try this
Evidence question: Which flag is present? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Use the recorded value without inferring patient suitability. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Finish by naming one supported statement and one stronger statement that still needs another evidence layer.
Evidence checkpoint
Record the evidence object for implant and life-support flags provide context, its identifier or version context, and one limit that must remain visible.
CHAPTER 13 OF 17 · Connect the evidence pathway
13. Recognised standards are linked evidence tools
A product code becomes useful when it stays attached to the device name, regulation, panel and class. A classification page can link FDA-recognised consensus standards relevant to a device category. A listed standard does not prove that a particular device conforms. This gives students a map of regulation without turning the class number into a complete risk score.
Try this
Evidence question: Which standard and recognition version apply? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Check the declaration or submission for actual conformity. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Keep the identifier, retrieval date and source page in the note so the route can be repeated.
Evidence checkpoint
Record the evidence object for recognised standards are linked evidence tools, its identifier or version context, and one limit that must remain visible.
CHAPTER 14 OF 17 · Connect the evidence pathway
14. Guidance documents add current expectations
FDA groups medical devices into regulatory categories that help determine controls and premarket expectations. Linked guidance can explain testing, submission or policy expectations for a device type. Guidance date and scope need checking. It also separates CDRH three-letter product codes from FDA import product codes.
Try this
Evidence question: Which guidance addresses this product code? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Record its title, date and whether it is final. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. If a field is missing, write “not shown” and follow the official documentation rather than inventing a value.
Evidence checkpoint
Record the evidence object for guidance documents add current expectations, its identifier or version context, and one limit that must remain visible.
CHAPTER 15 OF 17 · Connect the evidence pathway
15. Unclassified or proposed entries need caution
The public classification database links a generic device type with review and regulatory information. FDA notes that when the database lacks a regulation number, a listed class may be proposed rather than final. The regulation and database access date preserve context.
Try this
Evidence question: Is a regulation number present? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Flag proposed status explicitly. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Before comparing two records, check that their object types, methods, versions and units really align.
Evidence checkpoint
Record the evidence object for unclassified or proposed entries need caution, its identifier or version context, and one limit that must remain visible.
CHAPTER 16 OF 17 · Connect the evidence pathway
16. CDRH codes differ from import product codes
One trade name can cover variants, so the generic type and intended use need careful reading. The three-letter CDRH classification product code is distinct from the longer FDA import product code used for entry data. Specific devices still require their own clearance, approval, exemption or other record.
Try this
Evidence question: Which coding system does the task require? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Label the code system before copying a value. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Finish by naming one supported statement and one stronger statement that still needs another evidence layer.
Evidence checkpoint
Record the evidence object for cdrh codes differ from import product codes, its identifier or version context, and one limit that must remain visible.
CHAPTER 17 OF 17 · Connect the evidence pathway
17. Classification literacy supports device engineering
A product code becomes useful when it stays attached to the device name, regulation, panel and class. Regulatory scientists and biomedical engineers use classification to plan evidence, submissions and lifecycle obligations. This gives students a map of regulation without turning the class number into a complete risk score.
Try this
Evidence question: Which field changes the evidence plan? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Create a product-code classification receipt. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Keep the identifier, retrieval date and source page in the note so the route can be repeated.
Evidence checkpoint
Record the evidence object for classification literacy supports device engineering, its identifier or version context, and one limit that must remain visible.
Contents · Previous chapter · Continue at the Science Learning Hub
A device category becomes useful when every regulatory field keeps its label
The FDA classification record connects a generic device type to its product code, regulation, panel and controls. That map helps learners find the right premarket and postmarket evidence without treating category data as model-specific proof.
Save the generic name, three-letter product code, regulation number, medical specialty, device class, submission type, exemptions, implant and life-support flags, recognised standards, guidance, review office and access date.
| Reading object | What it can support | Question to keep visible |
|---|---|---|
| Generic device type | The regulated category | Does it match the intended use? |
| Product code | Three-letter CDRH category identifier | Which regulation and panel connect? |
| Device class | Regulatory control category | Which controls and submission route apply? |
| Exemption field | Specific regulatory relief where applicable | What limits or conditions remain? |
Sources and next reading
Substantive resource claims in this article were checked against the primary pages below. A structured record is a route into evidence; it does not by itself prove a scientific conclusion. Recheck the live record, evidence labels and release context before using it in assessed work or research.
For a classroom enquiry, save a short research receipt containing the question, search terms, selected object, exact identifier, version, access date and the evidence boundary you observed. Add the file or page that supports each statement. This small routine turns browsing into accountable science learning and gives a teacher, classmate or future analyst a route they can independently follow.
Before sharing the conclusion, ask another reader to retrace the route without verbal hints. If they reach a different version, file or interpretation, improve the receipt and narrow the claim. Reproducibility begins with this practical check. It teaches careful reading, supports fair collaboration and keeps uncertainty visible while evidence moves from an online service into notes, analysis and a final explanation.
A useful final review separates five questions. What object was found? Which organisation or repository maintains it? What exact evidence was inspected? Which statement does that evidence support? What remains uncertain? Answer each question in one sentence, then connect every answer to a visible field, file or source page. This review catches common mistakes: citing a collection when a file supplied the value, treating the newest release as the analysed release, confusing permission with scientific suitability, or turning a discovery count into a conclusion. It also gives students a calm way to improve work. A missing detail becomes a next research step instead of an invitation to guess. When the route is complete, the final explanation can stay simple because the identifiers, dates, versions, limitations and supporting evidence are already organised underneath it.
Primary sources
- FDA Product Classification Database — accessed 25 October 2026.
- Product Code Classification Database — accessed 25 October 2026.
- Classify Your Medical Device — accessed 25 October 2026.
- Download Product Code Classification Files — accessed 25 October 2026.
- Medical Device Classification Product Codes Guidance — accessed 25 October 2026.