Epic Data In.
Health Cloud Native.
Pull Epic patients and encounters straight into Salesforce Health Cloud — enriched FHIR R4, mapped to the native EHR data model, and upserted by source ID. No middleware. No nightly ETL. No second copy of the chart to reconcile.
Your team needs Epic's clinical data inside Salesforce — but standing up middleware and reconciling a second copy of the chart shouldn't be the price of admission.
Epic Patient Connect is a clinical data pipeline built natively on Salesforce. It reads patients and encounters from Epic over FHIR R4, enriches each with its conditions, practitioners, locations, and organizations, and upserts them onto Health Cloud's native EHR objects — keyed by source ID, so every run updates instead of duplicating. Nothing to sync by hand, nothing to reconcile, nothing leaving your org.
Built on FHIR. Landed Native.
Integration isn't just moving JSON from point A to point B. It's calling Epic's R4 endpoints, resolving the references each resource points to, mapping every code and value onto the right Health Cloud field, and upserting on a stable key so reruns stay clean. Epic Patient Connect owns that plumbing — a reusable R4 client, resource parsers, and a chained-queueable engine — so the data just shows up, correct.
What it does
Rekeyed charts, stale extracts, and brittle nightly jobs aren't integration.
They're risk.
Patient Create, Search & Read
Create patients in Epic from Salesforce, search on the demographics you already have, and read the chart back — so a patient in your org and the patient in Epic are one person, linked by a stable ID.
Encounters, Fully Enriched
Every encounter arrives with the context that makes it useful — conditions, practitioners, locations, and organizations resolved and attached — then mapped onto Health Cloud's EHR graph, not a flat, lonely visit row.
A Live Clinical Snapshot
See the patient's current state pulled live from Epic — allergies, problems, medications, vitals, and recent labs — right on the Account page. A read-through view that's always current, with nothing stored to go stale.
Speaks FHIR R4 Natively
One R4 client handles auth, token refresh, and every search — patients, encounters, observations — and lines up with Health Cloud's own R4 data model out of the box.
Upserts, Not Duplicates
Every record is keyed by its Epic source ID, so a second run updates what's already there instead of piling on copies. Reruns are safe, imports are idempotent, and your EHR data stays clean.
Lands on Native EHR Objects
Patients and encounters map onto Health Cloud's standard EHR objects — the same records, sharing rules, and reports your org already uses. No custom shadow schema, no data leaving the platform.
Put Epic's data where you work.
See Epic Patient Connect pull real patients and encounters into Health Cloud — enriched, mapped, and upserted onto your own data model, inside the org you already own.