The HemoCue Glucose 201 RT system is used for quantitative determination of glucose in whole blood supplementing the clinical evidence in the diagnosis and treatment of patients with diabetes. The HemoCue Glucose 201 RT system is for In Vitro Diagnostic use only. The HemoCue Glucose 201 RT Analyzer is only to be used with HemoCue Glucose 201 RT Microcuvettes. For professional use only.
Device Story
System comprises portable photometer analyzer and single-use microcuvettes; microcuvette acts as both pipette and reaction vessel. Capillary action draws ~4 µL whole blood sample into cuvette containing reagents. Chemical reaction involves hemolysis and modified glucose dehydrogenase method: mutarotase converts B-D-glucose; glucose dehydrogenase catalyzes oxidation to form NADH; diaphorase and tetrazolium salt (MTT) produce colored formazan. Analyzer measures transmittance; calculates absorbance and glucose concentration. Used in point-of-care settings by healthcare professionals. Factory-calibrated; no external QC required; internal self-test included. Provides rapid quantitative glucose results to support clinical decision-making in diabetes management.
Clinical Evidence
Performance demonstrated through in-house, clinical laboratory, and point-of-care center studies. Studies confirmed that intended users can operate the system and obtain expected results comparable to current clinical laboratory and point-of-care practices.
Technological Characteristics
System consists of a photometer analyzer and single-use plastic microcuvettes. Measurement principle: photometric transmittance/absorbance of colored formazan via modified glucose dehydrogenase reaction. Calibration: traceable to ID GC-MS method; factory-calibrated. Operating temperature: 15°C - 30°C (59°F - 86°F).
Indications for Use
Indicated for quantitative glucose determination in whole blood to aid in diagnosis and treatment of patients with diabetes. For professional, in vitro diagnostic, prescription use in point-of-care settings.
Regulatory Classification
Identification
A glucose test system is a device intended to measure glucose quantitatively in blood and other body fluids. Glucose measurements are used in the diagnosis and treatment of carbohydrate metabolism disorders including diabetes mellitus, neonatal hypoglycemia, and idiopathic hypoglycemia, and of pancreatic islet cell carcinoma.
Special Controls
*Classification.* Class II (special controls). The device, when it is solely intended for use as a drink to test glucose tolerance, is exempt from the premarket notification procedures in subpart E of part 807 of this chapter subject to the limitations in § 862.9.
{0}
1
510(k) SUBSTANTIAL EQUIVALENCE DETERMINATION
DECISION SUMMARY
ASSAY AND INSTRUMENT COMBINATION TEMPLATE
A. 510(k) Number:
k060765
B. Purpose for Submission:
New 510(k)
C. Measurand:
Glucose in blood
D. Type of Test:
Quantitative, instrument read, whole blood glucose test
E. Applicant:
HemoCue AB
F. Proprietary and Established Names:
HemoCue Glucose 201 RT System
G. Regulatory Information:
1. Regulation section:
862.1345, Glucose Dehydrogenase
2. Classification:
Class II
3. Product code:
LFR
4. Panel:
75 (Chemistry)
{1}
H. Intended Use:
1. Intended use(s):
See indications for use.
2. Indication(s) for use:
The HemoCue Glucose 201 RT system is used for quantitative determination of glucose in whole blood supplementing the clinical evidence in the diagnosis and treatment of patients with diabetes. The HemoCue Glucose 201 RT system is for In Vitro Diagnostic use only. The HemoCue Glucose 201 RT Analyzer is only to be used with HemoCue Glucose 201 RT Microcuvettes. For professional use only.
3. Special conditions for use statement(s):
The device is for in vitro diagnostic prescription use.
The assay is intended for use in point-of-care settings and the appropriate studies were done. This claim, however, is not included in the Indications for Use statement.
4. Special instrument requirements:
The microcuvettes and HemoCue 201 RT analyzer are not intended for use with other components. They are mutually exclusive.
I. Device Description:
The HemoCue Glucose 201 RT Analyzer is a portable device. The main parts are the cuvette holder (brings the microcuvette in correct measuring position), the optronic unit (a photometer which performs the measurement in the microcuvette) a display, a power adaptor and embedded software.
The single-use Microcuvette contains reagents deposited on its inner walls and serves both as a pipette and as a measuring cuvette. A blood sample of approximately 4 µL is drawn into the cavity by capillary action. The filled microcuvette is inserted into the HemoCue Analyzer. The measurement takes place in the analyzer in which the transmittance is measured and the absorbance and glucose level is calculated. The calibration of the analyzer is traceable to the ID (Isotope Dilution) GC-MS method. The HemoCue is factory calibrated and needs no further calibration. The reportable range is 12-560 mg/dL.
The instrument may be customized for use with or without plasma conversion of whole blood measurements. Plasma equivalents are determined by multiplying the whole blood reading by a factor of 1.1.
The sponsor indicates the device does not contain human source material.
{2}
J. Substantial Equivalence Information:
1. Predicate device name(s):
HemoCue Glucose 201 System
2. Predicate 510(k) number(s):
k020935
3. Comparison with predicate:
Both devices are for measurement of the same analyte in the same matrix, have the same intended use, and utilize similar test methodology. The microcuvettes and instrument are mutually exclusive. Both are for POC use, although not specifically identified in the Indications for Use statement.
The reportable range of the candidate device has been expanded from 444 mg/dL to 560 mg/dL. Modifications have been made to the candidate device with regard to the chemical make-up of the microcuvette, storage requirements, dimensions, algorithm, and the software.
K. Standard/Guidance Document Referenced (if applicable):
The sponsor referenced the following guidance document(s) or standards:
CLSI document EP9-A. Method Comparison and Bias Estimation Using Patient Samples; Approved Guideline- Second Edition.
CLSI document EP5-A. Evaluation of Precision Performance of Clinical Chemistry Devices; Approved Guideline.
CLSI document EP7-A. Interference Testing in Clinical Chemistry; Approved Guideline.
CLSI document EP6-A. Evaluation of the Linearity of Quantitative Measurement Procedure: A Statistical Approach; Approved Guideline.
Guidance for Industry - Cybersecurity for Networked Medical Devices Containing Off-the-Shelf (OTS) Software issued January 14, 2005.
The sponsor did not indicate any deviation from these guidances.
{3}
4
L. Test Principle:
The chemical reaction in the cavity of the HemoCue Glucose 201 RT microcuvettes has two phases, hemolysis and the glucose reaction. The glucose reaction is a modified glucose dehydrogenase method in which a tetrazolium salt (MTT) is used to obtain a quantification of glucose in visible light. β-D-glucose is transformed to β-D-glucose using mutarotase. Glucose dehydrogenase acts as a catalyst for the oxidation of β-D-glucose, to form NADH, which in the presence of diaphorase produces a colored formazan with MTT. The measurement takes place in the analyzer in which the transmittance is measured and the absorbance and glucose level is calculated.
M. Performance Characteristics (if/when applicable):
1. Analytical performance:
a. Precision/Reproducibility:
Studies were conducted according to CLSI EP-5A guidance “Evaluation of Precision Performance of Clinical Chemistry Devices; Approved Guidelines.” One batch of Microcuvettes, 5 analyzers, 5 operators, and 3 levels of commercial control were used in the study. Each operator ran duplicate samples twice a day for 20 days. Four hundred samples were run at each level. Results of the studies are presented below.
HemoCue 201 RT Precision
| Sample concentration, ng/mL | SD | CV% | | SD | CV% |
| --- | --- | --- | --- | --- | --- |
| Within-Run | | | Total | | |
| 45 | 1.02 | 2.3 | | 1.07 | 2.4 |
| 137 | 1.70 | 1.2 | | 1.74 | 1.3 |
| 298 | 2.90 | 1.3 | | 4.03 | 1.3 |
Precision was also established in POC studies. See the Method Comparison data in section M2, below.
b. Linearity/assay reportable range:
To verify linearity, the sponsor followed “Evaluation of the Linearity of Quantitative Analytical methods”, CLSI Document EP6-A Vol. 21 No. 28. Five HemoCue 201 RT analyzers were used in the study. Four replicates per level were evaluated on each analyzer. Whole blood concentrations and plasma equivalent converted results (multiplied by 1.1) both appear linear. Samples were EDTA whole blood hemolysates spiked with Glucose to eleven different concentrations ranging from 10-600 mg/dL. Results of the study support the claimed reportable range (12-560 mg/dL).
{4}
c. Traceability, Stability, Expected values (controls, calibrators, or methods):
No calibrators are required. The device is factory calibrated. Calibration is traceable to an ID-GCMS (Isotope Dilution- Gas Chromatography/Mass Spectrometry) system.
Users are instructed to follow local, state, and federal guidelines regarding quality control procedures.
A commercial control material is identified in the labeling, i.e., Eurotrol GlucoTrol-NG. This control was originally cleared during the review of k964053 under the name HemoCue GlucoTrol-NG.
The instrument contains electronic checks which validates that inputs from the LEDs are linear to the output signal of the detector. The sponsor states this indicates the electronics in the device are stable.
d. Detection limit:
The sponsor determined the lower limit of detection (LLD) for the HemoCue Glucose 201 RT system, defined as the lowest concentration which is measured by the analyzer with precision less than or equal to a $20\%$ CV. To establish this, EDTA samples were aged to concentrations down to $10\mathrm{mg / dL}$ and analyzed in replicates on multiple analyzers. A concentration of $12\mathrm{mg / dL}$ generated a $20\%$ CV.
e. Analytical specificity:
The sponsor evaluated the potential for interference from different compounds, proteins and pH levels. The cross reactivity of the enzyme Glucose Dehydrogenase (GDH) with various types of sugar species was also evaluated. The accepted deviation between the test sample (containing the interfering substance) and the mean values for the reference sample (not having the interferents) was $< 10\%$ . Warnings are included in labeling for those with greater than $10\%$ difference.
The sponsor states that they followed "Interference Testing in Clinical Chemistry", CLSI Document EP7-A vol. 22 No 27. The cross-reactivity of the sugar species was analyzed according to an internal procedure.
Five replicates were run on each of five HemoCue Glucose 201 RT analyzers. Results appear below:
| Substance | % Difference between spiked and non-spiked sample at a glucose level of 100 mg/dL | % Difference between spiked and non-spiked sample at a glucose level of 180 mg/dL |
| --- | --- | --- |
| Acetaminophen | 0.38 | 0.50 |
| EDTA 142 mg/dL | -2.0 | -1.0 |
| EDTA 731 mg/dL | -1.4 | -1.8 |
{5}
| Substance | % Difference between spiked and non-spiked sample at a glucose level of 100 mg/dL | % Difference between spiked and non-spiked sample at a glucose level of 180 mg/dL |
| --- | --- | --- |
| Heparin | -0.39 | -0.27 |
| Heparin NaF | -1.55 | -1.10 |
| Potassium oxalate /Sodium fluoride | 0.29 | 0.22 |
| Ascorbic Acid | 4.23 | 1.91 |
| Bilirubin (conjugated) | 4.03 | 1.74 |
| Bilirubin (non-conjugated) | 4.73 | 3.34 |
| Dextran15 g/L | 2.0 | 2.1 |
| Dextran 30 g/L | 3.0 | 3.4 |
| Dextran 45 g/L | 4.4 | 4.8 |
| Dextran 60 g/L | 6.3 | 10.1^{1} |
| Dopamine | 0.5 | -0.4 |
| Ephedrine | 0.20 | 0.11 |
| HbCO | 2.19 | 2.08 |
| HbO_{2} | 7.5 | 4.0 |
| Ibuprofen | 1.43 | 0.00 |
| Caffeine | 0.48 | 0.22 |
| Creatinine | -0.10 | 0.00 |
| L-Dopa | -1.30 | -0.34 |
| MetHb 10 % | -4.5 | -5.0 |
| MetHb 17 % | -10.3^{2} | -7.4 |
| MetHb 26 % | -16.4^{2} | -11.0^{2} |
| MetHb 31 % | -19.7^{2} | -12.5^{2} |
| Methyldopa | 0.00 | -0.55 |
| pH 6.3-6.8 | -1.3 | 0.5 |
| pH 8.5-9.1 | -0.8 | 0.1 |
| Salicylic Acid | 1.63 | 0.92 |
| Tetracycline | -0.41 | -0.49 |
| Cholesterol 6.4 mmol/L | -4.3 | - |
| Cholesterol 7.6 mmol/L | -6.3 | - |
| Cholesterol 8.7 mmol/L | -10.1^{3} | - |
| Triglyceride 2.70 mmol/L | 2.8 | - |
| Triglyceride 5.07 mmol/L | 7.3 | - |
| Triglyceride 9.51 mmol/L | 14.6^{4} | - |
| Tolazamide | 1.34 | 0.79 |
| Tolbutamide | 2.85 | 1.23 |
| Urea | -0.29 | -0.33 |
| Uric Acid | 0.10 | 0.50 |
1 Dextran 60 g/L interfere > 10%. Limitation to 30 g/L
2 MetHb >15 % interfere > 10%. Limitation to 15 %
3 Cholesterol 8.7 mmol/L interfere > 10%. Limitation to 336 mg/dL
4 Triglyceride >6.6 mmol/L interfere > 10%. Limitation to 584 mg/dL
{6}
f. Assay cut-off: Not applicable.
## 2. Comparison studies:
a. Method comparison with predicate device:
The accuracy of the HemoCue 201 RT system was studied at six locations in Sweden (including a study involving six untrained users at 3 at POC locations). A total of 460 samples were analyzed. A summary of the studies is presented below. (Note: For method comparison analysis, the first replicate of the HemoCue Glucose 201 RT is compared to the mean of the comparative method. The exception being the ID-GC/MS study, where only a single ID-GC/MS measurement was taken.)
| Site | Type of intended use site | Number of Operators | Number of samples | Type of samples | Comparative method |
| --- | --- | --- | --- | --- | --- |
| A | Hospital Clinical Laboratory | 1 | 136 | Venous blood | ID GC-MS* |
| B | Hospital Clinical Laboratory | 2 | 128 | Venous blood | Modular Roche -Hexokinase |
| C | Hospital Clinical Laboratory | 2 | 116 | Venous blood | ARCHITECT ci8200 - Hexokinase |
| D | District health centre in primary care | 1 | 26 | Capillary blood | HemoCue Glucose 201 |
| E | District health centre in primary care | 2 | 26 | Capillary blood | HemoCue Glucose 201 |
| F | District health centre in primary care | 3 | 28 | Capillary blood | HemoCue Glucose 201 |
*ID-GC/MS stands for Isotope Dilution-Gas Chromatograph/Mass Spectrometer
Data collected during the study was also used to characterize precision. Portions of the analyses are presented here. Performance among all studies appears comparable.
## Study A- Comparison to ID-GC/MS
Operators were provided with the HemoCue system and the instructions for use, in English, in order to evaluate readability of the labeling. Venous specimens were collected in EDTA tubes. All samples were analyzed in duplicate by the HemoCue and a single measurement was taken on the ID GC-MS reference method. After the study was completed the operators were given a questionnaire to evaluate the effectiveness of the
{7}
labeling. A copy of the questionnaire is included in the submission. Results from the questionnaire were favorable.
## Study Results:
Total mean difference between Glucose 201RT system and the comparative method was 0.23 %.
R² = 0.996 for Glucose 201RT system individual results versus the comparative method.
Bias (Glucose 201 RT – Comparative method) was 0.4 mg/dL
The total standard deviation, SD, between duplicates was 3.1 mg/dL for the Glucose 201RT system.
## HemoCue 201 vs. ID GC/MS
Error grid according to Clark et al.
for HemoCue Glucose 201 RT replicate 1 versus
Comparative method, ID GC-MS, Linköping University Hospital,
Linköping, Sweden
N=136

