EleplanConnect
Patient-directed health records API · Early access

Every patient's records,
one sign-in away.

Put a provider search inside your product. Your user picks their hospital or clinic and signs in to its own patient portal, and their records come back as FHIR R4. We built and run our own SMART on FHIR connector, with no aggregator in between.

Request early accessCheck your provider
Connectable organizations
137,106

organizations you can connect today

FHIR endpoints
37,551

FHIR endpoints in the catalog

Health checks
Hourly

health-check runs across the catalog

Eleplan
Select your provider
Search 137,000+ hospitals and practices
Mayo Clinic
Cleveland Clinic
Kaiser Permanente
Johns Hopkins
NYU Langone
Mount Sinai
Stanford Health
Medicare
VA
Secured by Eleplan Connect
Connects directly toEpicOracle HealthathenahealtheClinicalWorksNextGenVeradigmMeldRxMedicareVA
Coverage

The widest patient-access network we know of.

We rebuild the provider catalog every night from vendors' own endpoint directories and ONC's national list, then run health checks every hour, cycling through every endpoint. An organization counts as connectable only when we're registered with its EHR vendor and its endpoint is answering.

Eleplan Connect137,106
Largest other published count¹70,000+
Next published count²50,000+

Organizations offering patient-access sign-in, as each company publishes them. ¹ A consumer health-records API, August 2026, including TEFCA. ² A consumer health-records API, January 2026. Eleplan's count is from our catalog, October 2026.

152,508
organizations in the catalog
122
EHR vendors mapped
+ Medicare, VA
nationwide, one sign-in each
Check your coverage

Is your users' provider on the network?

Search any hospital, health system or practice by name, or enter a ZIP to see who connects directly nearby. No account needed.

Why it works

Direct connections, so your users don't hit dead ends.

Our own connector

We registered our app with each EHR vendor ourselves, using SMART App Launch 2.0 with PKCE and signed client assertions. No reseller sits between you and the hospital.

Only what works is shown

Health checks run every hour, cycling through every endpoint. An organization whose server is down drops out of search until it answers again, so users never meet a sign-in that can't finish.

Everything kept, codes included

Records arrive as FHIR R4: conditions, medications, labs, immunizations, visits, documents and claims. Every coding is kept, and records refresh before the patient's access expires.

How it works

Four steps. You build one of them.

  1. 01 · Your server

    Create a session

    One API call with your secret key and your own user ID returns a short-lived, single-use session.

  2. 02 · Your page

    Open the picker

    Drop in the embed. Your user searches by name or ZIP and sees who connects directly near them.

  3. 03 · Their portal

    They sign in, and consent

    On MyChart or their provider's own portal, in a real browser window. They see exactly who receives their records.

  4. 04 · Records

    FHIR, kept current

    A signed webhook tells you when records are ready. Pull them as FHIR R4; we keep them current every day.

Developers

Ship it in an afternoon.

A server call, a script tag and a webhook. Sandbox keys connect to vendor test systems and synthetic patients, so you can build without touching real records.

  • Sessions are single-use and expire in 15 minutes
  • The embed only frames on origins you register
  • Webhooks are signed; status messages carry no PHI
server.js · create a session
// ELEPLAN_CONNECT_API comes with your keys (early access).
const res = await fetch(`${process.env.ELEPLAN_CONNECT_API}/v1/sessions`, {
  method: 'POST',
  headers: { Authorization: `Bearer ${process.env.ELEPLAN_SECRET_KEY}` },
  body: JSON.stringify({ external_id: user.id, origin: 'https://app.acme.com' }),
});
const { session } = await res.json(); // ecs_… · single use · 15 min
page.html · open the picker
<script src="https://cdn.eleplan.com/connect/v1/connect.js"></script>
EleplanConnect.open({ session, onStatus: (s) => console.log(s.status) });
webhook · connection.ready
{ "type": "connection.ready", "connection_id": "conn_8f2c…",
  "external_id": "user_1042", "resources": 1873 }
Security

Built for health data from the first line.

Patient-directed, always

Every connection is the patient signing in under their HIPAA right of access. We never pull records on anyone else's say-so.

You never hold their tokens

Sign-in codes and refresh tokens stay sealed on our servers, encrypted with AES-256-GCM. Your app gets records, never credentials.

Locked to your origins

Secret keys work only from your server. The embed frames only on origins you register, and talks only to them.

HIPAA-grade infrastructure

HIPAA-eligible AWS under a signed BAA, with storage encrypted under our own keys. We sign a BAA with every partner that receives records.

Reviewed partners only

Every partner is verified and approved before getting a key, with sandbox first and production after review.

Audited end to end

Every connection, sync and export is attributed to the key that caused it. Webhooks are signed and replay-protected.

Build on the widest records network.

Early access is open to digital-health companies and care organizations. Tell us what you're building.

Request early access