EHR integration with Salesforce means moving data between your electronic health record and Salesforce through an interface, usually HL7 messages or a FHIR API, with something in the middle that translates and checks the data. Salesforce does not read an EHR on its own. The cost comes from four things: licenses, the integration tooling, the build effort, and the support you need after go-live. Nobody can honestly quote a number without knowing your EHR, your volume and which data you actually need.
This guide explains how the pieces fit, what drives each cost, and the questions to answer before you ask for a quote. It is general information, not legal or compliance advice.
What EHR integration actually means
Your EHR is the system of record for clinical care: visits, diagnoses, medications, results. Salesforce is usually where your care coordination, outreach, referrals and program tracking live. Integration connects the two so staff don't type the same information twice and can see what happened at the clinic or hospital.
Most organizations don't need the whole chart. They need a short list: who was seen, when, a flag that a visit or discharge happened, maybe diagnoses or a few results. Deciding that list first is the biggest cost saver in the project.
The two ways data moves: HL7 and FHIR
Health systems send data in two common ways. We cover the difference in detail in HL7 vs FHIR, so here is the short version.
- HL7 version 2 is a stream of coded messages sent when something happens, such as an admission or discharge. Your source pushes them to you.
- FHIR is a web API. You (or your integration) ask for a type of record, such as a Patient or an Encounter, and the system answers.
Which one you use depends on what your EHR vendor, hospital or health information exchange offers you. US federal certification rules require certified EHRs to offer a standardized FHIR API for patient and population services (ONC, 45 CFR 170.315(g)(10) resource guide, checked November 2026). Having the API available does not mean the vendor will turn it on for you, or at no charge, so ask.
How Salesforce receives the data
Salesforce needs three things whichever standard you pick:
- A place to put the data. A standard nonprofit org has no objects for encounters, diagnoses or medications. Salesforce Health Cloud includes a clinical data model built to align with FHIR R4, and Salesforce documents how FHIR resources map to its objects (Health Cloud developer guide, FHIR mapping, checked November 2026). Salesforce notes that its model supports most, not all, FHIR R4 attributes. Without Health Cloud, you build custom objects instead. See Health Cloud for community health organizations for when each makes sense.
- A translator in the middle. HL7 messages and FHIR resources have to be mapped to Salesforce fields. This can be an integration engine your hospital or HIE already runs, an integration platform such as MuleSoft, or custom code.
- Rules for conflicts and errors. What happens when the EHR and Salesforce disagree? What happens when a message fails? Decide this early.
MuleSoft publishes an Accelerator for Healthcare with prebuilt templates, including HL7 v2 and FHIR R4 options for bringing EHR patient data into Health Cloud, with Epic and Cerner named as examples (MuleSoft documentation, checked November 2026). It is a head start, not a finished integration. The docs we reviewed don't cover licensing, so ask MuleSoft or Salesforce about that.
What drives the real cost
We won't quote dollar figures, because they vary too much to be useful. Here are the drivers, roughly in the order they surprise people.
- Licenses. Salesforce licenses for the people who use the data. If you choose Health Cloud, its licenses cost more than standard ones. We could not confirm that Health Cloud is part of Salesforce's nonprofit discount program, so ask your Salesforce account executive for current terms.
- Interface and integration engine fees. Your EHR vendor or HIE may charge to set up and maintain an interface. An integration platform has its own subscription. Ask each one in writing.
- Build effort. Data modeling, mapping every field, security setup, testing with realistic data and a go-live plan. HL7 mapping is most of the work. On a project connecting a community health center to its regional exchange, we mapped every HL7 segment to its place in Salesforce before anyone built anything, so the integration team knew exactly what to send where.
- Ongoing support. Interfaces break when an EHR upgrades, a code set changes or a certificate expires. Someone needs to watch the error log and fix problems.
- Your own staff time. Clinical, compliance and IT people have to review mappings and test. This is real cost even when it isn't on an invoice.
Security and privacy come first
Health data in Salesforce is protected health information (PHI) if you are a covered entity or business associate. Salesforce offers a Business Associate Addendum for a defined list of "HIPAA Covered Services," and the list changes, so confirm that every product you plan to use is on it (Salesforce BAA restrictions page, checked November 2026). Salesforce's own FAQ says customers remain responsible for their own compliance.
Before any data flows, limit who can see it. A secure integration user, minimal permissions and a review of broad permissions such as View All Data matter. We walk through this in Salesforce permissions and PHI.
A practical plan before you ask for quotes
- List the data you need and why. Each field you skip is cost you avoid.
- Ask your source what it can send. HL7 feed, FHIR API, or neither? What does it cost?
- Decide the direction. Read-only into Salesforce is far simpler than two-way sync.
- Choose where the data lives. Health Cloud's clinical model or custom objects.
- Plan for errors and ownership. Who watches failures? Which system wins a conflict?
- Start small. One feed, one use case, then expand.
Frequently asked questions
Does Salesforce integrate with Epic or other EHRs?
Yes, through interfaces. Salesforce and MuleSoft provide templates that name Epic and Cerner as examples, but each connection still needs configuration, EHR vendor approval and testing for your organization.
Do I need Health Cloud for EHR integration?
Not always. Health Cloud gives you a clinical data model, but you can integrate into custom objects if you only need a few data points. It depends on how much clinical data you want to store and use.
Is HL7 or FHIR cheaper?
It varies. The cheaper path is usually whichever your source already offers and your partner already knows how to run. See HL7 vs FHIR.
How long does it take?
It depends mostly on the EHR vendor's or HIE's timeline for turning on an interface, and on how many data types you need. Ask them first, because that wait often sets the schedule.
Is this HIPAA compliant?
HIPAA depends on your agreements, policies, training and configuration, not just the software. Work with your compliance lead or attorney.
Talk it through with us
If you're weighing an EHR connection, we can review what your source can send, what Salesforce needs, and where the cost will land. Book a free Salesforce health check.