eduKateSG · Why Science?
Read a medical-device clearance as a documented comparison
Use the FDA 510(k) database through K numbers, predicates, intended use, product codes, performance evidence, decision dates and public summaries.
Many medical devices reach the US market through the 510(k) premarket-notification pathway. The public FDA database lets learners search by submission number, applicant, device name, product code, decision date and other fields.
The core question is substantial equivalence. FDA compares the new device with a legally marketed predicate, considering intended use, technological characteristics and evidence for any differences. This does not mean the devices are identical.
Did you know? A 510(k) record is described as cleared, while Premarket Approval is a different pathway for certain Class III devices. Precise verbs help readers understand which scientific and regulatory review occurred.
This guide supports science and regulatory literacy. It does not recommend a medical device or interpret suitability for an individual patient.
Chapter index
Chapters 1–9: submission identity, classification and use
- 1. The K number identifies the submission
- 2. 510(k) is a premarket notification pathway
- 3. Substantial equivalence is a defined comparison
- 4. The predicate is a legally marketed device
- 5. Device names need classification context
- 6. Intended use and indications need exact reading
- 7. Technological differences require analysis
- 8. Performance tests answer bounded questions
- 9. Clinical data may sometimes be needed
Chapters 10–17: comparison, decision documents and limits
- 10. The decision date marks FDA action
- 11. Decision codes need their wording
- 12. 510(k) summaries explain the basis
- 13. Traditional, Special and Abbreviated routes differ
- 14. Third-party review is a separate field
- 15. Predicate chains need caution
- 16. Clearance does not settle every safety question
- 17. 510(k) literacy supports engineering careers
A device clearance record becomes useful when submission number, device identity, predicate and decision date stay connected. FDA assigns a 510(k) number that anchors the submission record and decision. The device name or applicant alone can be ambiguous. This helps students read regulatory reasoning without calling clearance an approval under the PMA pathway.
Try this
Evidence question: Which K number supports the statement? 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 it before following predicates. 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 k number identifies the submission, its identifier or version context, and one limit that must remain visible.
CHAPTER 2 OF 17 · Identify the submission
2. 510(k) is a premarket notification pathway
The 510(k) pathway centres on an FDA determination of substantial equivalence to a legally marketed predicate. A 510(k) submission demonstrates that a device is substantially equivalent to a legally marketed predicate not subject to PMA. It also separates an intended-use comparison from a claim that two devices are identical.
Try this
Evidence question: Which regulatory pathway applies? 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 clearance language for the 510(k) decision. 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 510(k) is a premarket notification pathway, its identifier or version context, and one limit that must remain visible.
CHAPTER 3 OF 17 · Identify the submission
3. Substantial equivalence is a defined comparison
Product codes and regulation numbers provide classification context rather than proof that all devices in a group are interchangeable. FDA considers intended use and technological characteristics, including whether differences raise new questions and whether performance data support equivalence. The K number and source documents make the route repeatable.
Try this
Evidence question: Which comparison step supports the decision? 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: Read the decision summary rather than inferring from the product name. 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 substantial equivalence is a defined comparison, its identifier or version context, and one limit that must remain visible.
CHAPTER 4 OF 17 · Identify the submission
4. The predicate is a legally marketed device
A public summary can explain comparison and performance evidence while the exact decision remains tied to one submission. A predicate provides the comparison baseline. Its role does not mean the new device is identical or that every use is shared. Clinical use questions still belong with qualified healthcare professionals.
Try this
Evidence question: Which predicate number and intended use are 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: Create a subject-predicate table. 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 predicate is a legally marketed device, its identifier or version context, and one limit that must remain visible.
CHAPTER 5 OF 17 · Understand the predicate
5. Device names need classification context
A device clearance record becomes useful when submission number, device identity, predicate and decision date stay connected. Trade and common names can vary, while product codes, regulation numbers and panels provide structured classification. This helps students read regulatory reasoning without calling clearance an approval under the PMA pathway.
Try this
Evidence question: Which product code applies? 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 code and regulation description. 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 names need classification context, its identifier or version context, and one limit that must remain visible.
CHAPTER 6 OF 17 · Understand the predicate
6. Intended use and indications need exact reading
The 510(k) pathway centres on an FDA determination of substantial equivalence to a legally marketed predicate. The comparison depends strongly on intended use and indications for use. Similar technology with a different use can require additional evidence or another pathway. It also separates an intended-use comparison from a claim that two devices are identical.
Try this
Evidence question: Are the intended uses the same? 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: Quote the official use statement. 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 intended use and indications need exact reading, its identifier or version context, and one limit that must remain visible.
CHAPTER 7 OF 17 · Understand the predicate
7. Technological differences require analysis
Product codes and regulation numbers provide classification context rather than proof that all devices in a group are interchangeable. Different materials, energy sources, software or design features may be acceptable if they do not raise different questions and supporting data establish equivalence. The K number and source documents make the route repeatable.
Try this
Evidence question: Which difference required performance evidence? 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: Link each difference to its test. 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 technological differences require analysis, its identifier or version context, and one limit that must remain visible.
CHAPTER 8 OF 17 · Understand the predicate
8. Performance tests answer bounded questions
A public summary can explain comparison and performance evidence while the exact decision remains tied to one submission. Bench, biocompatibility, electrical safety, software, sterilisation or other tests may support the decision. Not every submission requires the same evidence. Clinical use questions still belong with qualified healthcare professionals.
Try this
Evidence question: Which standard and endpoint were used? 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 test type, acceptance criterion and result. 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 performance tests answer bounded questions, its identifier or version context, and one limit that must remain visible.
CHAPTER 9 OF 17 · Inspect performance evidence
9. Clinical data may sometimes be needed
A device clearance record becomes useful when submission number, device identity, predicate and decision date stay connected. FDA guidance explains that clinical data can be necessary in some 510(k) reviews, depending on intended use and technological questions. This helps students read regulatory reasoning without calling clearance an approval under the PMA pathway.
Try this
Evidence question: Was clinical evidence part of this record? 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: State its presence or absence without generalising. 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 clinical data may sometimes be needed, its identifier or version context, and one limit that must remain visible.
CHAPTER 10 OF 17 · Inspect performance evidence
10. The decision date marks FDA action
The 510(k) pathway centres on an FDA determination of substantial equivalence to a legally marketed predicate. The decision date records when FDA made the substantial-equivalence determination. It is not the manufacturing, market-launch or study date. It also separates an intended-use comparison from a claim that two devices are identical.
Try this
Evidence question: Which event does the date identify? 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 the decision label. 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 the decision date marks fda action, its identifier or version context, and one limit that must remain visible.
CHAPTER 11 OF 17 · Inspect performance evidence
11. Decision codes need their wording
Product codes and regulation numbers provide classification context rather than proof that all devices in a group are interchangeable. Database codes such as substantially equivalent or not substantially equivalent summarise the decision. They should be expanded accurately. The K number and source documents make the route repeatable.
Try this
Evidence question: What full decision wording 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: Do not translate a code into stronger language. 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 decision codes need their wording, its identifier or version context, and one limit that must remain visible.
CHAPTER 12 OF 17 · Inspect performance evidence
12. 510(k) summaries explain the basis
A public summary can explain comparison and performance evidence while the exact decision remains tied to one submission. Public summaries can describe the device, predicate comparison and performance evidence. Detail varies by period and submission. Clinical use questions still belong with qualified healthcare professionals.
Try this
Evidence question: Which public document supports the claim? 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 summary file and section. 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 510(k) summaries explain the basis, its identifier or version context, and one limit that must remain visible.
CHAPTER 13 OF 17 · Connect premarket and postmarket records
13. Traditional, Special and Abbreviated routes differ
A device clearance record becomes useful when submission number, device identity, predicate and decision date stay connected. FDA has used different 510(k) types with specific eligibility and content expectations. The database type field adds context. This helps students read regulatory reasoning without calling clearance an approval under the PMA pathway.
Try this
Evidence question: Which submission type is recorded? 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: Avoid assuming identical review content. 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 traditional, special and abbreviated routes differ, its identifier or version context, and one limit that must remain visible.
CHAPTER 14 OF 17 · Connect premarket and postmarket records
14. Third-party review is a separate field
The 510(k) pathway centres on an FDA determination of substantial equivalence to a legally marketed predicate. Certain eligible submissions may be reviewed through an accredited third party before FDA’s decision. The FDA decision remains the regulatory outcome. It also separates an intended-use comparison from a claim that two devices are identical.
Try this
Evidence question: Was third-party review used? 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 reviewer route and decision separate. 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 third-party review is a separate field, its identifier or version context, and one limit that must remain visible.
CHAPTER 15 OF 17 · Connect premarket and postmarket records
15. Predicate chains need caution
Product codes and regulation numbers provide classification context rather than proof that all devices in a group are interchangeable. Following predicates can reveal a lineage of clearances, but each decision compares defined devices and evidence at its time. A long chain does not prove current clinical equivalence among all members. The K number and source documents make the route repeatable.
Try this
Evidence question: Which direct comparison matters? 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: Stop at each decision record. 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 predicate chains need caution, its identifier or version context, and one limit that must remain visible.
CHAPTER 16 OF 17 · Connect premarket and postmarket records
16. Clearance does not settle every safety question
A public summary can explain comparison and performance evidence while the exact decision remains tied to one submission. Postmarket reports, recalls, safety communications and updated labeling provide later evidence. A premarket record is one layer. Clinical use questions still belong with qualified healthcare professionals.
Try this
Evidence question: Which postmarket source should be checked? 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 K number and UDI to later records. 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 clearance does not settle every safety question, its identifier or version context, and one limit that must remain visible.
CHAPTER 17 OF 17 · Connect premarket and postmarket records
17. 510(k) literacy supports engineering careers
A device clearance record becomes useful when submission number, device identity, predicate and decision date stay connected. Biomedical engineers, regulatory scientists, clinicians and information specialists use clearance documents for distinct questions. This helps students read regulatory reasoning without calling clearance an approval under the PMA pathway.
Try this
Evidence question: Which conclusion belongs to engineering and which to regulation? 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: Prepare a K-number evidence 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 510(k) literacy supports engineering careers, its identifier or version context, and one limit that must remain visible.
Contents · Previous chapter · Continue at the Science Learning Hub
A clearance claim is strongest when the K number, predicate and decision summary stay together
The FDA 510(k) record turns a broad device name into a traceable comparison and decision. Its public summary can show how intended use, technology and performance evidence were evaluated.
Save the K number, device and applicant, product code, regulation number, submission type, intended use, predicate number, technological differences, tests, decision wording and date, summary file and access date.
| Reading object | What it can support | Question to keep visible |
|---|---|---|
| K number | Identity of one 510(k) submission | Which decision and summary connect? |
| Predicate device | Legally marketed comparison device | Which intended use and technology apply? |
| Product code | FDA device classification category | Which regulation and panel? |
| Decision summary | Public explanation of the comparison | Which evidence supported clearance? |
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 510(k) database — accessed 25 October 2026.
- Premarket Notification 510(k) — accessed 25 October 2026.
- Content of a 510(k) — accessed 25 October 2026.
- 510(k) submission process — accessed 25 October 2026.
- openFDA 510(k) API overview — accessed 25 October 2026.