ARKRAY DIABETES DATA MANAGEMENT SOFTWARE (SMBG VIEWER)
K093819 · Arkray Factory USA, Inc. · NBW · Jun 9, 2010 · Clinical Chemistry
Device Facts
Record ID
K093819
Device Name
ARKRAY DIABETES DATA MANAGEMENT SOFTWARE (SMBG VIEWER)
Applicant
Arkray Factory USA, Inc.
Product Code
NBW · Clinical Chemistry
Decision Date
Jun 9, 2010
Decision
SESE
Submission Type
Traditional
Regulation
21 CFR 862.1345
Device Class
Class 2
Attributes
Software as a Medical Device
Indications for Use
The ARKRAY Diabetes Data Management Software (SMBG Viewer) is an optional accessory for use with ARKRAY blood glucose meters with data management capabilities. The ARKRAY Diabetes Data Management Software transfers data from the meter’s memory into a computer for enhanced data management. The ARKRAY Diabetes Data Management Software is intended for use in home and clinical settings to assist people with diabetes and their health care professionals in review, analysis and evaluation of historical blood glucose test results to support diabetes management.
Device Story
Software accessory for ARKRAY blood glucose meters; transfers stored glucose data via USB cable to PC. User/clinician installs software from CD; downloads meter memory; views data as graphs, charts, and reports (histograms, logbooks, modal days, pie charts, trends). Supports personal (single-patient) or professional (multi-patient) modes. Enables manual entry of health data (carbohydrates, exercise, HbA1c). Does not provide medical treatment or dosage recommendations. Used in home or clinical settings to facilitate diabetes management through historical data review.
Clinical Evidence
No clinical data. Bench testing included validation of hardware (USB cable) and software functionality. Consumer studies were conducted to demonstrate the system's ability to be easily operated by in-home users.
Technological Characteristics
System consists of a USB data transfer cable and software application. Operates on a computer platform. Software is used for data management, visualization, and reporting of blood glucose results. No specific materials or energy sources beyond standard USB connectivity and PC hardware.
Indications for Use
Indicated for people with diabetes and their healthcare professionals in home and clinical settings to review, analyze, and evaluate historical blood glucose test results to support diabetes management.
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.
Predicate Devices
GlucoBalance™ Data Management Software (k022545)
Submission Summary (Full Text)
{0}
# 510(k) SUBSTANTIAL EQUIVALENCE DETERMINATION DECISION SUMMARY ASSAY AND INSTRUMENT COMBINATION TEMPLATE
A. 510(k) Number:
k093819
B. Purpose for Submission:
ARKRAY is seeking clearance for the ARKRAY Diabetes Data Management Software as an accessory for use with ARKRAY blood glucose meters
C. Measurand:
Whole blood glucose
D. Type of Test:
Data management system for ARKRAY OTC whole blood glucose meters
E. Applicant:
ARKRAY Factory USA, Inc
F. Proprietary and Established Names:
ARKRAY Diabetes Data Management Software (SMBG Viewer)
G. Regulatory Information:
1. Regulation section:
21 CFR § 862.1345, Glucose Test System
21 CFR § 862.2100, Calculator/data processing module for clinical use
2. Classification:
Class II, Class I
3. Product code:
NBW, CGA, JQP
4. Panel:
75 (Clinical Chemistry)
H. Intended Use:
1. Intended use(s):
See Indication(s) for use below.
2. Indication(s) for use:
ARKRAY Diabetes Data Management Software:
The ARKRAY Diabetes Data Management Software (SMBG Viewer) is an optional accessory for use with ARKRAY blood glucose meters with data management capabilities. The ARKRAY Diabetes Data Management Software transfers data from the meter’s memory into a computer for enhanced data management. The ARKRAY Diabetes Data Management Software is intended for use in home and clinical settings to assist people with diabetes and their health
{1}
care professionals in review, analysis and evaluation of historical blood glucose test results to support diabetes management.
3. Special conditions for use statement(s):
Over-the-counter use
4. Special instrument requirements:
ARKRAY blood glucose meters such as GLUCOCARD 01 Meter (k073416), X-METER (k063771), PocketChem EZ (k063068), EasyPRO Plus (k063068), PocketChem EZ (k090653), and GLUCOCARD® Vital™ (k091102).
I. Device Description:
The ARKRAY Diabetes Data Management Software is an optional accessory for use with ARKRAY blood glucose meters with data management capabilities. The subject device consists of a USB data transfer cable and software. The system allows the user to download blood glucose results from their glucose meter to their computer, maintain a history of their glucose test results, and convert them into graphs, charts and reports. The software does not recommend any medical treatment or medication dosage level.
J. Substantial Equivalence Information:
1. Predicate device name(s):
GlucoBalance™ Data Management Software,
2. Predicate 510(k) number(s):
k022545
3. Comparison with predicate:
| Device Characteristic | Predicate: GlucoBalance | New Device: SMBG |
| --- | --- | --- |
| Indications for use | For use in home and clinical settings to assist people with diabetes and their health care professionals in review, analysis and evaluation of historical blood glucose test results to support diabetes management. | Identical |
| Installation of Program | Installed using a CD | Identical |
| Package Contents | Software and electronic instructions for use | Identical |
| Capable of uploading data from various devices | Software driver must be uploaded on the device or installed on PC | Identical |
| Software use indications | Home or multi-patient use setting | Identical |
| Deleting results | No | Yes |
{2}
| Language capabilities | English | Identical |
| --- | --- | --- |
| Customizable schedule | Yes | Identical |
| Search patient capability | Yes | Identical |
| Clock format | 12 hour clock format | Identical |
| Date format | Month/day/year only | Identical |
| Auto-detect COM port | No | Identical |
| Technical Support | Yes | Identical |
| System Components | Software and cable connection between meter and user's PC | Identical |
| Ability to export glucose test result information | Yes | Identical |
| Copy database to separate file | No | Yes |
| Ability to access DMS program via icon or explorer | No | Yes |
| Result type display | Choice of mmol/L or mg/dL | mg/dL only |
| Software Platform | Microsoft Windows 95, 98, NT, or 2000 | --Windows 2000 Professional/ XP Home edition / XP Professional, Windows Vista (32 bit edition only) |
| Hardware Requirements | --200 MHz Pentium class processor, -- 32 MB RAM for Windows 95, or 98, 64 MB RAM for Windows NT or 2000, --20 MB of free hard disk space, --Floppy or CD ROM drive, -- Available serial port. | --Pentium 100MHz or more (recommend Celeron 450MHz or more), --32 MB or more (recommend 128 MB or more), -- 40 MB disc space ore more (recommend 100 MB or more) --CD ROM drive, -- Available USB port. |
| Reports/Graphs Generated | --Histograms, --Log Book, --Modal Day, --Pie Charts, --Statistics, --Trend Chart | Identical |
| Report Type: Test Frequency | Yes | No |
3 of 7
{3}
K. Standard/Guidance Document Referenced (if applicable):
ISO 14971 Medical Devices – Application of Risk Management to Medical Devices 2007
L. Test Principle:
Data Transmission of whole blood glucose data from glucose meters.
M. Performance Characteristics (if/when applicable):
The below performance characteristics as applicable, were presented in specific glucose meter clearances under k073416, k063771, k063068, k063068, k090653, and k091102.
1. Analytical performance:
a. Precision/Reproducibility:
See above statement under section M.
b. Linearity/assay reportable range:
See above statement under section M.
c. Traceability, Stability, Expected values (controls, calibrators, or methods):
See above statement under section M.
d. Detection limit:
See above statement under section M.
e. Analytical specificity:
See above statement under section M.
f. Assay cut-off:
Not applicable
2. Comparison studies:
a. Method comparison with predicate device:
See above statement under section M.
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):
See above statement under section M.
4. Clinical cut-off:
Not applicable
5. Expected values/Reference range:
See above statement under section M.
4 of 7
{4}
5 of 7
N. Instrument Name:
ARKRAY Diabetes Data Management Software (SMBG Viewer)
O. System Descriptions:
1. Modes of Operation:
Does the applicant’s device contain the ability to transmit data to a computer, webserver, or mobile device?:
Yes ☐ X or No ☐
Does the applicant’s device transmit data to a computer, webserver, or mobile device using wireless transmission?:
Yes ☐ or No ☐ X
Operating systems - Windows 2000 Professional/ XP Home edition / XP Professional, Windows Vista (32 bit edition only)
2. Software:
FDA has reviewed applicant’s Hazard Analysis and software development processes for this line of product types:
Yes ☐ X or No ☐
3. Specimen Identification:
There are two options for data transmission; 1.) Personal option, where the data management system is dedicated to one patient; 2.) Multiple patient option where the data management system handles multiple patients.
The difference in the options is for the multiple patient option the patient is selected prior to results being transmitted from the meter.
Specimen identification is based on time and date of testing.
4. Specimen Sampling and Handling:
Data transmission from glucose meters using capillary whole blood samples
5. Calibration:
Glucose meter specific See above statement under section M.
{5}
6. Quality Control:
Glucose meter specific - See above statement under section M.
P. Other Supportive Instrument Performance Characteristics Data Not Covered In The "Performance Characteristics" Section above:
ARKRAY conducted bench testing to demonstrate data accuracy transmission for each meter stated in H. 4., special instrument requirements, above. Meter flags/functions were tested such as control solution, DEL (or!), and temperature warning to verify the information properly downloads from the meters to the data management software. Memory data rollover was also tested by adding four (4) data points to meters that were pre-loaded with full memory. Test results show that all glucose values, flags, date, and time properly downloaded from the meters to the software. Memory data rollover also functioned properly where the new glucose values replaced the oldest glucose values.
In addition, two studies each intended to assess personal lay users and professional healthcare users in the setup and use of on ARKRAY's Diabetes Data Management Software were conducted. The first study included 31 personal lay users and 5 professionals and the second study included 45 personal lay users and 10 professionals. The two studies evaluated a combined, seventy-six (76) diabetic adult consumers and fifteen (15) healthcare professionals who work with diabetics.
The GLUCOCARD X-METER, GLUCOCARD® Vital™, and PocketChem EZ Meter have different user interface. The PocketChem EZ has identical user interface as the, GLUCOCARD 01, Easy PRO Plus, and EasyPro Plus.
76 Personal lay users were given the software program on CD, operating manual, step by step user instructions, a computer and printer, an ARKRAY blood glucose meter with a USB cable and the study questionnaires. They were instructed to:
1. Install the software program as directed in the operating manual.
2. Start/access software program.
3. Enter User Information
4. Download and save data from the glucose meter.
5. Access and view information in logbook.
6. Enter user health information (carbohydrates and exercise)
7. View and print graphs and reports.
8. Export CSV files.
9. Exit software program.
6 of 7
{6}
10. Complete “Ease of Use” and “Performance” Questionnaires.
15 Professional users were given a copy of the software program on CD, operating Manual, step by step user instructions, computer, an ARKRAY blood glucose meter with a USB cable and the study questionnaires. Using simulated patient data they were instructed to:
1. Install and start the software program as instructed in the operating manual.
2. Enter patient preferences and profile (name, target ranges, patient demographics, printer preferences, time block settings ...).
3. Enter user health information (carbohydrates and exercise).
4. Download and save data from the blood glucose meter.
5. View and print graphs and reports.
6. Import and export CSV files.
7. Enter “Other Data” (HbA1c).
8. Exit software program.
9. Complete “Ease of Use” and “Performance” Questionnaires.
Personal lay users rated ARKRAY’s Diabetes Data Management Software Program at 100% for overall program as easy or somewhat easy. There were no users that rated the software program as somewhat difficult or difficult.
Overall, professional health care users rated ARKRAY Diabetes Data Management Software Program at 100% as easy or somewhat easy.
Q. Proposed Labeling:
The labeling is sufficient and it satisfies the requirements of 21 CFR Part 809.10.
R. Conclusion:
The submitted information in this premarket notification is complete and supports a substantial equivalence decision.
7 of 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.