What is OpenGlucose?
Why OpenGlucose?
The introduction page for developers, vendors, researchers, and partners evaluating open glucose interoperability.
Why we exist
Glucose data is generated continuously by CGMs, apps, and clinical systems—but it rarely travels cleanly between them. Each vendor uses different APIs, models, and semantics. That friction blocks innovation in apps, AI, research, and healthcare integration.
Problems we solve
- Fragmented vendor APIs and proprietary data shapes
- Inconsistent glucose models across apps and platforms
- Poor portability for AI training and research datasets
- Friction integrating glucose data into broader health workflows
Why not Apple Health alone?
Apple Health is a platform boundary on Apple devices—not a vendor-neutral, publicly specified standard for cross-vendor glucose exchange. OpenGlucose complements platform APIs with open schemas any implementer can use on any stack.
Why not FHIR alone?
FHIR excels at healthcare exchange. Open Glucose Interoperability adds glucose-native semantics, telemetry contracts, and developer ergonomics for streaming and app-level integration. The two are complementary—not competing—at clinical boundaries.
Why not Nightscout?
Nightscout is a vital community tool for CGM sharing. OpenGlucose pursues vendor-neutral standards at organization scale with open governance—so any vendor, app, or platform can implement the same contract.
Open Glucose Telemetry vs Open Glucose Interoperability
Open Glucose Telemetry (OGT) ingests vendor-specific data, validates envelopes, normalizes fields, and produces canonical output. Open Glucose Interoperability defines that canonical output—schemas, semantics, timestamps, units, and provenance—that producers and consumers share.
Why vendors should adopt
Vendor-neutral standards reduce integration cost, expand ecosystem reach, and create a path toward conformance and certification as the community matures. Implement once against OGIS; interoperate with every adopter.