Question 1

How do I build a HIPAA-ready healthcare app?

Accepted Answer

Start on infrastructure that already carries the compliance burden for you. 1health runs on HIPAA-compliant infrastructure with SOC 2 Type II annual audits, and every customer relationship operates under a Business Associate Agreement (BAA) executed at signup. You get patient identity, per-record permissions, and a complete audit trail of every read, write, and attestation out of the box, so your app is regulatory-defensible by default. PHI stays inside each customer's enclave under their BAA — you build your product logic instead of rebuilding identity, permissions, and audit from scratch.

Question 2

What patient database can I use for a healthcare app?

Accepted Answer

1health Patient Vault is a longitudinal patient record you build on directly, so you don't have to design and secure your own patient data store. It holds identity, demographics, clinical history, and consent in one place, with per-record permissions and a full audit trail behind every access. Because it's already covered by a BAA and wired to provider directories, lab ordering, and messaging, a single patient record powers every workflow your app needs. Patient data stays inside each customer's enclave under their BAA, so PHI never moves between firewalls.

Question 3

How fast can I ship a healthcare app on 1health?

Accepted Answer

Fast — because roughly 80% of a healthcare app's surface area is already built. Transitions of Care, a production app now serving 40,000–50,000 patients per month for a national payer, was built in 30 days by a single engineer on the 1health MCP. Eight enterprise applications shipped on 1health in a single quarter with a five-person delivery team. You build the application-specific 20%; the patient record, identity, permissions, audit, lab ordering, messaging, and provider workflows are already there.

Question 4

What is an agentic healthcare platform?

Accepted Answer

An agentic healthcare platform is the infrastructure layer that lets AI agents — built for payers, providers, labs, and patients — act safely across organizational boundaries. Every actor in healthcare is gaining an agent, and those agents break the moment they need to read a record, verify identity, or trigger a workflow at another organization. 1health provides the shared patient data, identity, governed access, and stateful workflows those agents need to actually function, with a complete audit trail of every action. It's the same infrastructure developers use to ship patient-facing and provider-facing apps to production.

Question 5

How do I connect HL7, FHIR, or fax data to a healthcare app?

Accepted Answer

1health's Conduit service turns HL7, FHIR, HIE, ADT, fax, and SFTP feeds into structured data your app can read and write. Every legacy system becomes an MCP node on the network without code changes on the sending side. You connect once, and the data flows into the same canonical model the rest of the platform uses. An app can act on inbound records the day it launches, instead of building point-to-point integrations for each source.

Question 6

How do I automate cross-organization healthcare workflows?

Accepted Answer

1health's Workflow Builder authors multi-step, cross-organization automations in natural language. It is the engine that acts on data after Conduit brings it in, triggering events, notifications, and actions across the organizations on the network. Because every step runs on the shared data model with identity and consent already resolved, a workflow can span a hospital, a practice, and a payer without custom middleware. Teams go from spec to a production workflow in days.

Question 7

What is a provider directory API for healthcare?

Accepted Answer

1health's Atlas is a live directory of providers and NPI-verified organization relationships, covering more than two million providers. Your app can look up a provider, confirm their organization, and resolve the relationships between entities through one API. The directory stays current as the network grows, so you never maintain your own copy of provider data. It is the backbone that lets a workflow route to the right provider at the right organization.

Question 8

How do I manage identity and consent for a healthcare app?

Accepted Answer

1health handles identity with Roster and consent with Grantor. Roster provides verified, auditable, and revocable identity for every actor in healthcare — people, legacy systems, and agents — with SSO, MFA, and org membership built in. Grantor codifies who may access what data, for how long, and for what purpose. Together they give your app production-grade access control and consent governance without building an auth and permissions stack from scratch.

Questions developers and partners ask first.