From prototype to patient, on infrastructure that's already connected
You build the app. 1health runs the healthcare plumbing underneath it — patient identity, records, permissions, audit, lab ordering, messaging, and provider workflows — so one engineer can take an app from prototype to production in 30 days.
Trusted by major health plans, laboratories, and health systems
Where the line is
What's yours, and what we run
You keep
- Your product, interface, and brand
- Your business rules and clinical logic
- Your customers and the patient and provider relationship
- Your pricing and your business
1health runs
- Patient identity and records
- Connections to labs, health plans, providers, and fax
- Workflows that cross organizations
- Compliance: SOC 2 Type II, BAAs, audit logs, and access rules
Apps on 1health are their builders' products. 1health is the layer underneath them.
For Builders
Three tracks. One platform.
Whether you're shipping an agentic app, a lab-connected product, or running a health plan — 1health is the infrastructure your teams build on.
Agentic software development is here — and you need a shared fabric to deploy it.
Startups & Developers
Ship an agentic healthcare app in days, not quarters. Build on the shared data model, MCP, and provider directory that eight production apps already run on.
- Full MCP for Cursor, Claude Code, V0, Replit, Codex
- Shared data model across every care setting
- Production-grade HIPAA from day one
Lab-Connected Products — built on LabLink
For diagnostics, therapeutics, and digital health companies whose products need to order labs, receive results, and run clinical workflows end to end.
- Universal test catalog across hundreds of lab partners
- Flexible order capture models
- Standardized results with intelligent routing
Payers & Health Plans
For large healthcare organizations with IT, security, and compliance requirements. Dedicated infrastructure, BAA availability, and governance controls.
- Dedicated environment with custom terms
- Real-time data access dashboard and audit trails
- Compliance reporting and governance controls
Don't want to build it yourself? See engineering teams that ship on 1health →
In Production
Real apps, already in production
Transitions of Care: one engineer, 30 days, now serving 40,000–50,000 patients a month across a national payer network. Eight production apps shipped on 1health in a single quarter with a five-person team. Each is its own product, run by the organization it was built for.
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.
Care Management
Transitions of Care
Automates the hospital → primary care handoff: real-time ADT ingestion, PCP notification, follow-up coordination, Stars/HEDIS gap closure — all on the 1health Patient Vault. Built in 30 days by one engineer.
Patient Flow
Symphony
A living map of how patients move through a healthcare ecosystem — enabling real-time patient flow optimization across care settings.
Biotech
Muse Bio
Built the donor eligibility and lab workflow for a menstrual stem cell-based regenerative medicine platform, enabling nationwide expansion in about one month.
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 organizedStart building
Whether you're building a healthcare application or connecting your organization to the platform — start here.