Ship healthcare apps in days, not quarters.
Build healthcare applications on the 1health MCP. Plug in from Cursor, Claude Code, V0, Replit, or Codex and reach 70M+ covered lives, 300K+ providers, and the labs and EHRs already wrapped as MCP nodes — with BAAs, identity, and audit already handled for you.
30 days. One engineer. One app. 300K providers onto the network.
Transitions of Care was built in 30 days by one engineer against the 1health MCP. It now handles 40,000–50,000 patients per month across a national payer network, runs in 50 states, supports 100+ clinical staff per payer, and lifted Star ratings from 2 to 5.
The 1health team shipped 8 enterprise applications in Q1 2026 with a 5-person delivery team. About 80% of any healthcare application's surface area — canonical patient record, provider directory, identity layer, audit ledger, BAA framework — is already shipped as platform infrastructure. Developers build the application-specific 20%, not the whole stack.
100 PCPs per month sign up to the network with zero marketing spend. Developer pull is real.
Build from the tools you already use
Build healthcare apps directly from Cursor with full access to the canonical data model, provider network, and BAA-aware exchange.
Build healthcare apps directly from Claude Code with full access to the canonical data model, provider network, and BAA-aware exchange.
Build healthcare apps directly from V0 with full access to the canonical data model, provider network, and BAA-aware exchange.
Build healthcare apps directly from Replit with full access to the canonical data model, provider network, and BAA-aware exchange.
Build healthcare apps directly from Codex with full access to the canonical data model, provider network, and BAA-aware exchange.
Build healthcare apps directly from Vercel with full access to the canonical data model, provider network, and BAA-aware exchange.
The 80% that's already shipped
A canonical, longitudinal patient record store for the patients your app serves — identity, history, and consent in one place, scoped to your data and kept in your enclave.
Live directory of providers and NPI-verified org relationships. 2M+ providers.
Org identity for humans, legacy systems, and agents. Verified, auditable, revocable.
Universal test catalog. Provider ordering portal. EHR connectivity.
HL7, FHIR, HIE, ADT, fax, SFTP. Every legacy system becomes an MCP node.
BAA framework, consent capture, governance, per-record access control.
Multi-step cross-org workflows authored in natural language. Spec to prod in days.
Complete provenance of every read, write, and attestation. Regulatory-defensible.
Why build on 1health instead of FHIR or Epic?
FHIR is the wire format, not the runtime. Every FHIR developer hits the same five-month cold start: brokering BAAs, building identity infrastructure, instrumenting audit, chasing endpoints one at a time. 1health speaks FHIR on the wire — but adds the canonical data plane, stateful workflows, identity, and governance that FHIR doesn't offer.
Epic's App Market is single-tenant. You can sell into Epic-only health systems — the moment your app touches a payer or lab outside the Epic fold, the App Market is a wall. On 1health, your app reaches every payer, provider, and lab on the network from day one.
TEFCA, QHINs, and HIEs route packets between organizations. They don't hold state, identity, or orchestration. 1health is the runtime layer above all of them — stateful, governed, BAA-aware.
Start building
Get MCP access, plug in from your AI coding tool of choice, and ship your first healthcare application.