K151639 · Sendx Medical, Inc. · CGA · Dec 7, 2015 · Clinical Chemistry
Device Facts
Record ID
K151639
Device Name
ABL80 FLEX and ABL80 FLEX CO-OX
Applicant
Sendx Medical, Inc.
Product Code
CGA · Clinical Chemistry
Decision Date
Dec 7, 2015
Decision
SESE
Submission Type
Traditional
Regulation
21 CFR 862.1345
Device Class
Class 2
Indications for Use
The ABL80 FLEX analyzer is a portable, automated analyzer that measures glucose, in whole blood. The ABL80 FLEX analyzer system is intended for use by trained technologists, nurses, physicians and therapists. It is intended for use in a laboratory environment, near patient or point-of-care setting. The ABL80 FLEX CO-OX analyzer is a portable, automated analyzer that measures glucose, in whole blood. The ABL80 FLEX CO-OX analyzer system is intended for use by trained technologists, nurses, physicians and therapists. It is intended for use in a laboratory environment, near patient or point-of-care setting. For in vitro diagnostic use.
Device Story
Portable, automated analyzers (ABL80 FLEX/ABL80 FLEX CO-OX) measure whole blood glucose via amperometric sensing; requires oxygen for enzymatic glucose conversion. Device monitors sample pO2 levels simultaneously; software automatically suppresses/flags glucose results when pO2 is insufficient for accurate measurement. Used in laboratory or point-of-care settings by trained clinicians. Output provided to clinicians for diagnostic decision-making. Modification ensures reporting limitations based on pO2-dependent glucose linearity ranges (36-180 mg/dL for pO2 20-40 mmHg; 36-270 mg/dL for pO2 ≥41 mmHg).
Clinical Evidence
No clinical data. Bench testing only. Interference study performed per CLSI EP7-A2 using whole blood samples tonometered to varying pO2 levels (control 100 mmHg vs. test levels). Bias calculated against control; acceptance criterion ≤10%. Results confirmed glucose measurement dependency on pO2, establishing validated linearity ranges.
Technological Characteristics
Portable, automated analyzer; amperometric sensing principle; two-point liquid calibration; sensor cassette and solution pack accessories; software-controlled parameter reporting based on pO2 levels.
Indications for Use
Indicated for trained technologists, nurses, physicians, and therapists to measure whole blood glucose in laboratory or 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 ONLY TEMPLATE
A. 510(k) Number:
k151639
B. Purpose for Submission:
To modify the software to incorporate limitations of reporting glucose results when pO₂ value is low.
C. Measurand:
Whole Blood Glucose
D. Type of Test:
Amperometric Test
E. Applicant:
SenDx Medical, Inc.
F. Proprietary and Established Names:
ABL80 FLEX and ABL80 FLEX CO-OX
G. Regulatory Information:
1. Regulation section:
862.1345
2. Classification:
Class II
3. Product code:
CGA
{1}
4. Panel:
Clinical Chemistry
H. Intended Use:
1. Intended use(s):
See indications for use below
2. Indication(s) for use:
The ABL80 FLEX analyzer is a portable, automated analyzer that measures glucose, in whole blood. The ABL80 FLEX analyzer system is intended for use by trained technologists, nurses, physicians and therapists. It is intended for use in a laboratory environment, near patient or point-of-care setting.
The ABL80 FLEX CO-OX analyzer is a portable, automated analyzer that measures glucose, in whole blood. The ABL80 FLEX CO-OX analyzer system is intended for use by trained technologists, nurses, physicians and therapists. It is intended for use in a laboratory environment, near patient or point-of-care setting.
For in vitro diagnostic use.
3. Special conditions for use statement(s):
For prescription use only
4. Special instrument requirements:
ABL80 FLEX and ABL80 FLEX CO-OX Analyzers
I. Device Description:
The ABL80 FLEX and ABL80 FLEX CO-OX analyzers are portable, automated systems intended for in vitro testing of samples of whole blood for the parameters pH, pO₂, pCO₂, potassium, sodium, calcium, chloride, glucose, hematocrit (ABL80 FLEX analyzer only) and the oximetry parameters (ABL80 FLEX CO-OX only) total hemoglobin, oxygen saturation, FO₂Hb, FCOHb, FMetHb, and FHHb.
The ABL80 FLEX and ABL80 FLEX CO-OX analyzers each exist in two different software configurations differing in the number of parameters available.
The ABL80 FLEX and ABL80 FLEX CO-OX analyzers consist of an instrument with a sensor cassette and a solution pack as the main accessories. Multiple models of sensor cassettes are available. The various sensor cassette models include models for different
2
{2}
parameter combinations. For each parameter combination, models allowing for different test loads are available. The solution pack is available in four models, one model for each of the four different configurations of the analyzer.
The ABL80 FLEX and ABL80 FLEX CO-OX analyzers were previously cleared in k051804 and k080370. The current modification to the glucose measurement software is to automatically handle certain glucose results depending on the $\mathrm{pO}_2$ value in the sample. This will allow incorporating limitations of reporting glucose results when the $\mathrm{pO}_2$ value of the sample is low.
# J. Substantial Equivalence Information:
1. Predicate device name(s): ABL800 FLEX
2. Predicate 510(k) number(s): k043218
3. Comparison with predicate:
| Item | Candidate Device ABL80 FLEX and ABL80 FLEX CO-OX | Predicate ABL800 FLEX (k043218) |
| --- | --- | --- |
| Intended Use | The ABL80 FLEX and ABL80 FLEX CO-OX analyzers are portable, automated analyzer that measures glucose in whole blood. | Same, plus the following parameters: pH, pO2, pCO2, potassium, sodium, calcium, chloride, glucose, lactate, total bilirubin, and co-oximetry parameters (total hemoglobin, oxygen saturation, and the hemoglobin fractions FO2Hb, FCOHb, FMetHb, FHHb and FHbF) |
| Intended Use Site | Laboratory and Point of Care | Laboratory |
| Measuring Method | Amperometric | Same |
| Calibration Method | Two-point liquid calibration | Same |
| Glucose measuring range | 36-180 mg/dL (pO2 between 20 - 40 mmHg); 36-270 mg/dL (pO2 ≥ 41 mmHg). | 36-270 mg/dL |
{3}
4
K. Standard/Guidance Document Referenced (if applicable):
CLSI EP7-A2: Interference testing in clinical chemistry; Approved Guideline – Second Edition (2005).
CSLI EP05-A2: Evaluation of Precision Performance of Quantitative Measurement Methods; Approved Guideline – Second Edition (2004).
CSLI EP6-A: Evaluation of the Linearity of Quantitative Measurement Procedures: A Statistical Approach; Approved Guideline (2003).
CLSI EP09-A3: Measurement procedure comparison and bias estimation using patient samples; Approved Guideline - Third Edition (2013).
CLSI EP17-A2: Evaluation of Detection Capability for Clinical Laboratory Measurement Procedures; Approved Guideline – Second Edition (2012).
L. Test Principle:
The amperometric test principle is used for the measurement of both pO₂ and glucose because glucose measurement is dependent upon enough pO₂ in the sample; therefore, pO₂ and glucose are measured simultaneously. The magnitude of an electric flow of current is proportional to the concentration of the substance being oxidized or reduced at an electrode.
M. Performance Characteristics (if/when applicable):
1. Analytical performance:
a. Precision/Reproducibility:
See k051804 and k080370.
b. Linearity/assay reportable range:
See k051804 and k080370.
c. Traceability, Stability, Expected values (controls, calibrators, or methods):
See k051804 and k080370.
d. Detection limit:
See k051804 and k080370.
e. Analytical specificity:
{4}
Analytical Specificity for glucose measurement was reviewed and cleared in k051804 and k080370. However, additional studies were conducted to further characterize the impact of, or interference from, limitations on the amounts of oxygen in the sample. The cause of this interference effect is that the enzymatic conversion of glucose in the sensor is oxygen consuming, the oxygen coming from the sample. The interference study was performed according to the CLSI "Interference testing in clinical chemistry; Approved Guideline - Second Edition", CLSI document EP7-A2. Testing was performed on three ABL80 FLEX and three ABL80 FLEX CO-OX instruments with five levels of glucose and four levels of $\mathsf{pO}_2$ . Base pools of whole blood were prepared for each glucose level and split into two samples with one being tonometered to $100\mathrm{mmHg}$ $\mathsf{pO}_2$ (control sample) and the other to the $\mathsf{pO}_2$ level being tested (test sample). Each sample was tested on the ABL80 FLEX and ABL80 FLEX CO-OX analyzers, and the glucose bias for each test sample vs. the control sample was calculated. The bias for the test sample was calculated and should be less than or equal to the acceptance criterion which was set to $10\%$ of the control value. Results are summarized below:
ABL80 FLEX:
| Glucose Concentration (mg/dL) | pO2mmHg | | | |
| --- | --- | --- | --- | --- |
| | < 20 | 20 | 40 | 80 |
| 270 | -67% | -17% | -5% | 1% |
| 180 | -51% | -3% | 9% | -1% |
| 90 | -37% | -7% | -6% | 0% |
| 54 | -26% | -10% | 6% | 1% |
| 36 | Not needed | -7% | -4% | 2% |
ABL80 FLEX CO-OX:
| Glucose Concentration (mg/dL) | pO2mmHg | | | |
| --- | --- | --- | --- | --- |
| | < 20 | 20 | 40 | 80 |
| 270 | -69% | -20% | 3% | 0% |
| 180 | -55% | -4% | 8% | 0% |
| 90 | -42% | -8% | -7% | -2% |
| 54 | -31% | -9% | 6% | 0% |
| 36 | Not needed | -9% | -4% | 2% |
The interference study test results support the glucose linearity ranges shown below and documented in the labeling:
Glucose linearity versus $\mathsf{pO}_2$ level
| pO2(mmHg) range | Glucose concentration (mg/dL) linearity range |
| --- | --- |
| 20 – 40 | 36 – 180 |
| ≥ 41 | 36 – 270 |
{5}
The labeling (reference manual and owner's manual) highlights awareness of dependency of glucose measurement on sample pO₂ levels and includes the following description for flagging glucose results outside the validated glucose linear range and the pO₂ level of the sample:
- All glucose results at pO₂ level <20 mmHg are suppressed and flagged by the symbol “>” with a message “Glu not usable. pO₂ too low for reliable cGlucose measurement”.
- All glucose results >180 mg/dL at pO₂ level between 20 – 40 mmHg will be suppressed and flagged by the symbol “>” with a message “Glu not usable. pO₂ too low for reliable cGlucose measurement”.
- When the measured value of pO₂ is not numeric (Not Reportable (N/R)) or pO₂ parameter is Lockout (P/L) or Not Derived (N/D) or Inactive (I/A) or QC Lockout (L/O), then the results for glucose measurement will not be displayed and the symbol “N/R” is displayed.
- If the results are outside the test range of the analyzer for glucose measurement (see table above), the results are highlighted in red and flagged with “↑” or “↓”.
f. Assay cut-off:
Not applicable
2. Comparison studies:
a. Method comparison with predicate device:
See k051804 and k080370.
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
{6}
4. Clinical cut-off:
Not applicable
5. Expected values/Reference range:
The glucose reference range for adults' arterial blood at 37 °C is 70.02 – 104.9 mg/dL (3.89 – 5.83 mmol/L)
Reference: Tietz NW, Logan NM. Reference ranges. In: Tietz NW, ed. Fundamentals of clinical chemistry. 3rd ed. Philadelphia: WB Saunders Company, 1987: 944-75.
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.
7
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.
