The easiest way to connect to major EHRs: direct APIs, aggregators or national networks

There are three ways to connect a product to major EHRs: build directly on each vendor's APIs, buy one API from an integration platform, or retrieve records through a national network. Each is easiest for a different job.

In short

  • The easiest way to connect to major EHRs depends on the job: national networks such as TEFCA are easiest for retrieving a patient's records from many organizations, an integration platform is easiest for one API across many vendors, and direct vendor APIs are easiest when you need deep workflow in one EHR.
  • Direct connections rest on a federal floor, since certified EHR APIs must support FHIR R4, US Core and SMART App Launch and publish their documentation, terms and endpoints.
  • No route removes the health system's own decision about what your product may read and write, so pick the route by the data you need and where it has to land.

The easiest way to connect to major EHRs depends on what you need from them. To retrieve a patient's records from many organizations, a national network is easiest. To read and write through one API across several EHR vendors, an integration platform is easiest. To work deep inside one EHR's workflow, such as launching inside the clinician's screen or filing data to specific places in the chart, going direct to that vendor's APIs is easiest.

Most products end up combining two of these. For a vendor-by-vendor look at integration platforms, see our comparison of Redox, Health Gorilla and 1upHealth.

What are the three ways to connect to an EHR?

  • Direct: your product connects to each EHR vendor's APIs, registers with each vendor's developer program, and goes live with each health system that runs it.
  • Aggregator: your product connects once to an integration platform, which maintains connections to many EHRs and translates between them.
  • Network: your product, or a partner acting for it, joins a health information network that lets participants request a patient's records from other participants for a stated purpose.

They solve different problems. Direct and aggregator routes connect you to a specific organization's EHR for ongoing work. A network connects you to many organizations at once, mostly for record retrieval.

When is a direct connection the easiest route?

Direct is easiest when your customers run one or two EHRs and your product needs workflow that only the vendor's own APIs offer. A clinician tool launched inside Epic with the patient in context, or a monitoring product filing readings to flowsheets, is a direct-connection product.

The federal floor makes the first step more predictable than it used to be. EHRs certified to ONC's §170.315(g)(10) criterion must support FHIR R4, US Core and SMART App Launch for single patients and groups, with documentation at a public link. Under the API Conditions of Certification at 45 CFR 170.404, certified API developers must publish their terms and fees, verify API users within ten business days, register apps for production within five business days after that, and publish patient-facing service base URLs at no charge.

Vendor programs add the rest. Epic's open.epic, for example, has no membership fee, offers public APIs, a sandbox and data sharing playbooks, and lists self-service client registration. Its optional Vendor Services program costs $1,900 a year and adds private APIs and paid support. Then each Epic customer requests the app's client ID for its environment and enables the APIs you use.

  • Easiest for: deep workflow in one EHR, launches inside the clinician's screen, specific write-back.
  • Hardest part: repeating vendor registration, testing and keys for every EHR you add.
  • You own: the code for each vendor, version changes, and each health system relationship.

When is an integration platform the easiest route?

An aggregator is easiest when your customers run many different EHRs and your product needs the same data from all of them. You build against one API and one data model, and the platform maintains the connections and translations. That saves the most effort when the vendor count is high and each connection is shallow.

Check three things before you commit. First, which EHRs and which data the platform supports for your use case, including writes. Second, what happens at each health system, because the organization that runs the EHR still decides what any connection may do. Third, what you pay as volume grows, since the platform's fees become a permanent cost of every connection.

  • Easiest for: many EHR vendors, the same reads everywhere, small engineering teams.
  • Hardest part: features the platform does not support, and being tied to its data model.
  • You own: the platform contract, a BAA with it, and the health system relationships.

When is a national network the easiest route?

A network is easiest when you need a patient's history from organizations you have no relationship with. ONC describes TEFCA as a nationwide framework for health information sharing. Qualified Health Information Networks, or QHINs, are its central connection points, and participants connect to QHINs. The Sequoia Project serves as the Recognized Coordinating Entity under a five-year contract with ONC awarded in August 2023, and the first QHINs were designated in December 2023.

TEFCA's initial exchange purposes are treatment, payment, health care operations, public health, government benefits determination and individual access services. ONC notes that the purpose must be indicated in each request. In practice, your product needs a valid purpose for every query.

You do not have to become a QHIN to use one. Health Gorilla, a designated QHIN, says customers connecting through it get TEFCA exchange without their own agreement with the RCE, that it enforces permitted purposes during request processing, and that responses are normalized into FHIR resources with provenance metadata, returned synchronously or pushed through FHIR Subscriptions. It also notes reciprocity: customers must share data such as encounter data and lab results to access records from other QHINs. CommonWell Health Alliance also presents itself as a designated QHIN, listing services such as a master person index and a record locator service.

  • Easiest for: retrieving history across many organizations, care coordination, individual access apps.
  • Hardest part: patient matching, reciprocity, and documents that vary in structure.
  • Not built for: launching inside a clinician's screen or writing into a specific organization's chart.

How do the three routes compare?

  • Reach: networks reach the most organizations, aggregators reach the EHRs they support, direct reaches one vendor at a time.
  • Depth: direct goes deepest into one EHR's workflow, aggregators cover common data well, networks mostly return records.
  • Write-back: direct offers the vendor's write APIs, aggregators offer what they have built, networks are not a write-back tool.
  • Approval: every route still depends on the organizations whose data you use, and each route adds its own agreements.
  • Lock-in: direct ties you to vendor APIs you can read and test yourself, aggregators tie you to a platform's model, networks tie you to a QHIN's terms and the Common Agreement.

How do you choose for your product?

Start from the data. For each feature, write down the data it needs, whether it reads or writes, which organizations hold the data, and where in their workflow the result must appear. The answers usually point to the route.

  • A patient app that shows records from every place the patient has been: network, through an individual access services path.
  • A care coordination tool that needs history before a visit: network for retrieval, plus a direct or aggregator connection for the home practice.
  • A remote monitoring product that files readings for clinicians: direct, or an aggregator only if it supports the specific writes.
  • A product sold to practices on many different EHRs that needs the same reads everywhere: aggregator.
  • A clinician tool used inside one EHR: direct.

Keep your own data model in the middle whichever route you pick. Map each route's data into it at the edge, so you can add a second route or switch vendors later without rewriting the product.

What does every route still leave to you?

Security, consent and support. Every route puts PHI in your product, so you need BAAs with each party that handles it, encryption, access control and an incident plan. We sign a BAA before anyone on our team sees PHI, run a penetration test before launch, and scope access so each clinician sees only their own patients.

We have shipped Epic and athenahealth integrations, and for any vendor platform or network we work from the vendor's documentation and sandbox. If you are deciding how to connect your product to the EHRs your customers run, talk to one of our engineers. Our free five-day technical audit ends with a written report that maps each feature to a route.