The cobas 8000 ISE module is a fully automated ion-specific analyzer intended for the in vitro potentiometric determination of chloride, potassium, and sodium in serum, plasma, and urine using ion-selective electrodes. Measurements obtained by this device are used in the diagnosis and treatment of diseases or conditions involving electrolyte imbalance.
Device Story
The cobas 8000 ISE module is a fully automated clinical chemistry analyzer component; it utilizes ion-selective electrodes (ISE) to measure sodium, potassium, and chloride concentrations in serum, plasma, and urine. The system operates by measuring the electrical potential (electromotive force, EMF) generated across selective membrane materials in contact with test and internal filling solutions; the EMF difference correlates to ion concentration via the Nernst equation. The device is operated by laboratory personnel in clinical settings. Output is provided as quantitative electrolyte concentrations, which clinicians use to diagnose and manage conditions related to electrolyte imbalance. This submission specifically expands the sample type capability to include urine.
Clinical Evidence
Bench testing only. Precision studies (within-run and total) performed using human urine and controls. Linearity validated across reportable ranges (Sodium 60-350, Potassium 3-100, Chloride 60-350 mmol/L). Method comparison against predicate (n=100 for Na/K, n=59 for Cl) showed high correlation (r ≥ 0.999). Interference studies confirmed no significant impact from common drugs, pH, or protein; hemolysis noted to interfere with potassium at >400 mg/dL in normal urine.
Technological Characteristics
Quantitative indirect potentiometric measurement using ion-selective electrodes. System includes sodium, potassium, chloride, and reference electrodes with open liquid junction membranes. Automated 1:46 sample dilution. Operates as a module within the cobas 8000 Modular Analyzer Series. Traceable to flame photometry and coulometry. Standards: CLSI EP5-A2, EP6-A, EP17-A.
Indications for Use
Indicated for in vitro potentiometric determination of sodium, potassium, and chloride in serum, plasma, and urine for patients requiring diagnosis or treatment of electrolyte imbalance.
Regulatory Classification
Identification
A sodium test system is a device intended to measure sodium in serum, plasma, and urine. Measurements obtained by this device are used in the diagnosis and treatment of aldosteronism (excessive secretion of the hormone aldosterone), diabetes insipidus (chronic excretion of large amounts of dilute urine, accompanied by extreme thirst), adrenal hypertension, Addison's disease (caused by destruction of the adrenal glands), dehydration, inappropriate antidiuretic hormone secretion, or other diseases involving electrolyte imbalance.
Predicate Devices
COBAS INTEGRA ISE System (k963627)
Submission Summary (Full Text)
{0}
1
# 510(k) SUBSTANTIAL EQUIVALENCE DETERMINATION DECISION SUMMARY ASSAY ONLY TEMPLATE
A. 510(k) Number:
k123726
B. Purpose for Submission:
Addition of urine sample type to the already cleared device (k100853)
C. Measurand:
Sodium, Potassium, and Chloride
D. Type of Test:
Quantitative, indirect potentiometric measurement with ion-selective electrodes
E. Applicant:
Roche Diagnostics
F. Proprietary and Established Names:
cobas 8000 ISE Indirect Na, K, Cl for Gen. 2.
G. Regulatory Information:
1. Regulation section:
21CFR 862.1665: Ion Specific Electrode, Sodium
21CFR 862.1600: Ion Specific Electrode, Potassium
21CFR 862.1170: Ion Specific Electrode, Chloride
2. Classification:
Class II
3. Product code:
JGS
CEM
CGZ
4. Panel:
75 (Clinical Chemistry)
H. Intended Use:
1. Intended use(s):
See Indication(s) for use below.
{1}
2. Indication(s) for use:
The cobas 8000 ISE module is a fully automated ion-specific analyzer intended for the in vitro potentiometric determination of chloride, potassium, and sodium in serum, plasma, and urine using ion-selective electrodes. Measurements obtained by this device are used in the diagnosis and treatment of diseases or conditions involving electrolyte imbalance.
3. Special conditions for use statement(s):
For in vitro diagnostic use only.
For prescription use.
4. Special instrument requirements:
cobas 8000 ISE Modular Analyzer
I. Device Description:
The cobas 8000 Modular Analyzer Series is a fully automated system for clinical chemistry analysis intended for the in vitro quantitative/qualitative determination of analytes in body fluids. It is optimized for high throughput workloads using a combination of ion selective electrodes (cobas 8000 ISE module) and photometric analysis modules (cobas c 701 and c 502 modules). The cobas 8000 ISE module and the ISE Gen 2 reagents were previously cleared for serum and plasma sample types under k100853. The ISE module includes a sodium electrode, a chloride electrode, a potassium electrode, a reference electrode, an ISE diluent, an ISE internal standard, an ISE reference electrolyte, an ISE calibrator and an ISE Compensator (calibrator). The ISE standard calibrators (S1, S2, and S3) were cleared under k053165 and ISE Compensator cleared under k052193.
J. Substantial Equivalence Information:
1. Predicate device name(s):
COBAS INTEGRA ISE System
2. Predicate 510(k) number(s):
k963627
3. Comparison with predicate:
| Similarities and Differences | | |
| --- | --- | --- |
| Item | Predicate device COBAS INTEGRA ISE k963627 | Candidate device cobas 8000 ISE Module |
| Intended Use | The COBAS INTEGRA ISE module applications are intended | Same (only for sodium, potassium and chloride, no |
{2}
| | for use for the quantitative determination of sodium, potassium, chloride, and lithium in serum, plasma or urine using ion-selective electrodes. | lithium) |
| --- | --- | --- |
| Specimen Type | Serum, Plasma, Urine | Same |
| Measurement Principle | ISE Potentiometry | Same |
| Reagent container | Plastic bottles closed via screw caps | Same |
| Onboard storage temperature | Room Temperature | Same |
| ISE Module | Integrated into Integra analyzer | Separate ISE module connected to Core cobas 8000 module |
| Ion Selective Electrodes (ISEs) | Potentiometric chloride, potassium, sodium and reference electrodes | Same |
| Sample Dilution | 1:6 | 1:46 |
| Throughput | Max 600 tests/hour | Max 1800 tests/hour |
| Detection Limits - Chloride | Not Determined | LOB = 10 mmol/L
LOD = 10 mmol/L
LOQ = 60 mmol/L |
| Reportable Range - Chloride | 20-350 mmol/L | 60-350 mmol/L |
| Detection Limits - Potassium | Not Determined | LOB = 1 mmol/L
LOD = 1 mmol/L
LOQ = 3 mmol/L |
| Reportable Range - Potassium | 1-150 mmol/L | 3-100 mmol/L |
| Detection Limits - Sodium | Not Determined | LOB = 10 mmol/L
LOD = 10 mmol/L
LOQ = 60 mmol/L |
| Reportable Range - Sodium | 20-350 mmol/L | 60-350 mmol/L |
# K. Standard/Guidance Document Referenced (if applicable):
- CLSI EP5-A2: Evaluation of Precision Performance of Clinical Chemistry
{3}
Devices
- CLSI EP6-A: Evaluation of Linearity of Quantitative Analytical Methods
- CLSI EP17-A: Protocols for Determination of Limits of Detection
- CLSI EP17-A: Protocols for Determination of Limits of Detection
# L. Test Principle:
Sodium, Potassium and Chloride are measured using ion-selective electrodes utilizing an indirect (diluted) method where urine samples are automatically diluted at 1:46 ratio using ISE diluent. Each of the electrodes (Sodium, Potassium and Chloride) has membrane with an open liquid junction that is ion-selective. The reference electrode uses the same design of the ion-electrodes and it is exclusively used as a reference for every measurement. The difference of all voltages between the reference electrode and any ion-selective electrode is a measure for the concentration of individual ions. For every test, the voltages of both ISE internal standard and diluted sample solution are measured for each type of ions (Sodium, Potassium and Chloride). The measurement of all electrodes is performed in parallel. The resulting voltages are converted into operator readable results.
# M. Performance Characteristics (if/when applicable):
# 1. Analytical performance:
# a. Precision/Reproducibility:
Precision studies were performed using human urine samples and control material. Within-run precision was determined using 21 replicates for each sample type (3 urine samples and 2 controls) by one operator on one instrument. Total precision was determined using 3 samples (Low, Medium and High) over 21 days in 2 runs with one operator on one instrument. The following results were obtained:
Sodium
| Sodium | Within-run precision | | | Total precision | | |
| --- | --- | --- | --- | --- | --- | --- |
| | Mean mmol/L | SD mmol/L | CV % | Mean mmol/L | SD mmol/L | CV % |
| Urine low | 66.4 | 0.4 | 0.6 | 68.6 | 1.1 | 1.6 |
| Urine medium | 178.9 | 0.9 | 0.5 | 180.3 | 1.0 | 0.6 |
| Urine high | 321.7 | 0.7 | 02 | 318.0 | 2.1 | 0.7 |
| Liquichek 1 | 81.1 | 0.3 | 0.4 | 82.7 | 1.2 | 1.4 |
| Liquichek 2 | 170.6 | 0.5 | 0.3 | 171.3 | 1.0 | 0.6 |
{4}
# Potassium
| Potassium | Within-run precision | | | Total precision | | |
| --- | --- | --- | --- | --- | --- | --- |
| | Mean mmol/L | SD mmol/L | CV % | Mean mmol/L | SD mmol/L | CV % |
| Urine low | 3.65 | 0.00 | 1.2 | 3.75 | 0.06 | 1.7 |
| Urine medium | 51.10 | 0.30 | 0.6 | 49.48 | 0.65 | 1.3 |
| Urine high | 83.78 | 0.66 | 0.8 | 80.60 | 1.32 | 1.6 |
| Liquichek 1 | 32.19 | 0.19 | 0.6 | 31.32 | 0.37 | 1.2 |
| Liquichek 2 | 69.47 | 0.39 | 0.6 | 67.49 | 1.17 | 1.7 |
# Chloride
| Chloride | Within-run precision | | | Total precision | | |
| --- | --- | --- | --- | --- | --- | --- |
| | Mean mmol/L | SD mmol/L | CV % | Mean mmol/L | SD mmol/L | CV % |
| Urine low | 63.6 | 0.5 | 0.7 | 64.7 | 1.1 | 1.7 |
| Urine medium | 180.8 | 0.9 | 0.5 | 179.7 | 12 | 0.7 |
| Urine high | 341.7 | 1.1 | 0.3 | 336.5 | 3.5 | 1.0 |
| Liquichek 1 | 92.3 | 0.4 | 0.5 | 92.6 | 1.1 | 1.2 |
| Liquichek 2 | 189.6 | 0.6 | 0.3 | 187.9 | 1.6 | 0.9 |
# b. Linearity/assay reportable range:
Linearity studies were performed according to CLSI EP6-A. Dilution series of 11 concentrations were prepared using low and high human urine sample pools for each of the analytes and tested in triplicates. Linear regression summary results of the study are presented in the table below:
| Analyte | Slope | Intercept | r2 | Range Tested |
| --- | --- | --- | --- | --- |
| Sodium | 0.9914 | 3.1424 | 0.999957 | 54.6 – 368.8 |
| Potassium | 1.0389 | 0.1518 | 0.999597 | 2.9 – 101.7 |
| Chloride | 0.9425 | 2.7004 | 0.999499 | 48 – 384.5 |
{5}
The results of the study support the sponsor's claims that the urine Sodium is linear from 60 - 350 mmol/L, urine Potassium is linear from 3-100 mmol/L, and urine Chloride is linear form 60-350 mmol/L.
c. Traceability, Stability, Expected values (controls, calibrators, or methods): Aqueous ISE standard calibrators (S1, S2, and S3) were previously cleared under k053165 and ISE Compensator (calibrator) under k052193. The ISE Compensator is traceable to Flame Photometry (Sodium, Potassium) and Coulometry (Chloride).
d. Detection limit:
Studies were carried out in accordance with CLSI Guidance Document EP17-A for Sodium, Potassium and Chloride analytes. For determination of LoB one analyte free sample was measured in 5 replicates, 6 runs, 3 days, on 2 cobas 8000 ISE analyzers. Total of 60 measurements were obtained per analyzer. For determination of LoD, five samples (one replicate) with low-analyte concentration were measured in 6 runs for 3 days on 2 cobas 8000 ISE analyzer modules. In total 60 measurements were obtained per analyzer. For LoQ studies a low level sample set was prepared by diluting 3 human urine samples with an analyte free diluent (ISE Diluent). The low level sample set was tested in single replicate for 3 days in 2 runs per day on two cobas 8000 ISE analyzers. LoQ is defined as the concentration where total error is less than 20%. Results from the detection limit studies are summarized in the table below:
| | LoB (mmol/L) | LoD (mmol/L) | LOQ (mmol/L) | Claimed measuring range (mmol/L) |
| --- | --- | --- | --- | --- |
| Sodium | 10 | 10 | 60 | 60-350 |
| Potassium | 1 | 1 | 3 | 3-100 |
| Chloride | 10 | 10 | 60 | 60-350 |
e. Analytical specificity:
Urine interference studies were performed in according to CLSI EP7-A2 for sodium, potassium, and chloride analytes using 2 levels of analytes (normal and abnormal). The effect of pH (3.8 - 8.2), total protein (14 - 280 mg/L), and hemoglobin (0 - 1,000 mg/dL) on analyte recovery was evaluated in these studies. Different concentrations of potential interference substances were spiked into pooled urine samples. The sponsor's definitions of non-significant interference is <10% difference between the spiked and unspiked samples. There was no significant interference for sodium, potassium, and chloride
{6}
when these analytes and interferents were tested in the concentration ranges indicated below:
**Drug interferents:**
Acetaminophen (paracetamol) 3000 mg/L
Ascorbic acid 4000 mg/L
Ca-Dobesilate 1000 mg/L
Gentamycin sulfate 400 mg/L
Ibuprofen 4000 mg/L
L-Dopa 1000 mg/L
Methyldopa 2000 mg/L
Na-Cefoxitin 12000 mg/L
N-Acetylcysteine 10 mg/L
Ofloxacine 900 mg/L
Phenazopyridine 300 mg/L
Salicyluric acid 6000 mg/L
Tetracycline (Doxycycline) 300 mg/L
**Hemolysis:**
**Sodium and Chloride**
Hemoglobin in urine samples does not interfere in the tested concentration range up to 1000 mg/dL (621 umol/L) hemoglobin (approximate H index 1000).
**Potassium**
Hemoglobin levels higher than 400 mg/dL in normal human urine samples increase the apparent potassium concentrations significantly.
Hemoglobin in pathological urine samples does not interfere in the tested concentration range up to 1000 mg/dl (621 umol/L).
Avoid hemolyzed specimens.
**Icterus:**
Bilirubin (conjugated) in urine samples does not interfere in the tested concentration range up to 60 mg/dl (1026 umol/L) bilirubin (approximate I index 60).
| Sample | pH | Sodium | | Potassium | | Chloride | |
| --- | --- | --- | --- | --- | --- | --- | --- |
| | | Result (mmol/L) | % of Reference | Result (mmol/L) | % of Reference | Result (mmol/L) | % of Reference |
| Reference | 6 | 74.4 | - | 27.32 | - | 70.0 | - |
| Acidic | 3.8 | 74.2 | 99.7 | 26.77 | 97.99 | 72.6 | 103.7 |
| Alkaline | 8.2 | 74.8 | 100.5 | 26.95 | 98.65 | 67.3 | 96.1 |
f. Assay cut-off: Not applicable
{7}
8
2. Comparison studies:
a. Method comparison with predicate device:
Method comparison studies were conducted for sodium, potassium and chloride on the candidate device (cobas 8000 ISE module) (y) and the results were compared to those determined with the predicate device analyzer (x). The lowest concentration and the highest concentration are diluted and spiked in order to cover hard-to-find sample range for each analyte. Results from the method comparison studies are summarized in tables below:
Sodium
| Instruments | No. Samples | Range Tested (mmol/L) | Passing Bablok | R |
| --- | --- | --- | --- | --- |
| x:cobas INTEGRA ISE
y:cobas 8000 ISE | 100 | 62.2 – 340 | y = 1.041x – 4.477 | 1.000 |
Potassium
| Instruments | No. Samples | Range Tested (mmol/L) | Passing Bablok | R |
| --- | --- | --- | --- | --- |
| x:cobas INTEGRA ISE
y:cobas 8000 ISE | 100 | 3.4 – 100 | y = 0.937x + 0.429 | 1.000 |
Chloride
| Instruments | No. Samples | Range Tested (mmol/L) | Passing Bablok | R |
| --- | --- | --- | --- | --- |
| x:cobas INTEGRA ISE
y:cobas 8000 ISE | 59 | 61.1 – 344.3 | y = 0.971x – 2.787 | 0.999 |
b. Matrix comparison:
Not applicable
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
{8}
4. Clinical cut-off:
Not Applicable
5. Expected values¹/Reference range:
The expected values for adult based on 24 hours urine out-put are cited from the literature:
Na+ 40-220 mmol/24 h
K+ 25-125 mmol/24 h
Cl- 110-250 mmol/24 h
References:
1. Tietz Fundamentals of Clinical Chemistry, Fifth Edition, Edited by Carl A. Burtis and Edward R. Ashwood, W.B. Saunders Company, 2001: 970, 1004, 1009 (ISBN 0-7216-8634-6).
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.
9
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.