Health Cloud explained

What Salesforce Health Cloud adds to core CRM for providers and payers, how it connects to EHRs, and what to plan before you start.

Type
Product guide
Topic
Industry clouds
Reading time
4 min
Updated
Author
GeekMidst Team
Reviewed by
Site owner
Banner for the GeekMidst product guide “Health Cloud explained”, covering What it adds on top of Sales and Service Cloud and Who it suits

Health Cloud is Salesforce's industry cloud for healthcare organisations such as providers and payers. It adds a healthcare data model and processes on top of the CRM capabilities found in Sales Cloud and Service Cloud, so teams can manage patients, members, referrals and care programmes without forcing clinical concepts into generic objects. This guide covers what it adds, who it suits and how to plan.

What it adds on top of Sales and Service Cloud

Industry clouds run on the Salesforce Platform alongside core CRM, so they share the same users, security model, automation tools and reporting as Sales Cloud and Service Cloud. Health Cloud adds healthcare-specific structure. Salesforce documents:

  • A data model aligned to FHIR R4 and HL7 standards, which makes it easier to exchange data with clinical systems.
  • Bi-directional EHR integration via MuleSoft Direct for Health, so records can flow between Health Cloud and electronic health record systems.

Salesforce's Winter '27 release highlights list referral management with Tableau Next dashboards, a payer contact centre voice agent and a Care Gap Closure dashboard. Confirm the status and licensing of each in the release notes before building plans on them.

Who it suits

Health Cloud suits organisations that need to coordinate patient or member engagement across teams: provider networks managing referrals and outreach, payers running member service contact centres, and care programmes that need a shared view of the person. It is not a replacement for an EHR; the clinical record usually stays in the EHR, with Health Cloud handling engagement, coordination and service.

How it connects with Data 360, Agentforce and Marketing Cloud

  • Data 360 can unify data from EHRs, claims and engagement channels into profiles for segmentation and analytics. Our Data Cloud consulting covers this design.
  • Agentforce can support service teams, as the payer voice agent shows. In healthcare, agent design must respect strict access rules and minimum-necessary data. See Agentforce and AI automation.
  • Marketing Cloud can run outreach such as reminders and programme communications, provided consent and data-use rules are designed carefully.

Planning considerations

Data model fit comes first: map your patients or members, providers, programmes and referrals to the FHIR-aligned model, and decide which system owns each data element. Integration is usually the largest workstream, so scope EHR and claims interfaces early. Plan privacy controls, field-level security and audit needs with your compliance team from the start.

Licensing questions to ask Salesforce:

  • Which core CRM licences and editions does Health Cloud assume?
  • Is MuleSoft Direct for Health included or a separate product?
  • Are Tableau Next dashboards and voice agents part of the package or add-ons?
  • What compliance commitments and data residency options apply in your region?

Common mistakes and how to avoid them

MistakeBetter approach
Copying the EHR into SalesforceBring in only the data needed for engagement and coordination
Building custom clinical objectsStart from the FHIR-aligned standard model
Underestimating integrationScope EHR and claims interfaces in the first phase
Adding AI before access rules are settledAgree data access and audit requirements first

How GeekMidst can help

We can help you scope Health Cloud, map your data to the model, design EHR and claims integrations and plan a phased rollout. See our healthcare page, our integration services and our data migration services.

Questions we hear

Does Health Cloud replace our EHR?
No. It is designed to work alongside an EHR, with bi-directional integration rather than replacement.
Why does FHIR matter?
A FHIR R4-aligned model reduces the translation work when exchanging data with clinical systems.
Do we need MuleSoft?
Salesforce documents EHR integration via MuleSoft Direct for Health. Ask Salesforce how it is licensed for you.
Can payers and providers both use it?
Yes. Salesforce positions it for both, with features such as the payer contact centre voice agent.

Planning Health Cloud?

Tell us about your processes, systems and timeline, and we will help you work out whether Health Cloud fits and what a sensible first phase looks like.

Talk to us →

Tell us what you are trying to fix.

Share your Salesforce setup, goals and constraints. A practitioner reads every message and replies with questions, first thoughts or an honest view of whether you need outside help at all.

Talk to a Salesforce Expert
Book a Consultation