{8}
9
# Precision- Sites A, B and C (Professional Users), Pooled
The results were divided into three groups; 0-200 mg/dL, 201-400 mg/dL and 401-500 mg/dL. The standard deviation for duplicate samples within each group were calculated according to the formula:
$$
\mathrm{SD} = \sqrt{\frac{\sum d^2}{2n}}
$$
where $d$ is the differences between two microcuvettes and $n$ is the number of samples included in the calculation.
| Group | Number of samples | SD |
| --- | --- | --- |
| 0-200 mg/dL | 259 | 2.04 |
| 201-400 mg/dL | 101 | 3.00 |
| 401-500 mg/dL | 20 | 6.71 |
# Sites D, E and F- POC Locations
Operators were provided with the test system and labeling. Operators did not receive training, coaching, prompting, or written or verbal instructions beyond the written test procedure.
Finger stick samples were taken and tested on the HemoCue Glucose 201 RT system and compared to measurements from the predicate device, the HemoCue Glucose 201 system. All samples were analyzed in duplicate for both methods. The results from 80 samples at all three sites are combined for analysis. There was limited data above $180\mathrm{mg/dL}$ in these studies, i.e., 4 data points between 180 and $220\mathrm{mg/dL}$ and one at $300\mathrm{mg/dL}$.
## Study Results -pooled
Total mean difference between Glucose 201 RT and the comparative method was $0.88\%$
$\mathrm{R}^2 = 0.972$ for HemoCue Glucose 201 RT individual results versus mean of Glucose 201 RT system.
Bias (Glucose 201 RT - Comparative method) was $1.03\mathrm{mg/dL}$.
Calculated total error according to CLSI guidance EP21-A was $-12.0\mathrm{mg/dL}$ to $12.3\mathrm{mg/dL}$ (95% confidence interval calculations).
Total standard deviation, SD, for duplicates was $3.71\mathrm{mg/dL}$ for the Glucose 201 RT system.
Precision estimates were NOT provided for these studies.
{9}
# POC Method Comparison Data
Error grid according to Clark et al. for the
HemoCue Glucose 201 RT replicate 1 vs Comparative method
N=80, Three Point of Care sites

