GLUCOSE REAGENT FOR BECKMAN SYNCHRON CX & CX DELTA SYSTEMS
K033055 · Diamond Diagnostics, Inc. · CGA · Jan 30, 2004 · Clinical Chemistry
Device Facts
Record ID
K033055
Device Name
GLUCOSE REAGENT FOR BECKMAN SYNCHRON CX & CX DELTA SYSTEMS
Applicant
Diamond Diagnostics, Inc.
Product Code
CGA · Clinical Chemistry
Decision Date
Jan 30, 2004
Decision
SESE
Submission Type
Traditional
Regulation
21 CFR 862.1345
Device Class
Class 2
Attributes
Pediatric
Indications for Use
Mission Glucose Reagent is intended for the quantitative determination of glucose in serum, plasma, cerebrospinal fluid (CSF), and urine on the Beckman Synchron CX® & CX® Delta Systems. Glucose measurements are used in the diagnosis and treatment of carbohydrate metabolism disorders including diabetes mellitus, neonatal hypoglycemia, idiopathic hypoglycemia, and pancreatic islet cell carcinoma.
Device Story
Reagent for quantitative glucose determination in serum, plasma, CSF, and urine; used on Beckman Synchron CX® and CX® Delta systems. Operates via oxygen rate method; Beckman oxygen electrode measures rate of oxygen consumption, which is directly proportional to glucose concentration in sample. Used in clinical laboratory settings by trained personnel. Output is a numerical glucose value (mg/dL) displayed by the host instrument. Healthcare providers use results to diagnose and manage carbohydrate metabolism disorders. Benefits include accurate glucose monitoring for clinical decision-making.
Clinical Evidence
No clinical studies were performed. Evidence is based on bench testing, including precision/reproducibility (N=18 to 80 per sample type), linearity (0.6–25 mmol/L), and method comparison against the predicate. Method comparison studies (N=50 serum, 57 urine, 36 CSF) showed high correlation (r² ≥ 0.997) and regression slopes near 1.0. Functional sensitivity is 10 mg/dL (CV < 20%).
Technological Characteristics
Quantitative electrochemical assay; oxygen rate method using an oxygen electrode. Reagent composition: 590 U/mL glucose oxidase, 10% denatured alcohol, 0.04 mol/L potassium iodide, buffers, ammonium molybdate, and preservatives. Form factor: 500 mL liquid reagent. Designed for use with Beckman Synchron CX®/CX® Delta Systems. Complies with NCCLS EP5-A and EP9-A2 guidance.
Indications for Use
Indicated for quantitative glucose determination in serum, plasma, CSF, and urine for patients with carbohydrate metabolism disorders, including diabetes mellitus, neonatal hypoglycemia, idiopathic hypoglycemia, and pancreatic islet cell carcinoma.
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}
510(k) SUBSTANTIAL EQUIVALENCE DETERMINATION
DECISION SUMMARY
DEVICE ONLY TEMPLATE
A. 510(k) Number:
k033055
B. Analyte:
Glucose
C. Type of Test:
Quantitative electrochemical assay
D. Applicant:
Diamond Diagnostics / Mission Diagnostics
E. Proprietary and Established Names:
Mission Diagnostic Glucose Reagent for Beckman Synchron CX® & CX® Delta Systems
F. Regulatory Information:
1. Regulation section:
21 CFR § 862.1345, Glucose Test System
2. Classification:
Class II
3. Product Code:
CGA, glucose oxidase glucose test system
4. Panel:
Clinical Chemistry (75)
G. Intended Use:
1. Indication(s) for use:
Mission Glucose Reagent is intended for the quantitative determination of glucose in serum, plasma, cerebrospinal fluid (CSF), and urine on the Beckman Synchron CX® & CX® Delta Systems.
Glucose measurements are used in the diagnosis and treatment of carbohydrate metabolism disorders including diabetes mellitus, neonatal hypoglycemia, idiopathic hypoglycemia, and pancreatic islet cell carcinoma.
2. Special condition for use statement(s):
Intended to serve as a direct replacement to like-named products manufactured by the Original Equipment Manufacturer (OEM).
{1}
Page 2 of 6
3. Special instrument Requirements:
Beckman Synchron CX® & CX® Delta Systems
H. Device Description:
The Mission Diagnostic Glucose Reagent for Beckman Synchron CX® & CX® Delta Systems is a reagent for use with the Beckman Synchron CX® & CX® Delta Systems. The reagent is packaged in 500 mL quantities, and contains 590 U/mL glucose oxidase, 10% denatured alcohol, 0.04 mol/L potassium iodide, buffers, ammonium molybdate, and preservatives.
I. Substantial Equivalence Information:
1. Predicate device name(s):
Beckman PN 443355
2. Predicate K number(s):
K942676, K864236
3. Comparison with predicate:
This reagent is intended to be a secondary reagent. The device and its predicate have the same intended use, composition, packaging quantities and dimensions, storage conditions, and shelf life.
J. Standard/Guidance Document Referenced (if applicable):
NCCLS Guidance document EP5A, Evaluation of Precision Performance of Clinical Chemistry Devices
NCCLS Guidance document EP9A2, Method Comparison and Bias Estimation Using Patient Samples
K. Test Principle:
Glucose concentration is determined by an oxygen rate method employing an oxygen Electrode. Electronic circuits determine the rate of oxygen consumption, which is directly proportional to the concentration of glucose in the sample.
L. Performance Characteristics (if/when applicable):
1. Analytical performance:
a. Precision/Reproducibility
Within run precision was measured by assaying serum and urine controls in triplicate 6 times to lead to N = 18 (CSF, N = 15). Total precision included samples run in triplicate 2 to 5 runs per day for 4 days (N = 51 serum, 35 urine, 32 CSF). Results are summarized below:
{2}
| Sample | Mean mg/dL | Mean within run SD N=3 | Total Run SD | Total Mean mg/dL | Total SD - all runs | % CV | N |
| --- | --- | --- | --- | --- | --- | --- | --- |
| DControl 1 | 90 | 0.6 | 1.7 | 93 | 4.2 | 4.5 | 51 |
| DControl 2 | 305 | 1.5 | 0.3 | 319 | 13.1 | 4.1 | 51 |
| Urine 1 Cntrl | 43 | 0.6 | 0.3 | 43 | 2.0 | 4.6 | 35 |
| Urine 2 Cntrl | 286 | 2.2 | 2.5 | 295 | 10.8 | 3.7 | 57 |
| CSF1 Cntrl | 53 | 1.4 | 2.9 | 52 | 2.6 | 5.0 | 32 |
| CSF2 Cntrl | 92 | 1.1 | 4.9 | 90 | 3.9 | 4.4 | 32 |
Additional data were submitted as follows. Data was collected per NCCLS EP5-A. Samples were assayed in duplicates twice a day for 20 days.
| | N | Mean mg/dL | Within-run SD | W/in run %CV | Total SD | Total %CV |
| --- | --- | --- | --- | --- | --- | --- |
| CSF Control 1 | 80 | 59 | 0.8 | 1.3 | 3.8 | 6.3 |
| CSF Control 2 | 80 | 30 | 1.5 | 5.0 | 3.0 | 10.1 |
| Serum Control 1 | 80 | 89 | 2.1 | 2.3 | 6.0 | 6.7 |
| Serum Control 2 | 80 | 308 | 2.2 | 0.1 | 21.7 | 7.0 |
| Urine Control 1 | 80 | 45 | 1.0 | 2.3 | 2.3 | 5.1 |
| Urine Control 2 | 80 | 287 | 2.4 | 0.8 | 14.4 | 5.0 |
# b. Linearity/assay reportable range:
The following useable range was specified by the sponsor:
0.6 - 25 mmol/L (or 10 - 450 mg/dL) for serum, plasma, urine, or CSF.
The CX® Systems Over Range Detection and Correction (ORDAC) function will accommodate samples with glucose concentrations between 25 - 50 mmol/L (450 - 900 mg/dL). Users are instructed to dilute these samples that exceed the high end of the analytic range with saline and reanalyze. (an integrated function of the instrument, K942676, K864236)
Percent recovery was evaluated on linearly diluted samples. Pooled serum, urine, or CSF samples were spiked to achieve glucose concentrations in the upper end of the measurement range of the assay. These samples were then diluted, expected concentrations were calculated and each pool was measured using both Mission reagents and the predicate reagents. Results are summarized below.
{3}
| | Reagents | Range of % Recovery | Mean Recovery |
| --- | --- | --- | --- |
| Serum | Mission | 83.3 – 115.4 | 103 % |
| 30 – 835 mg/dL | Predicate | 83.3 – 117.5 | 103 % |
| Urine | Mission | 88 – 120 | 101 % |
| 10 – 300 mg/dL | Predicate | 87 – 110 | 97 % |
| CSF | Mission | 88 – 98 | 94 % |
| 25 – 100 mg/dL | Predicate | 88 - 100 | 95 % |
# c. Traceability (controls, calibrators, or method):
Not applicable in this submission. The use of appropriate commercially available control materials is recommended.
# d. Detection limit:
Serum samples with low glucose concentrations were tested in triplicate over 13 runs. Results are summarized below.
| Mean (mg/dL) | SD | %CV |
| --- | --- | --- |
| 41.9 | 1.52 | 3.6 |
| 14.7 | 0.75 | 5.1 |
| 9.8 | 0.95 | 9.7 |
| 3.6 | 1.35 | 37.6 |
| 2.0 | 0.65 | 32.4 |
The sponsor claims a functional sensitivity of $10\mathrm{mg / dL}$ glucose (the lowest level tested with a CV less than $20\%$ ).
# e. Analytical specificity:
Whole blood samples are not recommended. Lipemic samples $> + 3$ should be ultracentrifuged and the analysis performed on the supernatant fraction. The sponsor refers the user to literature references for other interferences caused by drugs and diseases.
$5.0\mathrm{mg / dL}$ Hydroxyethyl starch may cause a result increase of $3\mathrm{mg / dL}$ .
20 mmol/L Glutathione may cause a result increase of $31\mathrm{mg / dL}$
The following anticoagulants or chemical additives are compatible with this method:
| Anticoagulants | Acceptable level |
| --- | --- |
| Sodium Citrate® | 3.5 mg/mL |
| EDTA | 4.0 mg/mL |
| Ammonium Heparin | 45 U/mL |
| Lithium Heparin | 45 U/mL |
| Sodium Heparin | 45 U/mL |
| Lithium Iodoacetate | 1.5 mg/mL |
{4}
Page 5 of 6
* specimens collected with liquid sodium citrate will exhibit a decrease in value due to dilution.
f. Assay cut-off:
Not applicable.
2. Comparison studies:
a. Method comparison with predicate device:
Serum and Urine controls were assayed six times in triplicate using both the Mission and predicate reagents (N = 18).
| | Mission Reagent | | | | Predicate Reagent | | | |
| --- | --- | --- | --- | --- | --- | --- | --- | --- |
| | Mean (mg/dL) | Within run SD | Total SD | % CV | Mean (mg/dL) | Within run SD | Total SD | % CV |
| DControl1 | 90 | 0.6 | 1.7 | 0.6 | 90 | 0.6 | 2.3 | 0.8 |
| DControl2 | 305 | 1.5 | 0.3 | 0.4 | 293 | 1.5 | 0.3 | 0.4 |
| Urine 1 | 43 | 0.6 | 0.3 | 0.8 | 44 | 1.0 | 0.5 | 1.1 |
| Urine 2 | 286 | 2.2 | 2.5 | 0.9 | 279 | 2.4 | 1.2 | 0.4 |
Comparisons of spiked serum, CSF, or urine samples or controls using the Mission reagent and the predicate reagent yielded the following correlations:
Serum:
- Range 0 – 400 mg/dL: $y = 1.09x - 2.52$, $R^2 > 0.999$
- Range 0 – 500 mg/dL: $y = 1.08x - 1.78$, $R^2 = 0.999$
- Range 0 – 780 mg/dL: $y = 1.08x - 2.37$, $R^2 = 0.999$
CSF:
- Range 23 – 90 mg/dL: $y = 0.96x + 1.50$, $R^2 = 0.997$
Urine:
- Range 20 – 294 mg/dL: $y = 1.05x - 4.80$, $R^2 = 0.999$
Additional data were submitted. Tests were performed per NCCLS EP9-A2 and analyzed by least squares regression.
Fifty (50) serum samples were spiked or diluted and tested in triplicate with the Mission reagents and the predicate reagents.
Range = 0 to 900 mg/dL
Mission = 1.038 (Predicate) – 2.31
$r^2 = 0.998$
95% CI at 70 mg/dL - 66.4 to 74.3 mg/dL
95% CI at 105 mg/dL – 102.3 to 111.0 mg/dL
Fifty-seven (57) urine samples were spiked or diluted and tested in triplicate with the Mission reagents and the predicate reagents.
{5}
Page 6 of 6
Range = 1 to 293 mg/dL
Mission = 1.022 (Predicate) + 1.067
r² = 0.998
95% CI at 1 mg/dL – 1.18 to 2.99 mg/dL
95% CI at 15 mg/dL – 15.3 to 17.4 mg/dL
Thirty-six (36) CSF samples were spiked or diluted and tested in triplicate with the Mission reagents and the predicate reagents.
Range = 8 to 118 mg/dL
Mission = 1.014 (Predicate) – 0.920
r² = 0.997
95% CI at 40 mg/dL – 37.7 to 41.5 mg/dL
95% CI at 70 mg/dL – 67.6 to 72.5 mg/dL
b. Matrix comparison:
Not applicable. Performance data was submitted for all matrices.
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:
| Sample Type | Units (mmol/L) | SI Units (mg/dL) |
| --- | --- | --- |
| Serum or Plasma | 3.9 – 5.8 | 70 - 105 |
| CSF | 2.2 – 3.9 | 40 - 70 |
| Urine | 0.06 – 0.8 | 1- 15 |
The sponsor states that normal fasting glucose is between 70 and 110 mg/dL. Diabetes (hyperglycemia) is diagnosed when patient glucose levels are: fasting glucose > 126 mg/dL, serum glucose of > 200 mg/dL, or other symptoms. Hypoglycemia is diagnosed when patient glucose levels are < 60 mg/dL.
The sponsor states that these values are intended as a reference, and that no adjustments have been made for age, sex, or dietary differences. Each laboratory should establish a reference range based on their patient population.
M. Conclusion:
I recommend that the Mission Diagnostic Glucose Reagent for Beckman Synchron CX® & CX® Delta Systems is substantially equivalent to the legally marketed predicate device.
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.