Platform
Interoperability isn't a feature here. It's the design constraint everything else fits inside.
Most EHR vendors treat their API, patient data access, and export path as things a customer earns by paying more. We built the opposite way around: those are fixed, and everything else — SSO, white-labeling, premium portal features — is what actually varies by tier.
Instant, self-serve developer access
Sign up, accept a click-through developer agreement, get API keys — no manual review, no paid NDA, no sales call. Most of the EMR market gates this behind exactly one of those.
Patient and EHI access, never gated
Patient API access and EHI export are outside our commercial tiers entirely — not a Starter-tier limitation, not an Enterprise-only unlock. It is the same on every plan.
Built on live standards, not a roadmap
FHIR R4, USCDI v3, and Facilitated FHIR over TEFCA (via a Health Gorilla QHIN Subparticipant relationship) — the current, in-force technical framework, not an aspirational future one.
Migration
Bring your data. All of it.
Switching EHRs today routinely costs a practice $50K–$500K and six to eighteen months — and some vendors charge separately just to release a practice's own records. We built dedicated import tooling for the systems practices are actually leaving, plus a generic standards-based path for everything else, so migration is a project, not a negotiation.
| Coming from | Path |
|---|---|
| Tebra / Kareo | Purpose-built importer |
| DrChrono | Purpose-built importer |
| ModMed | Purpose-built importer |
| Everything else | Standards-based generic import path |
Under the hood
What "interoperable" actually means here
- Certified API — §170.315(g)(10)-scoped FHIR API, bulk export, and CCDA, licensed identically across every paid tier.
- EHI export — a full patient-record export path, built to actually work as certified, not as a nominal checkbox.
- Claims layer — abstracted over the clearinghouse (not hard-coupled to one partner), so a network-level outage doesn't strand your billing.
- Network exchange — a self-built Facilitated FHIR client, connected as a Subparticipant under a QHIN, rather than a third-party integration aggregator sitting in between.
- Lab connectivity — FHIR-first (
DiagnosticReport/Observation), with HL7v2/SFTP as the fallback for labs that don't yet support it.