The ARK™ Levetiracetam Assay is a homogeneous enzyme immunoassay intended for the quantitative determination of levetiracetam in human serum or plasma on automated clinical chemistry analyzers. Levetiracetam concentrations can be used as an aid in management of patients treated with levetiracetam. The ARK™ Levetiracetam Calibrator is intended for use in calibration of the ARK Levetiracetam Assay. The ARK™ Levetiracetam Control is intended for use in quality control of the ARK Levetiracetam Assay.
Device Story
The ARK Levetiracetam Assay is a homogeneous enzyme immunoassay (EIA) used in clinical laboratories to measure levetiracetam concentrations in human serum or plasma. The device utilizes a two-reagent system: R1 containing anti-levetiracetam polyclonal antibodies and R2 containing levetiracetam labeled with bacterial glucose-6-phosphate dehydrogenase (G6PDH). The assay operates via competitive binding between the drug in the patient specimen and the enzyme-labeled drug for the antibody. When the drug is present, enzyme activity increases, converting NAD to NADH, which is measured spectrophotometrically as a rate of change in absorbance. The assay is performed on automated clinical chemistry analyzers. Results are used by clinicians to monitor therapeutic drug levels and manage patients on levetiracetam therapy. The system includes dedicated calibrators and controls for quality assurance.
Clinical Evidence
Bench testing only. Performance validated per CLSI protocols. Limit of Quantitation (LOQ) established at 2.0 µg/mL. Linearity demonstrated from 2.0 to 100.0 µg/mL. Method comparison against LC/MS/MS (n=305) showed Passing-Bablok regression slope of 1.01, y-intercept of 0.25, and r² of 0.97. Precision studies (n=160 per level) showed total CVs < 5%. Interference testing confirmed ≤10% error for common endogenous substances, metabolites, and co-administered anti-epileptic drugs.
Technological Characteristics
Homogeneous enzyme immunoassay (EIA). Two-reagent system: R1 (rabbit polyclonal anti-levetiracetam antibody, substrate) and R2 (levetiracetam-labeled bacterial G6PDH). Liquid, stored at 2-8°C. Operates on automated clinical chemistry analyzers via spectrophotometric measurement of NADH production. Includes six-level calibrators and three-level controls.
Indications for Use
Indicated for quantitative determination of levetiracetam in human serum or plasma to aid in the management of patients treated with levetiracetam. For prescription use only.
Regulatory Classification
Identification
A diphenylhydantoin test system is a device intended to measure diphenylhydantoin, an antiepileptic drug, in human specimens. Measurements obtained by this device are used in the diagnosis and treatment of diphenylhydantoin overdose and in monitoring levels of diphenylhydantoin to ensure appropriate therapy.
{0}
510(k) SUBSTANTIAL EQUIVALENCE DETERMINATION
DECISION SUMMARY
DEVICE ONLY TEMPLATE
A. 510(k) Number:
k091653
B. Purpose for Submission:
New assay
C. Analyte:
Levetiracetam
D. Type of Test:
Homogeneous enzyme immunoassay
E. Applicant:
ARK Diagnostics, Inc.
F. Proprietary and Established Names:
ARK™ Levetiracetam Assay, Calibrators and Controls
G. Regulatory Information:
1. Regulation section: 21 CFR 862.3350, 862.3200, 862.3280
2. Classification: Class II
3. Product code: NWM (assay), LAS (controls), DLJ (calibrator)
4. Panel: 91
H. Intended Use:
1. Intended use(s):
See indications for use.
2. Indication(s) for use:
The ARK™ Levetiracetam Assay is a homogeneous enzyme immunoassay intended for the quantitative determination of levetiracetam in human serum or plasma on automated clinical chemistry analyzers. Levetiracetam concentrations can be used as an aid in management of patients treated with levetiracetam.
The ARK™ Levetiracetam Calibrator is intended for use in calibration of the ARK Levetiracetam Assay.
The ARK™ Levetiracetam Control is intended for use in quality control of the ARK Levetiracetam Assay.
3. Special conditions for use statement(s):
{1}
For prescription use only.
See information in Expected Range Section below for special conditions for use.
# 4. Special instrument requirements:
The assay has been validated on the Hitachi 917.
# I. Device Description:
The ARK Levetiracetam Assay consists of reagents R1 anti-levetiracetam polyclonal antibody with substrate and R2 levetiracetam labeled with bacterial G6PDH enzyme. The ARK Levetiracetam Calibrator consists of a six-level set (target values: 0.0, 5.0, 12.5, 25.0, 50.0, and $100\mu \mathrm{g / mL}$ ) to calibrate the assay, and the ARK Levetiracetam Control consists of a three-level (target values 7.5, 30, $75\mu \mathrm{g / mL}$ ) set used for quality control of the assay.
# J. Substantial Equivalence Information:
1. Predicate device name(s): ARK Topiramate Assay
2. Predicate 510(k) number(s) k083799
3. Comparison with predicate:
| Characteristic | Device ARK™ Levetiracetam Assay | Predicate ARK™ Topiramate Assay K083799 |
| --- | --- | --- |
| Intended Use | The ARK™ Levetiracetam Assay is intended for the quantitative determination of levetiracetam in human serum or plasma on automated clinical chemistry analyzers. | The ARK™ Topiramate Assay is intended for the quantitative determination of topiramate in human serum or plasma on automated clinical chemistry analyzers. |
| Indications for Use | Levetiracetam concentrations can be used as an aid in management of patients treated with levetiracetam. | The results obtained are used in the diagnosis and treatment of topiramate overdose and in monitoring levels of topiramate to help ensure appropriate therapy. |
| Sample | Serum or plasma | Serum or plasma |
| Methodology | Homogenous enzyme immunoassay (EIA) | Homogenous enzyme immunoassay (EIA) |
| Reagent Components | Two (2) reagent system: Anti-levetiracetam Antibody/Substrate Reagent (R1) containing rabbit polyclonal antibodies to levetiracetam, glucose-6-phosphate, nicotinamide adenine dinucleotide, bovine serum albumin, preservatives, and stabilizers Enzyme Reagent (R2) containing | Two (2) reagent system: Anti-topiramate Antibody/Substrate Reagent (R1) containing rabbit polyclonal antibodies to an epitope of topiramate, glucose-6-phosphate, nicotinamide adenine dinucleotide, bovine serum albumin, preservatives, and stabilizers Enzyme Reagent (R2) containing |
{2}
Page 3 of 9
| | levetiracetam labeled with bacterial G6PDH, buffer, bovine serum albumin, preservatives, and stabilizers | topiramate epitope labeled with bacterial G6PDH, buffer, bovine serum albumin, preservatives, and stabilizers |
| --- | --- | --- |
| Platform required | Automated clinical chemistry analyzer | Automated clinical chemistry analyzer |
| Testing environment | Routine clinical laboratory | Routine clinical laboratory |
## K. Standard/Guidance Document Referenced (if applicable):
CLSI documents:
“Evaluation of Precision Performance of Clinical Chemistry Devices”, EP5;
“Evaluation of the Linearity of Quantitative Measurement”, EP6;
“Interference Testing in Clinical Chemistry”, EP7;
“Method Comparison and Bias Estimation Using Patient Samples”, EP9;
“Protocols for Determination of Limits of Detection and Limits of Quantitation”, EP 17-A.
## L. Test Principle:
The ARK Levetiracetam Assay is a homogeneous immunoassay based on competition between drug in the specimen and levetiracetam labeled with the enzyme glucose-6-phosphate dehydrogenase (G6PDH) for binding to the antibody reagent. As the latter binds antibody, enzyme activity decreases. In the presence of drug from the specimen, enzyme activity increases and is directly proportional to the drug concentration. Active enzyme converts the coenzyme nicotinamide adenine dinucleotide (NAD) to NADH that is measured spectrophotometrically as a rate of change in absorbance. Endogenous serum G6PDH does not interfere with the results because the co-enzyme NAD functions only with the bacterial enzyme used in the assay.
## M. Performance Characteristics (if/when applicable): Performance was validated on the Hitachi 917 instrument.
### 1. Analytical performance:
#### a. Precision
Samples evaluated included the ARK Levetiracetam Control and three pooled human serum samples. Data were collected on a single analyzer over twenty non-consecutive days. Five calibrations were performed (Days 1, 5, 10, 12 and 17) during this interval to provide variation (calibration was performing in a stable manner). Each sample was assayed in quadruplicate twice a day, with each run separated by at least two hours. Calculations were conducted according to CLSI Guideline EP5-A2. Results are summarized below:
{3}
Page 4 of 9
| | | | Within Run | | Between Day | | Total | |
| --- | --- | --- | --- | --- | --- | --- | --- | --- |
| Sample | N | Mean (μg/mL) | SD | CV (%) | SD | CV (%) | SD | CV (%) |
| Control Low | 160 | 7.5 | 0.25 | 3.4 | 0.23 | 3.2 | 0.34 | 4.5 |
| Control Mid | 160 | 29.4 | 0.85 | 2.9 | 0.83 | 2.8 | 1.08 | 3.7 |
| Control High | 160 | 73.4 | 2.14 | 2.9 | 2.03 | 2.8 | 3.08 | 4.2 |
| Low Patient Pool | 160 | 6.9 | 0.26 | 3.8 | 0.22 | 3.1 | 0.33 | 4.8 |
| Mid Patient Pool | 160 | 30.2 | 0.87 | 2.9 | 1.10 | 3.7 | 1.23 | 4.1 |
| High Patient Pool | 160 | 75.5 | 2.19 | 2.9 | 2.35 | 3.1 | 3.31 | 4.4 |
## b. Linearity/assay reportable range:
The manufacturer's claimed assay reportable range is from 2.0 to 100 μg/mL, based on linearity, recovery, lower limit of quantitation and method comparison results submitted in the 510(k). (See respective sections below for specific information on performance).
## Linearity:
Samples ranging from 2 to 100 μg/mL were prepared from a gravimetrically prepared levetiracetam stock solution and levetiracetam-free serum pools. The dilutions were prepared so that levetiracetam concentrations varied in increments of 1 ug/mL within the range 2-10 μg/mL; and in increments of 10 ug/mL within the range of 10 μg/mL - 100 μg/mL. The averaged results of multiple runs and replicates (n=6) for each sample using the ARK assay were used in the calculations. Regression analyses were performed between the measured mean levetiracetam and the nominal values for each dilution, using first order and second order polynomial determinations according to CLSI/NCCLS EP6-A. In the range from 7-100 ug/mL deviations from linearity were < 2%. In the range from 4-7 μg/mL, deviations were less than 5%, and in the range from 2-3 μg/mL, deviations ranged from 8 -13%. Regression equation was:
(measured) = 1.0309(gravimetrically determined) + 0.0264, r² = 0.9996
## Trueness/Recovery:
Serum samples across the assay range were prepared containing pure levetiracetam (USP). The results of the six replicates were averaged and compared to the theoretical target concentration and the percentage recovery was calculated.
Results are shown below. Percent Recovery = 100 x Mean recovered concentration Theoretical concentration
| Theoretical Concentration (μg/mL) | Mean Recovered Concentration (μg/mL) | Percent Recovery |
| --- | --- | --- |
| 2.0 | 1.9 | 95.8 |
| 4.0 | 3.8 | 94.6 |
{4}
Page 5 of 9
| 10.0 | 10.0 | 100.0 |
| --- | --- | --- |
| 20.0 | 19.2 | 95.9 |
| 45.0 | 44.1 | 98.0 |
| 80.0 | 79.3 | 99.1 |
| 100.0 | 105.3 | 105.3 |
Dilution of high samples:
The package insert recommends that patient samples with concentrations above the assay range may be diluted with zero calibrator. To support this, both spiked samples, and high patient samples were diluted 4-fold with zero calibrator (calibrator A) before pipetting the sample into the sample cup. The average of multiple measurements was used to determine recovery (relative to gravimetric concentration) for spiked samples and (relative to LC/MS/MS) for patient samples. Results are shown below.
Spiked Sample Dilution
| Spiked Level | Mean (μg/mL) | Dilution Factor | Recovery (%) |
| --- | --- | --- | --- |
| 200.0 μg/mL | 50.6 (n = 10) | 4 | 101.2 |
Patient Specimen Dilution
| LC/MS/MS (μg/mL) | ARK Result x Dilution Factor 4 (μg/mL) | Diff (%) |
| --- | --- | --- |
| 144.2 | 136.4 | -5.4 |
| 104.6 | 102.0 | -2.5 |
| 108.4 | 128.8 | 18.8 |
| 107.6 | 104.8 | -2.6 |
To further examine the dilution procedure (recommended in the package insert) for any matrix effects, patient samples with concentrations in the assay range were diluted 4-fold with both serum and calibrator. The percent recovery for both are shown below.
Diluted Patient Specimen: Comparison to LC/MS/MS
| Diluted with Cal A Result x factor 4 | | | Diluted with serum Result x factor 4 | |
| --- | --- | --- | --- | --- |
| LC/MS/MS (μg/mL) | (μg/mL) | % Difference | (μg/mL) | % Difference |
| 86.4 | 82.4 | -4.6 | 86.4 | 0.0 |
| 55.5 | 56.8 | 2.3 | 56.0 | 0.9 |
| 42.8 | 39.6 | -7.5 | 38.8 | -9.3 |
| 41.1 | 38.4 | -6.6 | 40.4 | -1.7 |
| 30.2 | 28.8 | -4.6 | 28.4 | -6.0 |
c. Traceability, Stability, Expected values (controls, calibrators, or methods):
Stability:
5
{5}
Stability is evaluated using both accelerated and real-time protocols. For real-time stability testing, performance of materials refrigerated at 2-8 degrees C are compared to a reference set of materials that are stored frozen. Results are evaluated at multiple time points during the expiration dating period for accuracy and precision in measuring levetiracetam controls. No change in recovery or precision was observed in the real-time studies submitted in the 510(k). Real time studies (to support the expiration dating of 25 months) are ongoing.
Calibrator value assignment:
Stock solutions of pure levetiracetam (USP) were prepared and then added to both the synthetic calibrator/control matrix (calibrator A) to achieve the calibrator concentrations of 4.0 µg/mL, 10.0 µg/mL, 20.0 µg/mL, 45.0 µg/mL and 80.0 µg/mL levels. Samples were assayed by the ARK™ Levetiracetam Assay. Multiple runs and replicates were evaluated to determine recovery in the two matrices. The same spiking was performed with serum, so that any matrix effects may be detected. Analytical recoveries observed were 92-98% in the calibrator/control matrix and 95-100% in the serum matrix.
Control value assignment:
Quality control (QC) ranges were established using three runs with four replicates tested per run (n=12 for each control level) and the mean levetiracetam level of each control was calculated. Control ranges were set at ± 15% around the mean level tested. The package insert notes that each laboratory should establish its own ranges for each new lot of controls.
### d. Detection limit:
Accuracy and precision studies near the low range of the assay were conducted to determine the manufacturer's claimed lower limit of quantitation (LOQ). Studies generally followed CLSI Guideline EP-17 guideline. Three levetiracetam levels were tested below the lowest positive calibrator concentration (5.0 µg/mL). Samples were prepared by gravimetric addition of pure levetiracetam (USP) to stock solution, and addition of this stock solution to pooled human serum negative for levetiracetam. Concentrations included 1.0, 2.0 and 3.0 µg/mL. Eight replicates of each sample were tested in each of five runs to give 40 replicates of each sample. Testing was performed on a total of 3 lots. Each run was performed on a separate day, with a separate calibration to enhance variability (i.e. challenge the assay). Results for all lots supported that performance met the manufacturer's acceptance criteria of the LOQ of 2.0 µg/mL having CV within 20% and recovery within +/-15%.
### e. Analytical specificity:
Studies included testing for interference from endogenous compounds, metabolite, and commonly co-administered, and other anti-epileptic drugs.
Serum samples with clinically high concentrations of the potential interfering substances were tested by the assay in the presence of varying amounts of levetiracetam.
{6}
Page 7 of 9
Specifically, serum samples tested contained levetiracetam at concentrations of 50 ug/mL, 15 ug/mL, and in some cases also 6 ug/mL. In addition, metabolite cross-reactivity was also tested in the absence of levetiracetam. Each sample containing interferent was assayed, along with a serum control of levetiracetam. Results for endogenous compounds and the metabolite ucb L057 are shown below. The complete list of interferents tested and results are included in the package insert.
| Interfering Substance | Highest Interferent Concentration tested | Percent recovery relative to control | |
| --- | --- | --- | --- |
| | | 15 μg/mL Levetiracetam | 50 μg/mL Levetiracetam |
| Albumin | 12 g/dL | 99.8 | 102.6 |
| Bilirubin | 70 mg/dL | 100.4 | 102.1 |
| Bilirubin | 70 mg/dL | 99.3 | 107.9 |
| Cholesterol | 535 mg/dL | 105.3 | 94.0 |
| Gamma-Globulin | 12 g/dL | 99.8 | 109.5 |
| Hemoglobin | 1000 mg/dL | 98.6 | 100.9 |
| Intralipid® | 1500 mg/dL | 97.1 | 99.8 |
| Rheumatoid Factor | 1100 IU/mL | 98.1 | 106.4 |
| Triglycerides | 1033 mg/dL | 96.8 | 100.2 |
| Uric Acid | 30 mg/dL | 99.6 | 102.5 |
Metabolite (2-pyrrolidone-N-butyric acid) ucb L057:
| Percent recovery of levetiracetam in presence of 250 ug ucb L057 | | | | |
| --- | --- | --- | --- | --- |
| Conc. Tested (μg/mL) | 0 μg/mL Levetiracetam | 6 μg/mL Levetiracetam | 15 μg/mL Levetiracetam | 50 μg/mL Levetiracetam |
| 250.0 | 0.0 | 95.1 | 97.0 | 106.6 |
(Results correspond to cross-reactivity calculations of 1.3% at 50 μg/mL, and -0.2% at 15 ug/mL in this evaluation.)
f. Assay cut-off:
See limit of quantitation section.
7
{7}
Page 8 of 9
2. Comparison studies:
a. Method comparison with predicate device:
Method comparison studies were performed using banked samples obtained from two laboratories. Specimens were mostly derived from a wide geographic area in the U.S., from patients across a wide range of ages, including both male and female. Samples were selected to be within the assay concentration range. No other selection criteria were applied.
Results of samples obtained with the ARK assay were compared to those obtained with three different reference methods. Assay descriptions and summary validation information for the comparator methods were included in the 510(k). In the largest of the three evaluations (n=305) results were compared to those of an LC/MS/MS assay. Results of Passing-Bablok regression analysis for this study are shown below:
Method comparison summary:
| Comparative Method | Number of Samples and range | Slope (95% CI) | Intercept (95% CI) | Mean bias of ARK relative to LCMS (SD) | Correlation coefficient (r²) |
| --- | --- | --- | --- | --- | --- |
| LC/MS/MS | N= 305
Range: 2-86 ug/mL | Y = 1.01 (0.99 to 1,03) | 0.25 (-0.24 to 0.63) | 0.76 (0.35 to 1.16) | 0.97 (0.96 to 0.97) |
In addition there were smaller method comparison studies with two additional reference methods. The averaged bias (reference minus ARK) was within 10%. Additional testing of patient samples, with levetiracetam concentrations close to 100 ug/mL, by the ARK assay and the reference method demonstrated agreement. Differences were all within +/- 10%.
b. Matrix comparison:
Assay recovery, as well as precision (within one run) was evaluated for levetiracetam spiked into the following plasma types: Lithium heparin, Potassium, EDTA, Sodium heparin and serum. Matched specimens for serum and plasma were collected from eight subjects. Five samples spiked with levetiracetam (2, 10, 20, 40, 80 µg/mL) were prepared from each specimen (for a total of 40 samples per anticoagulant). Replicate measurements for each of the forty samples were averaged. Percent recoveries for all forty samples ranged from 95.3% to 109.6% relative to nominal spiked values; and from 95.0 to 107.2 for plasma relative to serum values. For the large majority of samples recoveries well-within these ranges were observed, and no specific trends (of differences in recovery relative to concentration) were observed.
In addition, the sponsor submitted a summary of literature suggesting equivalence between serum and heparinized plasma for measuring levetiracetam in patient samples, as
8
{8}
Page 9 of 9
well as literature cautioning that levetiracetam is hydrolyzed in blood (Patsalos et al, Epilepsia 47 1818-21, 2006). To address this, the package insert advises users to process the blood as soon as possible after collection to prepare serum or plasma, since hydrolysis of levetiracetam may occur in the prolonged presence of whole blood.
3. Clinical studies:
a. Clinical Sensitivity: NA. Not typically submitted for this type of assay.
b. Clinical specificity: NA. Not typical for this type of assay.
c. Other clinical supportive data (when a. and b. are not applicable): The sponsor provided a discussion with balanced and representative literature discussing clinical use of levetiracetam measurements.
4. Clinical cut-off: see expected values.
5. Expected values/Reference range:
The following is included in the package insert:
A reference range for levetiracetam has not been well established. Tentative reference ranges for seizure control have been proposed, which include concentrations from 6 to 46 $\mu \mathrm{g} / \mathrm{mL}$ (35 to $270~\mu \mathrm{mol} / \mathrm{L}$ ; trough samples). However, these ranges have not been validated by adequate controlled trials, and in general the relationship between these serum concentrations and clinical effect has not been well-defined. Levetiracetam drug concentrations should be used in conjunction with information available from clinical evaluations and other diagnostic procedures. Circulating levels of levetiracetam (serum blood concentrations) may be affected by compliance, renal function, pregnancy, drug-drug interactions and timing of the sample draw. Furthermore, the clinical effect of these serum blood concentrations may be further altered by changes in progression in the severity of the disease and the addition or withdrawal of concomitant drugs which may interact pharmacodynamically with circulating levels of levetiracetam.
The reference range of drug concentrations which is quoted should only imply a lower limit below which a therapeutic response is relatively unlikely to occur, and an upper limit above which toxicity is relatively likely to occur in the specific patient populations studied. Generally, clinicians using reference ranges such as these should be aware that, because of individual variation, patients may achieve therapeutic benefit with serum drug concentrations outside of these ranges and may experience toxicity with levels below the lower limit of the reference range. Sampling time should be standardized such that trough serum concentrations are measured just before the next dosage, preferably in the morning.
N. Proposed Labeling:
The labeling is sufficient and it satisfies the requirements of 21 CFR Part 809.10.
O. Conclusion:
The submitted information in this premarket notification is complete and supports substantial equivalence decision.
9
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.