ONLINE PHENOBARBITAL, MODEL 03016757190 & 03510620
Applicant
Roche Diagnostics Corp.
Product Code
DLZ · Clinical Toxicology
Decision Date
Sep 12, 2007
Decision
SESE
Submission Type
Traditional
Regulation
21 CFR 862.3660
Device Class
Class 2
Indications for Use
The ONLINE TDM Phenobarbital assay is for the quantitative determination of phenobarbital in human serum or plasma on Roche automated clinical chemistry analyzers. Measurements obtained by this device are used in the diagnosis and treatment of phenobarbital use or overdose and in monitoring levels of phenobarbital.
Device Story
The ONLINE TDM Phenobarbital assay is an in vitro diagnostic reagent kit used on Roche automated clinical chemistry analyzers (Hitachi 912, 917, and Modular P). It measures phenobarbital concentrations in human serum or plasma samples. The assay utilizes enzyme immunoassay technology to quantify drug levels. Clinicians use these quantitative results to individualize patient dosage, achieve maximal seizure control, minimize side effects, and diagnose potential overdose. The device is intended for use in clinical laboratory settings by trained laboratory personnel. By providing accurate, automated monitoring of serum drug levels, the device assists healthcare providers in optimizing therapeutic regimens for patients with epilepsy.
Clinical Evidence
Bench testing only. Precision studies (within-run and total) performed on Hitachi 917 showed CVs < 5% at high concentrations. Linearity assessed across 2.4–60 µg/mL range with recoveries 89.39%–113.75%. Method comparison against predicate (n=53) yielded a correlation of R=0.996 and slope of 1.047. Interference studies confirmed no significant impact from bilirubin, hemolysis, lipemia, proteins, or common drugs.
Indicated for quantitative determination of phenobarbital in human serum or plasma for patients requiring monitoring of phenobarbital levels for the diagnosis and treatment of phenobarbital use or overdose, including management of grand mal, psychomotor, and focal epilepsy.
Regulatory Classification
Identification
A phenobarbitol test system is a device intended to measure phenobarbital, an antiepileptic and sedative-hypnotic drug, in human specimens. Measurements obtained by this device are used in the diagnosis and treatment of phenobarbital use or overdose and in monitoring levels of phenobarbital to ensure appropriate therapy.
Predicate Devices
Roche COBAS INTEGRA Phenobarbital assay (k951595)
Submission Summary (Full Text)
{0}
1
510(k) SUBSTANTIAL EQUIVALENCE DETERMINATION
DECISION SUMMARY
ASSAY ONLY TEMPLATE
A. 510(k) Number:
k071644
B. Purpose for Submission:
New device
C. Measurand:
Phenobarbital
D. Type of Test:
Quantitative enzyme immunoassay
E. Applicant:
Roche Diagnostics Corp.
F. Proprietary and Established Names:
Online TDM Phenobarbital Assay
G. Regulatory Information:
1. Regulation section:
21 CFR 862.3660 Phenobarbital test system
2. Classification:
Class II
3. Product code:
DLZ
4. Panel:
91 (Toxicology)
{1}
H. Intended Use:
1. Intended use(s):
See indications for use statement below.
2. Indication(s) for use:
The ONLINE TDM Phenobarbital assay is for the quantitative determination of phenobarbital in human serum or plasma on Roche automated clinical chemistry analyzers. Measurements obtained by this device are used in the diagnosis and treatment of phenobarbital use or overdose and in monitoring levels of phenobarbital.
3. Special conditions for use statement(s):
For prescription use only.
4. Special instrument requirements:
For Roche/Hitachi 912/917/ and MODULAR P analyzers. The cobas (lower case) is associated with Hitachi instruments, and COBAS (capital letters) is associated with COBAS Integra analyzers.
I. Device Description:
The ONLINE TDM Phenobarbital assay is comprised of two ready to use reagents. Reagent 1 is a conjugate reagent consisting of phenobarbital conjugate, piperazine-N, bugger, preservative and stabilizer. Reagent 2 is a latex antibody reagent consisting of anti-phenobarbital antibody (mouse monoclonal), latex microparticle, MOPS, bugger, stabilizer and preservative. The previously cleared preciset TDM calibrators are not included with the device but are suggested in the package insert (k031856).
J. Substantial Equivalence Information:
1. Predicate device name(s):
Roche COBAS INTEGRA Phenobarbital assay
2. Predicate K number(s):
k951595
3. Comparison with predicate:
{2}
| Similarities | | |
| --- | --- | --- |
| Item | Device | Predicate |
| Intended use | Quantitative measurement of phenobarbital | Same |
| Matrix | Serum or plasma | Same |
| Storage | 2-8 C | 2-8 C |
| Differences | | |
| --- | --- | --- |
| Item | Device | Predicate |
| Measuring range | 2.4 – 60 μg/mL | 0.6-60 μg/mL |
| Methodology | Homogeneous enzyme immunoassay | Fluorescence polarization |
| Instrumentation | Roche/Hitachi 912, 917 and Modular P | Roche COBAS Integra |
# K. Standard/Guidance Document Referenced (if applicable):
Guidance for Industry and FDA Staff; Replacement Reagent and Instrument Family Policy http://www.fda.gov/cdrh/oivd/guidance/950.
# L. Test Principle:
The assay is based on the kinetic interaction of microparticles in a solution (KIMS). Phenobarbital antibody is covalently coupled to microparticles and the drug derivative is linked to a macromolecule. The kinetic interaction of microparticles in solutions is induced by binding of drug-conjugate to the antibody on the microparticles and is inhibited by the presence of phenobarbital in the sample. A competitive reaction takes place between the drug conjugate and phenobarbital in the serum sample for binding to the phenobarbital antibody on the microparticles. The resulting kinetic interaction of microparticles is indirectly proportional to the amount of drug present in the sample.
# M. Performance Characteristics (if/when applicable):
# 1. Analytical performance:
All of the performance characteristics for this submission were conducted on the Roche Hitachi 917.
# a. Precision/Reproducibility:
Within-run precision was conducted by running three levels of control (low, mid and high controls) and two levels of human serum pools (low and high) 21 times on the Hitachi 917. The sponsor acceptance criteria for an observed within run precision no greater than a standard deviation of 0.75, up to a concentration of $15\mathrm{mg / mL}$ , or CV of less than $5\%$ at higher concentrations.
{3}
| Material | TDM I | TDM II | TDM III | HSP 1 | HSP 2 |
| --- | --- | --- | --- | --- | --- |
| Concentration | 9.13 | 23.30 | 44.40 | ~15 | ~35 |
| Mean | 9.80 | 24.34 | 45.21 | 15.66 | 38.18 |
| SD | 0.14 | 0.33 | 0.27 | 0.15 | 0.34 |
| CV% | 1.4 | 1.4 | 0.6 | 0.9 | 0.9 |
| Min | 9.64 | 23.90 | 44.68 | 15.40 | 37.33 |
| Max | 10.24 | 25.23 | 45.74 | 15.94 | 38.87 |
Between-day precision was assessed conducted by running three levels of control (low, mid and high controls) and two levels of human serum pools (low and high) for 21 days on the Hitachi 917. The sponsor acceptance criteria was that the within run precision observed should be no greater than a standard deviation of 0.9, up to a concentration of $15\mu \mathrm{g / mL}$ , or CV less than $7\%$ at higher concentration. The total and between-day run precision observed should be no greater than a standard deviation of 0.9, up to a concentration of $15\mu \mathrm{g / mL}$ , or CV less than $7\%$ at higher concentration.
| Specimen | TDM I | TDM II | TDM III | HSP 1 | HSP 2 |
| --- | --- | --- | --- | --- | --- |
| Total Mean | 9.62 | 24.09 | 45.24 | 15.39 | 37.59 |
| Within Run Imprecision SD | 0.125 | 0.180 | 0.369 | 0.149 | 0.336 |
| Within Run Imprecision CV% | 1.3 | 0.7 | 0.8 | 1.0 | 0.9 |
| Total Imprecision SD | 0.338 | 0.586 | 0.822 | 0.432 | 0.760 |
| Total Imprecision CV% | 3.5 | 2.4 | 1.8 | 2.8 | 2.0 |
| Between-day Imprecision SD | 0.315 | 0.558 | 0.735 | 0.406 | 0.682 |
| Between-day Imprecision CV% | 3.3 | 2.3 | 1.6 | 2.6 | 1.8 |
# b. Linearity/assay reportable range:
Linearity was assessed via an 11-level dilution series that were prepared using a phenobarbital spiked human serum pool diluted with a non-spiked serum pool on the Hitachi 917. Recovery was determined by comparison of the measured value to the theoretical value. The theoretical values were calculated according to the dilution factors. The sponsor's acceptance criteria were recovery within $+/-10\%$ recovery or less than $1.7~\mu \mathrm{g / mL}$ difference between the observed and theoretical concentrations up to $60~\mu \mathrm{g / mL}$ . The samples were measured in triplicate. The recoveries for the lower assay range
{4}
were 89.39% to 113.75% for samples at 2.44 µg/mL to 2.67 µg/mL. The recoveries were 91.3% to 104.8% from for samples ranging from 7.5 µg/mL to 72.9 µg/mL.
The sponsor conducted a sample dilution study with the calibrator A diluent that is recommended in the package insert. The samples (55.95- 10.97 µg/mL) were diluted in a 1:1 ratio and the diluted sample value was multiplied by two and compared to the pre-diluted sample value. The recovery results ranged from 95 to 104%. The assay range for the ONLINE TDM phenobarbital assay is 2.4 - 60 µg/mL. The sponsor's recovery acceptance criterion is +/- 10%. The package insert instructs the users to manually dilute samples that fall outside the assay range.
c. Traceability, Stability, Expected values (controls, calibrators, or methods):
The already cleared Preciset TDM I Calibrators (k031856) are prepared to contain known quantities of phenobarbital in normal human serum and are traceable to USP reference standards. These calibrators are used to establish a standard curve from which the quantity of unknown specimens can be determined. The previously cleared Preciset TDM calibrators are not included with the device but are suggested in the package insert.
d. Detection limit:
To determine the lower detection limit (LDL), twenty one replicates of the zero calibrator and five replicates of calibrator b (5.0 µg/mL) were assayed in a single run on the Hitachi 917. The observed LDL with zero calibrator is 0.15 µg/mL at 2 SD. The LDL was within the sponsor's acceptable limits of less than 1.7 µg/mL.
To determine the functional sensitivity, 7 clinical samples having concentrations between zero and twice the LDL were assayed in triplicate daily for ten days on the same instrument on the Hitachi 917. The acceptance criterion for functional sensitivity was calculated as the lowest concentration from clinical samples with a CV of less than 20%. The observed functional sensitivity on the Hitachi 917 is 1.44 µg/mL.
e. Analytical specificity:
The sponsor tested common substances and biological materials for interference with the phenobarbital assay at a concentration of 15 µg/mL in drug positive samples on the Hitachi 917. Spiked samples containing the interferent substances were run in triplicates in a recovery study. The sponsor states that there were no deviations from the expected results and all drug interferences passed with 10% of the referenced values.
5
{5}
Cross-reactivity was assessed by spiking cross-reactants into serum pools that contained approximately $15~\mu \mathrm{g / mL}$ phenobarbital. The sponsor definitions are:
| Cross-reactivity equation | If Da-Dt < LDL claim, then ND (Not Detectable) If Da-Dt > LDL claim, then the cross-reactivity is calculated as follows: % Cross-Reactivity = [(Da-Dt)/ C] x 100 Dt = Concentration of Control Analyte Spike in serum Da = Concentration of (Analyte + Cross-Reactant) C = Concentration of Cross-Reactant |
| --- | --- |
Cross reactivity was ND for all of the following compounds except Butabarbital (0.15%), Mephobarbital (0.18%), Secobarbital (0.15%) and Butalbital (0.67%) and are placed in the package insert.
| Compounds | Concentration Tested | % Cross-reactivity |
| --- | --- | --- |
| Amobarbital | 1000 | ND |
| Aprobarbital | 1000 | ND |
| Butabarbital | 1000 | 0.15 |
| 5,5 Diallybarbituric acid | 1000 | ND |
| Mephobarbital | 1000 | 0.18 |
| Secobarbital | 1000 | 0.15 |
| Acetylsalicylic acid | 1000 | ND |
| Amitriptyline | 9 | ND |
| Barbital | 1000 | ND |
| Butalbital | 1000 | 0.67 |
| Caffeine | 1000 | ND |
| Carbamazepine | 1000 | ND |
| Carbamazepine-10,11-epoxide | 140 | ND |
| Chlordiazepoxide | 30 | ND |
| Chlorpromazine | 50 | ND |
| Clonazepam | 1.2 | ND |
| Diazepam | 25 | ND |
| Ethosuximide | 1000 | ND |
| Glutethimide | 1000 | ND |
| Hexobarbital | 1000 | ND |
| 5-(p-Hydroxyphenyl)-5-phenylhydantoin | 1000 | ND |
| Imipramine | 5 | ND |
| Meperidine -HCl | 100 | ND |
| Mephenytoin | 1000 | ND |
| Methsuximide | 400 | ND |
| Methyprylon | 1200 | ND |
| Nitrazepam | 0.6 | ND |
{6}
| Nordiazepam | 100 | ND |
| --- | --- | --- |
| Pentobarbital -Na | 1000 | ND |
| Phensuximide | 1000 | ND |
| Phenylbutazone | 2500 | ND |
| 2-Phenyl-2-ethylmalon-amide (PEMA) | 1000 | ND |
| Phenytoin | 1000 | ND |
| P-Hydroxyphenobarbital | 200 | ND |
| Primidone | 120 | ND |
| Promethazine | 0.23 | ND |
| Theophylline | 200 | ND |
| Thiopental -Na | 1000 | ND |
| Valproic acid | 1000 | ND |
The sponsor also conducted an interference study to evaluate the effects of bilirubin, hemolysis, lipemia, triglycerides, total protein, HAMA, heterophilic antibodies and rheumatoid factor with their phenobarbital assay on the Hitachi 917. The sponsor claims no interference with either assay as their recovery results met their acceptance criteria of $+/- 10\%$ of the initial value. There was no significant interference for conjugated and unconjugated bilirubin up to 66 mg/dL, hemolysis up to 1000 mg/dL, lipemia up to 600, triglycerides up to 1000 mg/dL, proteins between 2-14 g/dL, no HAMA interference and rheumatoid factors up to 200 IU/mL.
f. Assay cut-off:
Not applicable
# 2. Comparison studies:
a. Method comparison with predicate device:
The ONLINE TDM Phenobarbital assay for the Roche/Hitachi 917 analyzer (y) was compared to the COBAS FP Phenobarbital on the BOBAS Integra 700 analyzer (x). Fifty-three non pooled human samples that ranged from 3.0-52.4 ug/mL were assayed and Passing-Bablok and linear regression was calculated and the results are located below.
| | Passing Bablok | Linear Regression |
| --- | --- | --- |
| Slope | 1.042 | 1.047 |
| Intercept | -0.215 | -0.339 |
| Correlation | Tau= 0.955 | R=0.996 |
{7}
b. Matrix comparison:
Plasma pairs were obtained from an in-house blood draw and samples processed according to labeling requirements for each tube. All individuals donating were Phenobarbital and related analyte free. The recoveries for ½ K2 EDTA, K2 EDTA, K2 EDTA ½, ½ K3 EDTA, K3 EDTA, K3 EDTA ½, ½ Lithium Heparin, Lithium Heparin, Lithium Heparin ½, Lithium, ½ Sodium Heparin, Sodium Heparin, Sodium heparin ½ and its serum equivalent were calculated and the results are shown in the table below.
| Anticoagulant | Sample Range (μg/mL) | n | Recovery range % |
| --- | --- | --- | --- |
| ½ K2 EDTA | 4.18-54.25 | 13 | 94- 105 |
| K2 EDTA | 4.18-60.54 | 47 | 90-101 |
| ½ K3 EDTA | 10.46-54.07 | 13 | 95-105 |
| K3 EDTA | 4.18-60.54 | 49 | 91-105 |
| ½ Lithium Heparin | 13.38-60.54 | 13 | 96-103 |
| Lithium Heparin | 13.38-60.54 | 10 | 97-103 |
| Lithium | 20.9-59.3 | 7 | 96-109 |
| ½ Sodium Heparin | 7.76-58.79 | 14 | 90-110 |
| Sodium Heparin | 7.76-58.76 | 19 | 93-107 |
3. Clinical studies:
a. Clinical Sensitivity:
Not applicable.
b. Clinical specificity:
Not applicable.
c. Other clinical supportive data (when a. and b. are not applicable):
Not applicable.
4. Clinical cut-off:
Not applicable.
5. Expected values/Reference range:
The sponsor has referenced the following expected values in the package insert.
{8}
"The therapeutic range of phenobarbital is correlated with seizure control as well as the absence of toxic effects, and is generally accepted to be between 10 and 30 ug/mL. Variation in metabolism and absorption of the drug may cause levels to rise above 40 µg/mL or fall below 15 µg/mL. The most frequent dose-related side effect is sedation, to which a tolerance usually develops. Phenobarbital serum levels above 40 µg/mL are often associated with nystagmus, atazia and dysarthria. At high doses, phenobarbital can even cause an increase in seizure frequency. Each laboratory should investigate the transferability of the expected values to its own patient population and if necessary determine its own reference ranges."
Kutt H., Penry JK. Usefulness of blood levels of anti-epileptic drugs. Arch Neurol. 1974; 31:283-288.
Morselli PL. Antiepileptic Drugs in Drug Disposition During Development. Morselli PL, ed. New York, NY: Spectrum. 1971;311-360.
## 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 a substantial equivalence decision.
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.