OpenGlucose

Open Glucose Interoperability

Standards overview

Open Glucose Interoperability (OGIS) is the specification layer: canonical schemas, semantic conventions, and validated examples. It is not a runtime—OGIS defines what glucose data means. For how data moves through adapters and collectors, see the OGT runtime ecosystem.

Specification stack

OGIS layers from governance and core semantics through JSON Schema, with multiple provenance source systems converging on canonical glucose.reading events.

Governance and core semantics sit above the normative glucose.reading schema. Multiple upstream source systems map to one canonical event shape for consumers.

Published today (v0.1)

  • glucose.reading with event_version 0.1 — canonical CGM and manual reading event
  • Core semantics for time (observed_at, received_at, source_recorded_at), units (mg/dL), provenance, and measurement source
  • JSON Schema at schemas/jsonschema/glucose.reading.v0_1.json with CI-validated examples
  • Release pin: Git tag ogis-v0.1.0-schema

Specification layers

Layer Contents Learn more
Core semantics Time, units, provenance rules Time · Units · Provenance
Semantic conventions measurement_source, device.type, trend, quality Measurements · Metadata
Event model glucose.reading v0.1 (normative); alerts and sessions planned Events · Data Model
Source-system registry Informative provenance.source_system strings Provenance

Multiple sources, one canonical shape

OGIS examples show how different upstream paths produce the same glucose.reading contract. OGT adapters set provenance.source_system during mapping; consumers rely on OGIS field semantics, not vendor payload shapes.

Example fixture provenance.source_system measurement_source
HealthKit CGM com.apple.health cgm / bgm / manual
Dexcom cloud dexcom cgm
LibreLinkUp direct abbott.librelinkup cgm
App manual entry app.manual manual
Watch quick log app.manual manual (device.type watch)

Validated fixtures live in OpenGlucoseInteroperabilityStandard/examples. See also Example JSON.

Validation and conformance

  • Example validation — npm run validate:examples in the interoperability repository (CI gate on every change)
  • OGT pinned schema — Open Glucose Telemetry vendors a copy under spec/pinned/ and validates at pipeline stage 8
  • Swift reference validator — OpenGlucoseInteroperabilityStandardSwift for embedded apps
  • Cross-runtime parity — OGT TypeScript ↔ Swift golden fixtures prove the same canonical output

A formal conformance certification program is planned; see Conformance.

Relationship to OGT

OGIS is authoritative for schema and semantics. OGT pins the schema, maps vendor payloads, and validates canonical output. Mental model: OGIS is the grammar; OGT is the postal system. Architecture covers both roles end-to-end.

Explore the specification

Why OpenGlucose? →