Standards

Architecture

Open Glucose Interoperability defines what glucose data means. Open Glucose Telemetry defines how glucose data moves.

Specification layer (OGIS)

OGIS is not a runtime. It publishes canonical schemas, semantic conventions, unit and timestamp rules, provenance requirements, and validated examples. Implementers treat the JSON Schema as normative for glucose.reading v0.1.

Runtime layer (OGT)

OGT provides adapters, validation, normalization, and routing. Vendor-specific payloads enter through adapters; OGT validates against OGIS and emits canonical events consumers can trust.

End-to-end flow

1. Source system produces a vendor-specific reading (HealthKit, Dexcom, LibreLinkUp, manual app entry, etc.)
2. OGT adapter maps fields to glucose.reading v0.1
3. OGT validates, deduplicates, and attaches provenance
4. Applications, AI pipelines, research tools, and EHR integrations consume OGIS-shaped events

Data Model → · Getting Started →