For teams building healthcare apps

From prototype to patient, on infrastructure that's already connected

Healthcare apps are easy to spin up and hard to take live. 1health gives you the patient identity, records, permissions, audit, lab ordering, messaging, and provider workflows to reach production — without rebuilding the compliance stack. It's the same infrastructure our team ships eight enterprise apps a quarter on.

Trusted by major health plans, laboratories, and health systems

70M+
Covered Lives
300K+
Providers Onboarded
SOC 2 Type II
Annually Audited
HIPAA
Compliant Infrastructure

In Production

Real apps, already in production

Transitions of Care was built in 30 days by one engineer on the 1health MCP — now serving 40,000–50,000 patients/month across a national payer network. Eight enterprise apps shipped in Q1 by a five-person team.

A provider connected through one app is already reachable for medication adherence, lab ordering, transitions of care, and every future application. Every app you ship reuses the same connections — so each one is faster to build than the last.

Common Questions

What developers and partners ask first

The Platform

Under the hood: four layers you compose.

1health organizes around four layers: protocols (canonical data structures and workflow rules), primitives (atomic healthcare objects), services (long-running backend engines), and modules (the API surface developers call). Applications and agents compose these layers into healthcare workflows that span every endpoint on the network. As more teams build on 1health, every connection becomes reusable — so the platform gets more useful over time.

See how the platform is organized
ModuleAPI surface developers call
ServiceLong-running backend engines
ProtocolCanonical data & workflow rules
PrimitiveAtomic healthcare objects

Start building

Whether you're building a healthcare application or connecting your organization to the platform — start here.