Insights

EHR and Salesforce Integration Checklist

A practical checklist for connecting Epic, Oracle Health or another EHR to Salesforce, covering data, standards, identity, security, testing and support.

Interoperability
Interoperability8 min readNovember 16, 2026Selah Digital Team
Share

Before you start

Name the workflows the integration serves. An integration built to support post discharge outreach needs different data and timing than one built for a contact center console. Write down who in Salesforce will use the data, what decision it supports and how quickly it needs to arrive.

Bring your EHR team, privacy officer and security team in early. Interface requests often join a long queue, and security review can take weeks.

Data and ownership

List every data element and agree a minimum necessary set for each use case. For each element, record the system of record, whether Salesforce reads it or also writes it, and how conflicts are resolved. Decide how long the data is kept in Salesforce and whether it can be shown, reported on or used in outreach.

Standards and interface types

Confirm what your EHR supports. Options usually include FHIR R4 APIs, HL7 v2 messages such as ADT and scheduling feeds, vendor specific APIs and file based exports. FHIR is the better choice for request and response access to specific resources. HL7 v2 feeds remain common for real time events such as admissions and discharges.

Check whether your EHR vendor requires a registered application, client credentials or a specific approval process for API access, and how long that takes.

Patient identity

Decide how records are matched: MRN, enterprise master patient index identifiers, or demographic rules. Plan for patients with several MRNs, merged records and people who exist in Salesforce before they exist in the EHR. Build a review queue for uncertain matches.

Architecture

Choose where integration logic lives: MuleSoft, your existing integration engine, or a cloud service. Separate EHR specifics from Salesforce logic so either side can change later. Plan for retries, ordering of events, duplicate messages and outages on either side.

Security and compliance

Confirm that business associate agreements are in place with every vendor that will handle PHI. Use encryption in transit, scoped credentials stored securely and least privilege access in Salesforce. Log access to sensitive data and decide who reviews those logs.

Testing

Test with realistic volumes and messy data, not just clean samples. Include merges, cancellations, corrections and late arriving messages. Have clinical and operational users confirm that what they see in Salesforce matches what they expect from the EHR.

Support after go live

Set up monitoring and alerts for failed messages and stalled queues. Write runbooks that explain how to diagnose and replay failures. Agree who is on call for the interface, and how EHR upgrades and Salesforce releases will be tested before they reach production.

Ready to start?

Talk with the people who will do the work.

From the first conversation to go live, you work with our delivery team. No account-manager handoff, and no surprises.