Connectivity and Data Standards (Bluetooth/BLE)

A Bluetooth blood glucose meter can send your readings to a phone, but in practice it usually sends them to one app: the one its manufacturer publishes. Two open standards, the Bluetooth Glucose Profile and IEEE 11073-10417, were written so that any app following the rules could read any meter following them. Below we explain how those standards work, why they haven't made meters interchangeable, and what that means if you want your numbers somewhere else.

What the Bluetooth radio in a meter does

Bluetooth Low Energy (BLE) is the low-power form of Bluetooth that phones use to talk to small battery-powered gadgets. In a meter, it's a way to copy finished results out of memory. The measurement itself happens on the strip: an enzyme reacts with glucose, and the meter turns the resulting electrical current into a number.[1] When the FDA cleared the Accu-Chek Guide in August 2016, its review listed "USB for PC connectivity and BLE (Bluetooth Low Energy) for wireless," and noted that the meter stores up to 720 results with the time and date.[1]

So the radio never changes how a reading is made. It only decides where the reading can go next.

How the two standards fit together

IEEE 11073-10417 is the glucose meter chapter of a larger family of standards for personal health devices. The FDA's recognized-standards database describes it as defining communication between glucose meters and "compute engines" such as cell phones and personal computers "in a manner that enables plug-and-play interoperability," using fixed term codes and data formats.[2] As of October 2026, the FDA recognizes the 2023 edition (recognition number 13-148, entered May 2025) and will accept declarations of conformity to the older 2015 edition until July 4, 2027.[2] We cover the wider family in our article on interoperability standards (IEEE 11073).

In 11073 terms, the meter is an "agent" and the phone or computer is a "manager" that collects from it.[3] Early phone apps ran this conversation over Bluetooth Classic's Health Device Profile. A 2015 study built an Android app that read a meter exactly that way.[3]

Here's what surprised us: that route has largely closed. iOS and Android don't support health data exchange over Bluetooth Classic, according to a 2025 review written by a Roche Diabetes Care engineer, so the work moved to Bluetooth Low Energy profiles, which the review calls Bluetooth's implementations of the matching 11073 standards.[4] The Glucose Profile is the one for meters. Sister profiles cover continuous glucose monitors and insulin pumps.[4]

What a Bluetooth profile actually defines

BLE devices expose data through the Generic Attribute profile, usually shortened to GATT. Data sit in small units called attributes, grouped into services that hold characteristics, and each one carries a UUID, a long identifying number.[5] The Bluetooth Special Interest Group, the industry body behind Bluetooth, publishes standard services for common jobs such as heart rate, blood pressure and glucose. It also lets manufacturers define their own vendor-specific services.[5]

That choice matters. An app has to know which services a device exposes before it can read anything.[5] A meter that offers the standard glucose service can, in principle, be read by any app written for that service. A meter that keeps its data in a private service can be read only by software that knows its maker's format.

Why your meter still talks to one app

Standards on paper haven't produced interchangeable meters. The 2025 review states plainly that manufacturers "still create closed ecosystems" with proprietary interfaces.[4] A 2022 analysis of 3,251 Android health and wellness apps found the standard glucose measurement service in just 26 of them, under 1%. Only about half of the Bluetooth IDs found across those apps (259 of 509) were publicly known ones; the rest included private vendor IDs.[5] We explore the business side of this in digital lock-ins and data silos.

As of October 2026, here's what US users see. Roche says its Accu-Chek meters pair with the mySugr app over Bluetooth and transfer values automatically.[6] LifeScan's OneTouch Reveal app connects to the OneTouch Verio Reflect and OneTouch Verio Flex meters.[7] Neither product page says whether the meter's Bluetooth link follows the Glucose Profile,[6][7] so we can't tell you whether a third-party app will read either one.

Moving your readings between apps

Because the meter-to-phone link is usually tied to one app, the practical route for moving data runs through that app. LifeScan says OneTouch Reveal syncs with Fitbit and Apple apps, and offers a web version.[7] The Accu-Chek Guide also has a USB port for a computer connection, and its memory keeps results whether or not you ever pair it.[1] How your clinic receives or uses shared readings is something to set up with your care team.

None of this is new. An FDA scientist wrote in 2015 that diabetes devices "are often capable of sharing data with a few other specific devices but are generally not broadly interoperable," and listed remote monitoring and data sharing among the things broader interoperability would improve.[8]

Security on a wireless link

Any radio link is also a way in. The FDA's final guidance on cybersecurity in medical devices, issued in February 2026, sets out the security design, labeling and documentation the agency expects in premarket submissions for devices with cybersecurity risk.[9] The 2025 review argues that open standards don't have to be less secure than closed designs, and that proven security standards beat "homebrew" solutions.[4] Our article on cybersecurity vulnerabilities in connected diabetes devices goes further.

What we still can't answer from public sources is the most practical question: which meters on US shelves as of October 2026 expose the standard Glucose Profile at all. Until manufacturers say so on their product pages, the app that comes with the meter is the only one you can count on.