The Platform
How the 1health platform is organized
Four layers that turn healthcare's fragmented data into a composable protocol stack — protocols, primitives, services, and modules that developers build applications on.
The Problem
Healthcare data is trapped at the edges
Patient data sits in silos — locked inside proprietary EHRs, lab systems, and payer platforms. Applications can't access real-time, accurate data because it's fragmented across dozens of disconnected systems.
Every connection is a custom, point-to-point integration.
No shared protocols. No shared data layer. No unified audit trail.
No standard protocols
Unlike the internet (HTTP) or email (SMTP), healthcare has no universal protocols for ordering a lab test, sharing a care plan, or coordinating a transition of care. Every integration is bespoke.
Data stuck at the edge
Patient records are locked inside individual systems. There is no canonical, shared source of truth that applications can build against. Each system has a partial, often outdated view.
No visibility into data movement
When data moves between organizations — via fax, HL7, or manual upload — nobody has a unified audit trail. IT and compliance teams are stitching together logs from a dozen systems to answer basic questions about who accessed what.
The Platform
How the 1health platform is organized
Four layers. Each with a clear job. Composable from the bottom up.
What developers call
Grouped API endpoints developers call to compose applications.
What runs the workflows
Long-running backend systems that ingest, process, and orchestrate.
Canonical data and rules
Canonical data structures and workflow rules.
Atoms of the data model
Canonical healthcare nouns — the atoms of the data model.
Developers build applications by calling modules. Modules are powered by services running behind them. Services read from and write to protocols — the canonical data structures and workflow rules that make cross-organizational exchange possible. Protocols are composed of primitives — the canonical healthcare objects (an order, a person, an encounter) that everything else is built from.
The Solution
A protocol layer for every domain of care
1health creates canonical protocols that standardize how data is exchanged across healthcare — the same way HTTP standardized document exchange and SMTP standardized email. Services run on top of those protocols. Modules give developers the API surface to build.
Canonical Data Model
Patients, providers, payers, labs, encounters — one normalized schema regardless of source system. Applications write their logic once and it works with every endpoint on the network.
Shared Ledger
A single, normalized source of truth in the cloud. Data from any source is committed to a canonical record with a complete audit trail of every exchange, permission, and access event. Cross-organizational by design.
Canonical Compendium
Every lab has its own test catalog, codes, and ordering requirements. 1health normalizes them into one canonical compendium — so applications interact with a single, unified lab protocol regardless of which lab fulfills the order.
Workflow Builder
Build multi-step workflows where each step can involve any combination of systems, people, and services. 1health handles the data flow between endpoints and maintains the canonical record of everything that happens.
Granular Permissioning
Control data access at the atomic level — per record, per user, per app, per organization. Invite partners, sign BAAs, and grant access to specific records. The platform tracks every sharing relationship and permission change.
Developer Modules
Lab Orders, Claims Data, Provider Search, Work Queue, Notifications, MCP. One API call composes primitives into workflows that span every endpoint on the network.
Architecture
Every entity becomes an endpoint on the network
Applications built on 1health interact with any healthcare entity through a single, standardized interface. The platform handles translation, routing, permissioning, and auditability.
Connected Endpoints
Addressable Endpoints
(reachable via connectivity partners)
← Standardized Protocols →↓ Standardized Protocols ↓
1health Platform
Canonical data model
Protocol translation
Permissioned shared ledger
Complete audit trail
← Standardized APIs →↓ Standardized APIs ↓
Applications
"Connected" means live bidirectional integration. "Addressable" means reachable via 1health connectivity partners and expanding.
What to do next
Choose the path that fits your organization.