{10}
Combined Method Comparison Data Plotted on a Clarke Error Grid (460 samples)
# Error grid according to Clark et al.
for HemoCue Glucose 201 RT replicate 1 versus
Comparative method for all sites, venous and capillary blood
N=460

# b. Matrix comparison:
The sponsor demonstrated equivalence between capillary whole blood samples, arterial, and venous whole blood samples (EDTA, Heparin, Sodium oxalate, potassium oxalate). A minimum of 10 specimens of each sample type were drawn from multiple individuals, and the samples were spiked with glucose (in order to obtain glucose concentrations
{11}
spanning the reportable range). Each sample was analyzed by the HemoCue and a laboratory hexokinase method. Results among all matrices appear equivalent. Calculated differences between all data pairs were analyzed and are presented below.
Matrix Equivalence Study Results
| Matrix | Mean differences in Percent (Glucose 201 RT - Comparative) |
| --- | --- |
| Capillary | 0.3 |
| Venous EDTA | -3.3 |
| Venous NaHep | 4.8 |
| Venous KOx | 7.4 |
| Arterial | -4.5 |
Additionally, studies for venous EDTA and capillary blood were done during the method comparison studies. (See Section 2a above.) Anticoagulants (EDTA, heparin, and potassium oxalate) were also evaluated in the interference portion of the specificity studies. See section 1E above.
3. Clinical studies:
a. Clinical Sensitivity:
Not applicable. Clinical studies are not typically submitted for this device type and matrix.
b. Clinical specificity:
Not applicable. Clinical studies are not typically submitted for this device type and matrix.
c. Other clinical supportive data (when a. and b. are not applicable):
4. Clinical cut-off:
Not applicable. This is a quantitative test with reference ranges.
5. Expected values/Reference range:
Fasting glucose values (reference interval): Plasma glucose, adults 74-106 mg/dL. This is consistent with the predicate's reference range.
N. Instrument Name:
HemoCue 201 RT
{12}
O. System Descriptions: (See Section 16.)
1. Modes of Operation:
Photometric / Colorimetric
2. Software:
FDA has reviewed applicant’s Hazard Analysis and software development processes for this line of product types:
Yes ☐ X or No ☐
The sponsor has classified their device as a Moderate Level of Concern.
The following sections are presented in the submission, and appear adequate:
1. Software Description- A summary overview of the features that are controlled by the software and the intended software operating environment.
2. Hazard Analysis- Tabular description of identified hardware and software hazards, including severity assessment and mitigations.
3. Software Requirements Specification (SRS)- A summary of functional requirements for the software, e.g., interface, performance, or functional needs. The complete SRS is provided. (See page 163.)
4. Architecture Design Chart
5. Traceability Analysis
6. Software Development Environment Description- A summary of the software development life cycle and the processes that are in place to manage the various life cycle activities, e.g., changes or adjustments to software after released into market.
7. Verification and Validation Documentation- Verification means confirmation that specified requirements have been fulfilled. Validation is confirmation that specifications meet the needs of the user.
8. Revision Level History- Revision history log, including release version numbers and dates.
9. Unresolved Anomalies- The sponsor indicates there are no unresolved anomalies.
3. Specimen Identification:
Specimen information is manually entered by the operator.
4. Specimen Sampling and Handling:
Whole blood capillary samples are the primary sample type used. Other anticoagulated venous whole blood samples are also acceptable, along with arterial samples.
13
{13}
5. Calibration:
The instrument is calibrated at the manufacturer's site and is traceable to an ID/MS method. Using a series of calibrators, a standard curve is constructed which is lot specific. The calibration information is contained within the barcode which accompanies each reagent unit.
Users do not calibrate the device.
6. Quality Control:
The system utilizes external control materials. An FDA cleared control material is identified in the labeling. Additionally, the instrument contains electronic checks.
P. Other Supportive Instrument Performance Characteristics Data Not Covered In The "Performance Characteristics" Section above:
None.
Q. Proposed Labeling:
The labeling is sufficient and it satisfies the requirements of 21 CFR Part 809.10.
R. Conclusion:
The submitted information in this premarket notification is complete and supports a substantial equivalence decision.
14
Predicate graph will load when search results are available.
Embedding visualization will load when search results are available.
PDF viewer will load when search results are available.
Loading panels...
Select an item from Submissions
Click any panel, subpart, regulation, product code, or device to see details here.
Section Matches
Results will appear here.
Product Code Matches
Results will appear here.
Special Control Matches
Results will appear here.
Loading collections...
Loading
My Alerts
You will receive email notifications based on the filters and frequency you set for each alert.
Sort by:
Create Alert
Search Filters
Agent Token
Create a read-only bearer token for Claude, ChatGPT, or other agents that can call HTTP APIs.
Copy this now. It will not be shown again.
Connected apps
Apps you authorized through browser sign-in. Disconnecting revokes their access immediately.
Learn the FDA Browser
Two short videos show you everything — or skip straight to the written tutorial if you'd rather read. You can reopen this any time from the Tutorial button in the top bar.
Part 1 — Search, results, and everyday workflows 16 min
Part 2 — Embeddings: the galaxy map 3 min
1. Search: exact and fuzzy
Type a phrase like "coronary artery calcification" into the search box. You get two kinds of results. Exact results match the literal phrase — prefix searches work ("coronary artery calcificati") but suffix searches do not. Fuzzy results match on the meaning and intent of your phrase rather than the exact words, and are sorted by relevance score. Hover over the Exact or Fuzzy badge on any row to see exactly why it matched.
Use the checkboxes above the results to narrow: SaMD keeps only software-only devices, AI / ML keeps only devices with AI.
Exact vs. fuzzy search: what's the difference?
Exact matches on the literal phrase (prefix search works, suffix does not). Fuzzy matches on the meaning and intent of the phrase rather than the exact words. Hover over the badge on any row to see why it matched.
You search "coronary artery calcification" and want only software devices with AI. What two filters do you apply?
Narrow by SaMD (software-only devices), then narrow by AI/ML (devices with AI).
2. The results table
Scroll right in the results table. The intended use is extracted for you — no need to open the PDF. The device story gives a high-level snapshot of what the device does and how it's used. The AI Performance sub-table shows each output name, acceptance criteria, observed values, and development/test dataset descriptions — the same format Innolitics uses for regulatory strategy outputs, and the fastest high-level fingerprint of an AI device. It is AI-generated but has been very reliable in practice.
Where do you find a device's intended use without opening the PDF?
Scroll right in the search results table. The intended use column is extracted for you; no need to dig into the 510(k) summary PDF.
What does the AI Performance sub-table show, and why is it useful?
Output name, acceptance criteria, observed values, development dataset description, and test dataset description. It's the same format we use for regulatory strategy output and Fast 510(k) input, and the fastest high-level fingerprint of an AI device. AI-generated but reliable in practice.
3. Judging fuzzy relevance
Fuzzy results trail off in relevance as you scroll. Use three signals to decide how far down to go: the fuzzy badge explanations, the intended use column, and whether your target output (e.g., Cobb angle) still appears in the AI Performance sub-table. Once it stops appearing, you're past the relevant zone. A top hit with a low score (~0.4) and a stretched explanation is a hint the closest predicates are far away — the project may be headed for De Novo. Note the fuzzy search is a pattern match: it doesn't handle negation ("not") well, and hardware devices can appear — filter by SaMD/AI ML to cut them.
How do you judge how far down fuzzy search results to go?
Use the relevancy signals: the fuzzy badge explanations, the intended use column, and whether the target output (e.g., Cobb angle) still appears in the AI Performance sub-table. Once it stops appearing, results are trailing off in relevancy.
4. Device detail page: chat and citations
Click a device name to open its detail page: device facts on the left, a chat window on the right. Ask something like "Describe the training data". The answer carries little citation bubbles — click one to jump to the highlighted passage in the source PDF, so you can verify every AI answer against the document. There's also a Download PDF button for sharing.
How do you verify an AI chat answer on the device detail page?
Click the citation bubbles to jump to the relevant highlight in the source document.
Reading rule for every project: how many summaries do you read in full?
At least the three most relevant 510(k) or De Novo summaries, in full. After that, use targeted chat questions to confirm your memory quickly. The tool supports this professional habit — it doesn't replace it.
5. Side-by-side comparison
Select multiple rows in the results table (aim for under ~10), then open the PDF Viewer tab. Ask one question — it goes to all selected devices in parallel, each with citations. This is the fastest way to compare and contrast devices: training data, PCCP scope, how they handled adding new scanners, and so on.
What does the side-by-side PDF viewer mode do?
Select multiple devices, open the PDF viewer tab, and ask one question (e.g., "Describe the training data"). It queries all selected devices simultaneously with citations, so you can compare and contrast quickly.
6. Collections
With rows selected, go to the Collections tab and create a labeled collection (e.g., "Cobb Angle Project"). Reload that selection any time — before a client call, pull up the collection and ask questions across all of its devices at once.
How do you save a set of selected devices for later use?
Select the rows, go to the Collections tab, and create a labeled collection (e.g., "Cobb Angle Project"). You can reload the selection anytime and carry it into the PDF viewer and other tabs that support selections.
7. Product codes and the regulations tree
Click a product code in the results to jump to it in the regulations tree — identification text, sibling product codes, and devices you can open in a PDF viewer on the right. Click a regulation number to see its identification, special controls, and related product codes. You can also search by product code or regulation number at the top of the tree. Always read the special controls if any exist for your device — it broadens your search and sharpens pre-kickoff research.
What can you do from the regulations tree view?
Browse product codes and regulation numbers, read the identification text and special controls, browse sibling product codes, open device PDFs on the right, and search by product code or regulation number at the top of the tree.
8. Chart view
Click Show Chart and segment by regulation number (or product code) to see which regulations dominate your result set. Clicking a regulation takes you into the regulations tree. Great for spotting that most matches are, say, hardware laparoscopic devices — a cue to go back and filter.
How do you see which regulations dominate a search result set?
Click "Show Chart" and segment by Regulation Number. Clicking a regulation takes you to the regulations tree.
9. The predicate graph
Open the Predicates tab for a family-tree view of predicate relationships. Click a node to trace its parents and children; selections from search carry over pre-selected. Commonly predicated devices are worth reading — a lot of people predicated them for a reason. The visual lineage is also handy on client calls, e.g. to show how a predicate family evolved and justify why your predicate still holds.
In the predicate graph, why are commonly predicated devices worth reading?
A lot of people predicated them for a reason. Clicking a node traces parents and children, and selections from search carry over pre-selected.
10. Embeddings: the galaxy map
The Embeddings tab plots every matching document in a 2-D "galaxy map" where semantically similar devices cluster together. Hover or click clusters to explore, and let AI label the clusters for you. Embeddings beat product codes for grouping: two devices can carry different product codes (LLZ vs. QIH) yet do the same thing — the embedding captures the meaning of the intended use and device story. This is also exactly how retrieval-augmented generation (RAG) works under the hood, and it makes a great visual on client calls.
Try it yourself
Head to the search page and work through a few of these AI/ML fuzzy searches to build intuition: perivascular fat on CT · aortic valve calcification opportunistic screening on noncontrast CT · breast cancer prediction on digital pathology slides · autism detection · gestational age prediction · a hearing aid that can also detect a pulse · foundation model based analysis of ECG · large language models · penetration test. Watch how the relevance scores, intended use, and AI Performance tables tell you when results stop being meaningful.