K122142 · Glooko, Inc. · NBW · Dec 21, 2012 · Clinical Chemistry
Device Facts
Record ID
K122142
Device Name
GLOOKO LOGBOOK CHARTS
Applicant
Glooko, Inc.
Product Code
NBW · Clinical Chemistry
Decision Date
Dec 21, 2012
Decision
SESE
Submission Type
Traditional
Regulation
21 CFR 862.1345
Device Class
Class 2
Attributes
Software as a Medical Device
Indications for Use
The Glooko device system for the Glooko Logbook Application and Glooko Logbook Charts is data management software intended for use in home and professional settings to aid individuals with diabetes and their health care professionals in review, analysis and evaluation of blood glucose readings to support an effective diabetes management program. The Glooko device system for the Glooko Logbook Application connects to compatible FDA cleared meters and allows users to transfer their blood glucose meter results to their iPhone operating system platform. The Glooko device system for the Glooko Logbook Application and Glooko Logbook Charts are not intended to provide treatment decisions or to be used as a substitute for professional healthcare advice.
Device Story
System consists of Glooko MeterSync Cable, IR Adapter, Logbook Application (iOS), and Logbook Charts (Excel-based software). Device downloads blood glucose (BG) data from FDA-cleared meters via cable or IR adapter to an iOS device. Application allows user annotation of readings, data viewing, and sharing. Logbook Charts software enables quantitative evaluation of downloaded data, generating reports on average BG values, trends, and scattergrams by time/date. Used by patients and healthcare professionals in home or clinical settings. Output assists in diabetes management by providing visual and statistical summaries of glucose history. Does not provide treatment recommendations.
Clinical Evidence
No clinical trials; evidence based on bench testing and usability performance validation. Usability studies (IRB-approved) conducted with 20 patients (Type 1/2 diabetes) for the application/cable and 20 patients plus 15 healthcare professionals for the charts software. Validated data download accuracy, annotation/sharing capabilities, and user manual effectiveness. Software verification and validation performed per moderate level of concern requirements, including data integrity, design verification, and error handling. All results met pre-determined specifications.
Technological Characteristics
System includes hardware (MeterSync Cable, IR Adapter) and software (iOS App, Excel-based Charts). Connectivity via 30-pin iOS connector and 3.5mm meter interface or IR. Software is a data management tool for visualization and statistical analysis. Validated under moderate level of concern. No specific material standards or energy sources beyond standard consumer electronics connectivity.
Indications for Use
Indicated for individuals with diabetes and their healthcare professionals in home and professional settings to aid in the review, analysis, and evaluation of blood glucose readings. Not intended for treatment decisions or as a substitute for professional medical advice.
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
GlucoFacts Express Data Management Software (K082486)
Submission Summary (Full Text)
{0}
1
# 510(k) SUBSTANTIAL EQUIVALENCE DETERMINATION DECISION SUMMARY INSTRUMENT ONLY TEMPLATE
A. 510(k) Number:
k122142
B. Purpose for Submission:
New Device
C. Manufacture and Instrument Name:
Glooko, Inc.
Glooko Device System for Logbook Application & Glooko Logbook Charts
D. Type of Test or Test Performed:
Diabetes data management system
E. System Descriptions:
1. Device Description:
The Glooko device system includes two major modules: Glooko Logbooks™ and Glooko Logbook Charts™. The main function of Glooko Logbooks™ is to extract data from FDA-cleared glucose meters. The major function of Glooko Logbook Charts™ is to analyze and graph the data obtained from Glooko Logbooks™ to assist people with diabetes who self-manage their Blood Glucose (BG) readings.
The Glooko™ Logbooks
The Glooko™ Logbooks contain the following: Glooko MeterSync Cable, Glooko IR Adapter, and Glooko Logbook app. (1) The Glooko MeterSync Cable downloads data from compatible, FDA-cleared, commercial blood glucose meters into an iOS (iPhone Operating System) device by connecting the two components. One end of the Glooko MeterSync Cable plugs directly into the 30-pin connector slot of the iOS device. The 3.5mm end of the Glooko MeterSync Cable plugs directly into several FDA cleared, compatible meters to allow for the transfer of data. A listing of the FDA cleared meters, compatible with this system are identified in section H. Some meters require an additional 3.5mm to 2.5mm adapter to allow for this connectivity, while other meters transfer data through infrared, and thus require the use of the Glooko IR Adapter. The Glooko MeterSync Cable is designed to attach to a variety of compatible, FDA-cleared, commercial blood glucose meters. The users simply connect the supported meters to their iOS device and transfers the blood glucose meter data into the Glooko Logbook app. (2) The Glooko IR Adapter is designed to transmit data via infrared from a variety of compatible, FDA-cleared, commercial blood glucose meters into the Glooko Logbook app. The user connects the Glooko IR Adapter
{1}
to the 3.5mm adapter end of the Glooko MeterSync Cable to transmit data from the compatible meters. (3) The Glooko Logbook app performs the following functions: a) Syncs with compatible meters; b) Allows users to annotate glucose measurements with notes; c) Provides multiple view options for the data; and d) Shares the collected data in multiple formats to anyone the user selects. This iOS application logs the user's blood glucose values and meal tags that are downloaded from compatible blood glucose meters.
## Glooko™ Logbook Charts
The Glooko™ Logbook Charts is a data management software tool designed to assist people with diabetes who self-manage their Blood Glucose (BG) readings. The Logbook Charts software is used in conjunction with the Glooko MeterSync Cable and Logbook Application. The MeterSync Cable and Logbook Application allow users to download BG readings from commercially available blood glucose meters to an iOS device. The Glooko Logbook Charts software tool enables the Glooko Logbook App users to chart and graph their BG values from the application. Glooko Logbook Charts is a spreadsheet program developed in Microsoft Excel and helps with quantitatively evaluating the BG data downloaded into the Glooko Logbook Application. Users can download the Glooko Logbook Charts sheet template from the Glooko website to generate and display reports on average BG values and BG trends. Several statistical parameters are calculated and the data is plotted as scatter grams relating blood glucose by time of day and by date. Glooko Logbook Charts specifically offers the following charts and table for view:
1) BG readings By Time of Day provides an overview of glucose readings during the day. 2) BG readings By Date: provides an overview of glucose readings over a specified date range. 3) BG readings Analysis By Time Of Day: provides an overview of analyzed glucose readings during the day with high and low values, percentiles, mean and medians, and BG readings Summary Statistics, which provides an overview of the analyzed glucose readings in table format.
## 2. Principles of Operation:
The Glooko™ system is a data management software tool.
Operating System requirements for the Glooko device system are: Windows XP Professional, Windows server 2003, Windows Vista Professional or Windows 7 Professional. The system requirements are as follows: (1) Microsoft Windows personal computer, (2) CPU: 550 MHz Intel Pentium 3 or above, (3) DRAM: 512 or above, (4) HD: 2 GB or more, (5) Internet Explorer 7.0 or above, (6) USB 2.0 or above, (7) LCD screen with resolution of 1024x768 or above, (8) CD-ROM drive and (9) a printer (Optional).
iOS devices with versions employed to extract data from blood glucose (BG) meters.
{2}
| iOS Device | Version |
| --- | --- |
| iPod touch | 3rd Generation and above |
| iPhone | 3GS, 4, 45 |
| iPad | 1, 2 and 3 |
3. Modes of Operation:
Does the applicant’s device contain the ability to transmit data to a computer, webserver, or mobile device?
Yes ☐ or No ☑.
Does the applicant’s device transmit data to a computer, webserver, or mobile device using wireless transmission?
Yes ☐ or No ☑.
4. Specimen Identification:
Specimen identification is based on time and date of testing.
5. Specimen Sampling and Handling:
Data transmission from glucose meters using capillary whole blood samples
6. Calibration:
Glucose meter specific. See statement below under section J.
7. Quality Control:
Glucose meter specific. See statement below under section J.
8. Software:
FDA has reviewed applicant’s Hazard Analysis and Software Documentation:
Yes ☐ or No ☑.
F. Regulatory Information:
| Device Name | Product Code | Classification | Regulation | Panel |
| --- | --- | --- | --- | --- |
| Glucose Test System | NBW: Blood Glucose Test System, Over-the-Counter | Class II | 21 CFR § 862.1345 | Clinical Chemistry (75) |
| Calculator/Data Processing Module for Clinical Use | JQP: Calculator/Data Processing Module for Clinical Use | Class I * | 21 CFR § 862.2100 | Clinical Chemistry (75) |
* A premarket notification (510 (k)) is required for the Class I devices meeting the limitations under 21CFR 862.9 (c)(5) For use in diabetes management.
G. Intended Use:
1. Indication(s) for use:
The Glooko device system for the Glooko Logbook Application and Glooko
{3}
Logbook Charts are data management software intended for use in home and professional settings to aid individuals with diabetes and their health care professionals in review, analysis and evaluation of blood glucose readings to support an effective diabetes management program. The Glooko device system for the Glooko Logbook Application connects to compatible FDA cleared meters and allows users to transfer their blood glucose meter results to their iPhone operating system platform.
The Glooko device system for the Glooko Logbook Application and Glooko Logbook Charts are not intended to provide treatment decisions or to be used as a substitute for professional healthcare advice.
2. Special conditions for use statement(s):
Over-the-counter use
H. Substantial Equivalence Information:
| | Glooko Logbook Charts / Logbook (K122142)
New Device | GlucoFacts Express Data Management Software (K082486)
Predicate |
| --- | --- | --- |
| Intended use | • For use in home and professional settings
• Device allows for the review, analysis and evaluation of BG results from a variety of FDA cleared meters | Same |
| Logbook for | Blood glucose readings, insulin and carbs intake | Same |
| Accessory to | Accu-Chek Aviva, Accu-Chek Compact Plus, Accu-Chek Nano, Bayer’s Breeze 2, Bayer’s Contour NEXT EZ, Bayer’s Contour, Freestyle Freedom-Lite, Freestyle Lite, One Touch Ultra 2, OneTouch Ultra-Link and OneTouch Ultra-Mini, Glucocard 01, Glucocard Vital, ReliOn Confirm, ReliOn Prime meters. | Bayer’s Contour, Contour TS, Breeze, and Breeze 2 blood glucose meters. |
| Use on | PC / Mac / iOS Platforms | PC |
| Data Analysis-Statistics | Mean, Median, Min, Max, Standard deviation, percentiles and Total | Mean, Min, Max, Standard deviation, Target (%), Above Target (%), Below |
{4}
| | Glooko Logbook Charts / Logbook (K122142) | GlucoFacts Express Data Management Software (K082486) |
| --- | --- | --- |
| | New Device | Predicate |
| Generated | number of tests | Target (%) and Total number of tests |
| Data Analysis-Ability to set target ranges | Yes | Same |
| Data Graphics-Reports, Charts, and Graphs | • Glucose by time of day
• Glucose by date
• Glucose analysis by time of day
• Glucose summary statistics table | • Glucose trend results by day.
• Daily blood glucose trends.
• Weekly blood glucose trends.
• Summary chart |
I. Special Control/Guidance Document Referenced (if applicable):
- ISO 14971, Medical devices - Application of risk management to medical devices.
- AAMI TIR36:2007 Validation of software for regulated processes
- EN55D24: 2003 European standard for information technology equipment- immunity characteristics – limits and methods of measurement
- ANSIC63.42003: American national standard for methods of measurement of radio-noise emissions from low-voltage electrical and electronic equipment in the range of 9 khz to 40 Ghz
- EN55022:2006-A1:2007: Information Technology Equipment – Radio Disturbance Characteristics Limits and Methods of Measurements
J. Performance Characteristics:
1. Analytical Performance: The performance characteristics listed below as applicable, were established in the specific glucose meter clearance under k043474, k081389, k113137, k062347, k062058, k111268, k051839, k070850, k073416, k091102, k062195, k073231, k061118, k073416, and k091102.
a. Accuracy:
See above statement under section J(1).
b. Precision/Reproducibility:
See above statement under section J(1).
c. Linearity:
See above statement under section J(1).
d. Carryover:
{5}
See above statement under section J(1).
e. Interfering Substances:
See above statement under section J(1).
2. Other Supportive Instrument Performance Data Not Covered Above:
1) The following documentation related to the software was reviewed and found to be acceptable: level of concern (moderate), software description, device hazard analysis, software requirements specifications, software design specification, revision level history, unresolved anomalies, software development environment description, verification testing and traceability analysis.
a. Glooko Logbook: The Glooko Logbook software was validated pursuant to the moderate level of concern requirements. Design validation testing confirmed that the Glooko device performs according to the stated intended use. Such testing included Characterization of the Glooko Logbook spreadsheet, Data Integrity Verification, Software Design Verification, Microsoft Excel Version Testing and Glooko Logbook Application Version testing. The validation of Glooko Device System for Logbook Application were validated in 29 patients with Type 1 and Type 2 diabetes and 2 healthcare professionals.
The test goals for this study were to validate:
- Accuracy of data download into the Glooko device System
- Ability to share (transmit, download, save and email) and annotate data
- Effectiveness of user manual
- Ease of use of the Glooko MeterSync Cable and the Logbook Application
b. Glooko Logbook Charts: A validation study was conducted based on pre-designed study protocol. The validation of Glooko Device System for Logbook Application & Glooko Logbook Charts were validated in 22 patients with Type 1 and Type 2 diabetes and 15 healthcare professionals. The test goals for this study were to validate:
- Effectiveness of the User Manual
- Ability to transmit, download, save and email csv files
- Ability to view and print the Logbook Chart graphs
2). A usability study was conducted using the Glooko Device System for Logbook Application in 20 patients with Type 1 and Type 2 diabetes. Additional subsequent validation/human usability studies for Glooko device system in 9 diabetes patients and 2 healthcare providers.
a. The protocol and acceptance criteria of the usability studies were reviewed and found to be acceptable. The results from the usability study demonstrated that the product performs as intended in the hands of lay users and healthcare professionals. All test results fell within the pre-determined specification parameters.
b. A readability study was performed on the labeling and the above studies were reviewed and found to be acceptable.
6
{6}
3). The sponsor provided the appropriate documentation certifying that electromagnetic testing been evaluated.
K. Proposed Labeling:
The labeling is sufficient and it satisfies the requirements of 21 CFR Part 809.10.
L. 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.