A search for "Salesforce EHR integration cost" produces numbers that look precise and usually describe different projects. Some assume read-only FHIR. Some mean one endpoint. Some include middleware but exclude vendor fees. Some price a demo without production monitoring, reconciliation, or post-launch ownership.
Behavioral-health operations make those differences material. An admission can include a patient, episode of care, emergency contact, insurance context, screenings, agreements, and returned verification-of-benefits documents. The cost question becomes useful only after the workflow is put into one of three shapes.
The three project shapes
| Shape | Fits when | What increases scope |
|---|---|---|
| Admission push | Salesforce owns the admissions funnel; the EHR needs a ready record at one milestone | Multiple record types, documents, repeat admissions, and partial-failure recovery |
| Real-time sync | Clinical staff work in the EHR while Salesforce must reflect patients and appointments continuously | Two-way writes, conflict rules, identity, burst volume, replay, and monitoring |
| Operating layer | The EHR remains clinical truth while Salesforce supplies census, VOB, referral, document, or attribution workflows | Facilities, workflow variants, reporting, historical data, and multiple surrounding systems |
GAT has shipped each pattern. The Opus Behavioral Health EHR build is a milestone-based admission push. The AdvancedMD build is a real-time event-driven sync with MRN writeback. The broader behavioral-health proof library includes census, VOB, documents, and intake automation around the EHR.
The seven cost drivers
01
Vendor access
API entitlement, writable endpoints, developer agreements, sandbox access, certification, and vendor support.
02
Direction
One-way milestone push, inbound event mirror, or continuous bidirectional synchronization.
03
Identity
Patient matching, MRN or external-ID writeback, repeat admissions, householding, and duplicate resolution.
04
Payload
Demographics, appointments, episodes of care, contacts, insurance, documents, and clinical or operational fields.
05
Reliability
Idempotency, retries, error queues, reconciliation, replay, alerts, and a support procedure for partial failure.
06
Regulated workflow
Minimum-necessary data, credential handling, access controls, logging boundaries, test data, and the client's compliance review.
07
Ownership
Documentation, admin-managed mappings, monitoring, hypercare, vendor changes, and who responds when an endpoint moves.
Vendor access can change the project before development starts
"The vendor supports FHIR" does not prove that an admissions workflow can write records. AdvancedMD states that its regulatory FHIR implementation is read-only. Transactional writeback uses its proprietary Connect APIs and requires a developer agreement, licensing and support fees, sandbox work, and a successful production demonstration. See the AdvancedMD FHIR guidance and developer onboarding requirements.
That access work belongs in the estimate. So do the vendor's recurring fees. GAT separates third-party licenses and API charges from implementation fees so a buyer can see who owns each cost.
Salesforce licenses are separate from implementation
Salesforce currently lists Health Cloud Enterprise at $350 per user per month and Unlimited at $525 per user per month, billed annually. Those are platform license prices, not an integration estimate. See Salesforce Health Cloud pricing.
Health Cloud is also not automatically required. If Salesforce owns referral, admissions, communication, or operational reporting while the EHR owns clinical documentation, core Salesforce can be the lighter operating foundation. The right comparison includes license cost, implementation burden, data model fit, and the client's ability to own the result.
API headroom belongs in the estimate
Salesforce says paid org editions such as Enterprise begin with a 100,000-request rolling 24-hour API allocation that increases with licenses. The limit is soft until platform protection is enforced, but normal operations should not be designed around an overage. See Salesforce's API-limit and monitoring guidance.
A production estimate should include normal volume, bursts, retries, replay, reconciliation, and other integrations already consuming the org's allocation. The value is not "using no APIs." It is preserving headroom by avoiding unnecessary polling, consolidating work where appropriate, and making failure recoverable.
What a defensible fixed price needs
- The source and destination systems, environments, and API entitlements.
- A system-of-record decision for patient, appointment, episode, document, and operational data.
- Direction, trigger moments, volumes, payloads, and historical-data requirements.
- Identity, duplicate, retry, partial-failure, reconciliation, and alerting rules.
- Security, test-data, access, vendor-agreement, and compliance-review dependencies.
- Acceptance tests, launch plan, hypercare, documentation, and post-launch owner.
The Behavioral Health Integration Fit Check confirms the first-order facts. When the workflow needs deeper discovery, GAT scopes a paid Blueprint before the build: record ownership, field and event map, API budget, failure model, implementation backlog, and fixed proposal.
Frequently asked questions
How much does a Salesforce–EHR integration cost?
The honest answer depends on the integration shape, writable API access, identity matching, documents, data volume, security controls, testing, and post-launch ownership. A one-way admission push has fewer moving parts than a continuous bidirectional sync. GAT confirms those facts before offering a fixed scope and price.
Is the EHR vendor's API included in the implementation price?
Not always. Some vendors charge separately for API licensing, sandbox access, certification, or ongoing support. Those are vendor costs, not consulting fees, and should be confirmed before the implementation is priced.
Do we need Salesforce Health Cloud for an EHR integration?
Not necessarily. Health Cloud can be valuable when its healthcare data model and care capabilities fit the operating model. Core Sales or Service Cloud can be the better foundation when Salesforce owns admissions, referrals, communication, or non-clinical operations while the EHR remains the clinical record.
Is bidirectional integration always better?
No. Every additional direction creates more ownership, identity, conflict, retry, and reconciliation decisions. Many behavioral-health operators need one direction done reliably at a clear milestone, not two directions synchronized indiscriminately.
Can GAT provide a fixed price?
Yes, after the workflow and API access are understood. The Fit Check identifies the likely shape and blockers. A paid Blueprint can then define the system-of-record matrix, field and event map, failure model, implementation backlog, and fixed build proposal.