Salesforce · Healthcare · Agentforce Health

Salesforce Health Cloud in 2026: Features, EHR Integration, Pricing and HIPAA

Health Cloud is now called Agentforce Health, it no longer installs as a package, and its clinical data now sits in FHIR R4-aligned standard objects. Here is what the platform does today, how it connects to Epic and Oracle Health, how setup works, what it costs, and what a BAA does and does not cover.

Key Takeaways

  • Salesforce Health Cloud, renamed Agentforce Health, is a healthcare CRM on the Salesforce platform. It sits beside the EHR and does not replace it.
  • Since Summer '24, new customers no longer get a managed package. Health Cloud features are part of the platform, and patients are modelled as person accounts.
  • Clinical data lives in standard objects aligned with FHIR R4, fed from Epic, Oracle Health and other EHRs through FHIR APIs, HL7 v2 feeds or MuleSoft.
  • List prices run from $350 to $725 per user per month, billed annually, with add-ons for portals, MuleSoft Direct, Provider Network Management and analytics.
  • HIPAA coverage needs a signed BAA, covered services only, encrypted PHI, and Einstein Trust Layer data masking whenever Agentforce touches patient data.

What is Salesforce Health Cloud? Salesforce Health Cloud is a healthcare-specific CRM built on the Salesforce platform and now sold as Agentforce Health. It gives providers, payers, home health and medtech teams one patient or member record that combines clinical data from the EHR with contact history, care plans, programs, referrals, authorizations and service cases, plus workflows and AI agents that act on that record.

We first published this article in August 2024. This version replaces the old package-era setup steps, an unsourced statistic and a list of hospital examples we could not verify with Salesforce's current documentation, pricing page and Business Associate Addendum terms, all checked in November 2026. It is written for operations, IT and patient-access leaders at growing and mid-market healthcare organizations, from multi-site clinics to regional health plans, and for the admins who will configure the platform.

Section 01 · Short Answer

What Does Salesforce Health Cloud Actually Do?

It runs the relationship and operational side of care on top of the clinical record. The EHR stays the system of record for charting, orders and results. Health Cloud pulls the clinical context it needs from the EHR, then manages everything around it: intake, referrals, scheduling, care coordination, programs, member service, utilization management and outreach. Salesforce's own setup guide describes the work as mapping clinical data from a source EHR into Health Cloud objects.

Features of Salesforce Health Cloud: enhanced patient experience, care plan creation, 360-degree patient insight, real-time interaction, EHR integration, personalized engagement and tailored patient programs

Providers

Hospitals, clinics and specialty groups use it for patient access, referrals, intake, scheduling and care coordination across sites.

Payers

Health plans use it for member service, care management, utilization management, prior authorization and provider networks.

Home health and medtech

Home health agencies schedule visits and track care in the field; medtech teams run patient programs and support.

Section 02 · What Changed

What Has Changed in Health Cloud Since 2024?

Four things: the name, the delivery model, the data model and the AI layer. Health Cloud is now Agentforce Health in Salesforce Help, though pricing pages still say Health Cloud. New customers no longer install a managed package. Clinical data moved to FHIR R4-aligned standard objects. And prebuilt Agentforce health agents now sit on top. Guides written before these changes, including our own 2024 version, describe steps that no longer apply.

TopicOlder guides sayCurrent Salesforce documentation
NameSalesforce Health CloudAgentforce Health (formerly Health Cloud); edition names on the pricing page still say Health Cloud
InstallationInstall the Health Cloud packages from AppExchangeSince Summer '24, new customers cannot access the managed package; features are built into the platform. Customers onboarded earlier keep package access.
Patient recordPatient as an extension of ContactPatients and members are modelled as person accounts. Salesforce says you cannot fully use Health Cloud otherwise.
Clinical dataPackaged EHR objectsSince Spring '23, new customers cannot create records in the packaged EHR objects that have FHIR R4-aligned counterparts; all new development is on the FHIR R4-aligned model.
Care plansA custom Care Plan object with tasksCarePlan is a standard object based on the FHIR CarePlan resource, part of Integrated Care Management. The older care plans are a managed-package feature.
EHR vendor namesEpic and CernerOracle acquired Cerner in 2022 to form Oracle Health; Salesforce integration pages still say "Oracle Cerner"
AIPredictive analytics and NLP in general termsAgentforce Health agent templates and Document AI for Health, under specific BAA restrictions

Sources: Salesforce Help on the Health Cloud managed package, person accounts and the clinical data model.

Section 03 · Data Model

How Does Health Cloud Model Patients and Clinical Data?

In layers: a person account for the patient, FHIR R4-aligned clinical objects for what the EHR knows, care management objects for what the care team plans, and code sets that keep terminology consistent. Salesforce aligns the clinical model with FHIR v4.0.1, with a few documented differences, such as one-to-many attributes modelled as child objects.

Layer 1 · Who

Person accounts for patients, members and independent providers

A person account combines account and contact fields in one record. Contacts to Multiple Accounts lets one person relate to several households, practices or plans. Providers and facilities have their own objects, such as HealthcareProvider and HealthcareFacility.

Layer 2 · Clinical context

FHIR R4-aligned standard objects

ClinicalEncounter covers an encounter from pre-admission to discharge. HealthCondition holds problems and diagnoses. AllergyIntolerance, MedicationStatement, MedicationRequest, PatientImmunization, PatientMedicalProcedure and CareObservation cover the rest. Most need the FHIR-Aligned Clinical Data Model setting turned on in Setup.

Layer 3 · Care

Integrated Care Management, programs and assessments

CarePlan, CarePlanTemplate, goals, problems and interventions model what the team will do, and Salesforce describes this model as both USCDI and FHIR R4-aligned. Care Program objects handle enrolment, eligibility rules and products; Assessments use Discovery Framework and Omnistudio.

Layer 4 · Shared vocabulary

CodeSet and CodeSetBundle

CodeSet stores industry codes with their system and version; CodeSetBundle groups codes from different systems that mean the same thing. Getting these right is what makes reporting and automation reliable across EHR feeds.

Read the full object list in Salesforce's FHIR R4-aligned clinical data model guide, and the HL7 FHIR R4 specification it maps to.

Section 04 · Capabilities

What Features Are Included in Salesforce Health Cloud?

Every edition includes the clinical and insurance data models, Integrated Care Management, utilization management, referral management, appointment management, program enrolment, assessments, identity verification and provider relationship management. Some capabilities that older articles list as standard are add-ons or need Data 360, so check each one against your edition before you plan around it.

Integrated Care Management

Care plans built from templates and a library of problems, goals and interventions, with care episodes and activities the whole team can see.

Care programs and assessments

Enrol patients in programs with eligibility rules, and run guided questionnaires by staff or through a patient portal.

Referrals and appointments

Referral management and Intelligent Appointment Management move a patient from referral to a booked visit with fewer handoffs.

Utilization management

Guided authorization requests for payer and provider offices, with dashboards and prediction of service-level breaches.

Intelligent Document Automation

Extracts values from faxed referrals, forms and lab reports and creates records such as care requests and program enrollees. It needs its own licences.

Unified Health Scoring

Displays risk scores and trends on the patient record. It does not calculate them: scores come from Data 360 or your own scoring logic.

Add-ons to budget for separately: Provider Network Management (credentialing and network data, including NPI registry lookup), MuleSoft Direct for Health Cloud, Experience Cloud for Health Cloud portals on Core and Advanced, Analytics for Health and Life Sciences, and Home Health. Life Sciences Cloud is a separate product with its own pricing.

Section 05 · EHR Integration

How Does Health Cloud Integrate with Epic and Oracle Health?

Through one of three patterns Salesforce documents: read clinical data in real time over FHIR without storing it, ingest HL7 v2 events into the clinical data model, or move bulk FHIR data into Data 360. MuleSoft Direct for Health Cloud provides prebuilt apps for each, and the MuleSoft Accelerator for Healthcare adds reusable APIs and mappings for Epic, Cerner and other systems.

PatternHow it worksBest for
Real-time FHIR read No PHI copyA generic FHIR client retrieves records from the EHR when a user opens the patient, without saving them in Salesforce. Salesforce lists Epic, Oracle Cerner and athenahealth as supported EMRs.Contact centres and care teams that need to see clinical context but not report on it
HL7 v2 event ingestion StoredAdmission, discharge and transfer messages and other HL7 v2 feeds are written into ClinicalEncounter and related objects.Care coordination, discharge follow-up, automation triggered by clinical events
Bulk FHIR to Data 360 AnalyticsLarge FHIR datasets land in Data 360 for segmentation, calculated insights and health scoring.Population health, risk scoring, outreach campaigns

The MuleSoft accelerator also covers lab results, appointment scheduling, benefits and eligibility checks, prior authorization (the HL7 Da Vinci CRD, DTR and PAS guides), and converters from HL7 v2, X12 and C-CDA to FHIR. Its integrations are modular, so you change endpoints and mappings to suit your EHR build rather than starting from zero. See Salesforce's Health Cloud integration apps and the MuleSoft Accelerator for Healthcare documentation.

Practical rule: store in Salesforce only what you will report on, automate from or show offline, and read the rest live. Every clinical field you copy adds PHI to protect, data to reconcile and a mapping to maintain. Twopir Consulting's MuleSoft integration team designs these flows so the EHR stays the clinical source of truth.

Section 06 · Fit

Health Cloud vs Service Cloud: Which Does a Healthcare Organization Need?

Choose Health Cloud when your processes depend on clinical, insurance or care data; choose Service Cloud when you mainly need a contact centre and case management. Health Cloud is built on Service and Sales Cloud, so it includes the console, cases, knowledge and omni-channel routing. HIPAA is not the deciding factor, because Sales Cloud and Service Cloud are also covered services under Salesforce's BAA.

Health Cloud fits. You coordinate care across a team, run care or disease programs, manage referrals into scheduled visits, process authorizations, maintain provider networks, or need diagnoses, encounters and medications next to the service history.

Service or Sales Cloud may be enough. Your work is billing questions, general enquiries, B2B sales to practices, or marketing that never touches clinical data. You can still sign a BAA for these clouds. Revisit the choice when care data enters the process.

Salesforce publishes a comparison datasheet listing the Health-only features: the clinical and insurance data models, Integrated Care Management, utilization management, integrated assessments, unified patient and member profiles, provider relationship management, prebuilt healthcare agents, appointment and referral management, and disease surveillance. If only some of your users need these, ask Salesforce how mixed licensing works in one org before you sign. Our Service Cloud team scopes both options against your actual workflows.

Section 07 · Setup

How Do You Set Up Salesforce Health Cloud Today?

Enable person accounts, install Omnistudio, assign the Health Cloud permission set licences, turn on the FHIR R4-aligned data model, then switch on features one at a time. There is no package to install for new customers. Do it in a sandbox first: Salesforce offers a 30-day Health Cloud trial with no installation.

1. Enable person accounts.
→ Turn on Contacts to Multiple Accounts and person accounts, then create record types and page layouts for patients, members and providers. Person accounts cannot be switched off once enabled, so confirm the decision with your architect first.
2. Install Omnistudio.
→ Assessments, utilization management and many guided intake flows run on Omnistudio, so it is part of the basic setup in Salesforce's admin guide.
3. Assign licences and permission sets.
→ Every internal user needs at least the Health Cloud Platform permission set licence. Then add feature permission sets, such as Health Cloud Foundation, Utilization Management or Appointment Management, by role.
4. Enable the clinical data model.
→ In Setup, open FHIR R4 Support Settings and enable the FHIR-aligned clinical data model. Turn on Enhanced Care Plans in Integrated Care Management settings if you will use care plans.
5. Connect the EHR.
→ Pick the integration pattern per use case, map EHR codes to CodeSet records, and test with de-identified data before any PHI enters the org.
6. Switch on features in sequence.
→ Start with the workflow that hurts most, such as referral intake or discharge follow-up, then add care programs, assessments and portals.
7. Open the portal last.
→ Build patient and member portals on the Health Cloud Consumer App template in Experience Cloud. External care team members need at least a Customer Community Plus licence.

Salesforce's Agentforce Health administration guide and permission set licence reference have the detail. For the portal itself, see our Experience Cloud services.

Section 08 · Pricing

How Much Does Salesforce Health Cloud Cost?

Salesforce lists Health Cloud from $350 per user per month for Sales & Service Core up to $725 for Sales & Service Max, billed annually. Each edition includes a yearly allowance of Flex Credits for Data 360, Agentforce and Tableau Next. Agentforce is an add-on on Core and Advanced and included in Max, and it needs the $0 Salesforce Foundations SKU.

EditionList price (USD/user/month)What it adds
Sales & Service Core$350Clinical and insurance data models, care management, Slack Business+, Tableau Next, Premier Success; 500K Flex Credits per org per year
Sales & Service Advanced$525Everything in Core plus more AI, storage, automation and security: Backup & Recover, Archive, Data Detect, Security Center; 1M Flex Credits
Service Max or Sales Max$700Advanced plus Agentforce for health with service (Workforce Management, Quality Management) or with sales (Contracts, digital contact centre)
Sales & Service Max$725Both Max editions in one; 2.75M Flex Credits

Core has tighter limits than Advanced and Max: 100 custom objects instead of 2,000, 25 developer sandboxes instead of 100, 20 MB of data storage per user instead of 1 GB, and a Full sandbox only as an add-on. Listed add-ons include Provider Network Management at $100 per user per month, Analytics for Health and Life Sciences at $165, and Home Health from $30 per login. Data 360 provisioning is $0, while Data Cloud Starter is listed at $108,000 per org per year.

Prices from the Health Cloud pricing page, checked November 6, 2026; Salesforce states they are subject to change. An older 2025 Salesforce datasheet uses Enterprise and Unlimited edition names, and Salesforce Help still says "Enterprise and Unlimited Editions with Health Cloud". Confirm current names and prices with your account executive. These figures are licences only: implementation, integration and Shield are separate.

Section 09 · HIPAA

Is Salesforce Health Cloud HIPAA Compliant?

Health Cloud can be used for HIPAA-regulated data, but it is not compliant by default. Coverage starts only when you and Salesforce sign a Business Associate Addendum that lists the service, and it continues only while you follow its restrictions. Those restrictions include encrypting PHI, using covered services only, and limits on how AI may use health data.

What the BAA requires of you

  • Sign the BAA first. Salesforce's compliance site says customers building HIPAA applications should contact their account representative about a BAA. Health Cloud and Life Sciences Cloud were added to the covered services list in August 2024.
  • Stay on covered services. The list includes Health Cloud, Sales Cloud, Service Cloud, Experience Cloud, the Lightning Platform, Shield, Data 360, CRM Analytics, Omnistudio, MuleSoft Anypoint on Hyperforce, Marketing Cloud Engagement and Agentforce Service Agent, Voice and Prompt Builder. Some features in these clouds, such as Tableau Bridge, are excluded. Check each new tool before PHI reaches it.
  • Encrypt PHI. You are responsible for secure transmission and must encrypt PHI in transit and, where it is in your control, at rest.
  • Mask data for AI. For Agentforce and Prompt Builder, you must enable and keep using data masking in the Einstein Trust Layer.
  • No AI diagnosis. Einstein and Agentforce services may not be used for diagnosis or treatment, as a medical device, or to predict a person's condition, program eligibility or outcome.

Salesforce Shield adds Platform Encryption (fields, files, attachments and search indexes, with customer-controlled keys), Event Monitoring, Field Audit Trail and Data Detect. Shield is not included in any Health Cloud edition, so price it separately. Two documented limits to plan around: you cannot sort a list column on an encrypted field, and Event Monitoring does not log which patients appear on the Today, Patient List or Candidate Patients pages.

Source: Salesforce Business Associate Addendum restrictions (last updated September 30, 2026) and the Salesforce HIPAA compliance page. For what a business associate contract must contain, see HHS guidance. This is not legal advice: confirm your obligations with your compliance team.

Section 10 · AI

What Can Agentforce Do in Health Cloud?

Agentforce Health adds prebuilt agents and actions for administrative healthcare work: verifying identity, booking appointments, capturing referrals, checking eligibility and benefits, answering member questions and summarizing records. They run on the Health Cloud data model, so their quality depends on how cleanly that model is populated, and BAA restrictions apply to every one of them.

Contact centre and voice

Agent templates for provider and payer contact centres; a voice agent can verify a caller, book or waitlist an appointment, or capture a referral, then hand off to staff.

Document AI for Health

Reads PDFs such as lab reports and maps the values to Health Cloud objects, in batches if needed.

Summaries and assessments

Generative summaries of a patient or member record, and suggested assessment questions with pre-filled responses for care managers.

In March 2026 Salesforce announced six more agents, including referrals and assessments, bidirectional EHR read-write through MuleSoft connectors, and claims and coverage. Some were marked generally available and others were due later in 2026, so check the release notes before you plan around one. Pilots should start where the BAA rules are easiest to meet: scheduling, referral capture and member service rather than anything that interprets clinical status. Our Agentforce agent development team builds and tests agents against those limits.

Section 11 · Pitfalls

Where Do Health Cloud Implementations Usually Go Wrong?

Most failures come from planning against outdated guidance, licensing gaps found after go-live, and treating HIPAA as a checkbox. The platform is mature; the risk sits in design decisions made in the first weeks. These are the ones we check on every Health Cloud project and every rescue.

Following package-era instructions. Guides that start with "install the Health Cloud package" or build care plans on custom objects lead new orgs into dead ends. Build on the platform features and the FHIR R4-aligned objects.
Patients as contacts. Skipping person accounts limits what Health Cloud can do, and the decision is hard to reverse once data is loaded.
Copying the whole chart. Replicating every EHR field multiplies PHI, storage and reconciliation work. Read live where you can and store only what drives workflow or reporting.
Licences missed in the budget. Every internal user needs the Health Cloud Platform permission set licence, portal care team members need Customer Community Plus, and MuleSoft Direct, Provider Network Management and Experience Cloud are add-ons on most editions.
Expecting scores out of the box. Unified Health Scoring shows scores; it does not calculate them. Plan the Data 360 or custom scoring work.
A BAA with nothing behind it. PHI flowing into a tool outside the covered list, unencrypted fields, or Agentforce running without Trust Layer data masking breaks the BAA terms even with the contract signed.

If your org already has some of these problems, a Salesforce health check finds them before they turn into a compliance or adoption issue.

Section 12 · Bottom Line

The Bottom Line

Salesforce Health Cloud works best as the operating layer around the EHR: one patient or member record, the workflows that move people through care, and AI agents that take on administrative work within clear compliance limits. Twopir Consulting implements Health Cloud for healthcare organizations, with a focus on patient operations: intake, referrals, scheduling, EHR integration and leadership reporting. We also redesign Health Cloud orgs that are not delivering.

  1. 1

    Start from current documentation: no package, person accounts, FHIR R4-aligned objects.

  2. 2

    Decide Health Cloud or Service Cloud by workflow, not by HIPAA.

  3. 3

    Choose an integration pattern per use case, and store only the clinical data you act on.

  4. 4

    Budget the full licence stack: edition, permission set licences, portals, MuleSoft, Shield.

  5. 5

    Sign the BAA, encrypt PHI, mask data for AI, and pilot agents on administrative work first.

Ready to Start

Plan Your Health Cloud Build with a Salesforce Partner

Tell us how patients and members move through your organization today. We will map the data model, EHR integration and licence stack your Health Cloud project actually needs.

Schedule a Discovery Call

FAQ

Frequently Asked Questions

Salesforce Health Cloud, now sold as Agentforce Health, is a healthcare CRM built on the Salesforce platform. It gives providers, payers, home health and medtech teams one patient or member record that combines clinical context from the EHR with care plans, programs, referrals, authorizations and service history, plus workflows and AI agents that act on that record.

Yes. Salesforce Help now says Health Cloud is Agentforce Health, and you may still see the Health Cloud name in the product and documentation. The pricing page continues to use Health Cloud edition names, such as Health Cloud Sales & Service Core. The underlying product, data model and setup are the same.

No. The EHR remains the system of record for charting, orders and results. Health Cloud maps the clinical data it needs from the EHR into its own objects, or reads it live over FHIR, and manages the relationship and operational work around care: intake, referrals, scheduling, care coordination, programs and member service.

Salesforce lists Health Cloud at $350 per user per month for Sales & Service Core, $525 for Advanced, $700 for Service Max or Sales Max, and $725 for Sales & Service Max, billed annually. Add-ons such as Provider Network Management, MuleSoft Direct, portals and analytics cost extra, and prices are subject to change.

It can support HIPAA compliance, but not by default. You must sign Salesforce's Business Associate Addendum covering the services you use, keep PHI in covered services, encrypt PHI, and enable Einstein Trust Layer data masking for Agentforce and Prompt Builder. AI may not be used for diagnosis or to predict a person's health status or eligibility.

Salesforce documents three patterns: real-time FHIR reads that show EHR data without storing it, HL7 v2 event feeds written into the FHIR R4-aligned clinical objects, and bulk FHIR loads into Data 360. MuleSoft Direct for Health Cloud and the MuleSoft Accelerator for Healthcare provide prebuilt integrations and mappings for Epic, Cerner and other systems.

No. Since the Summer '24 release, new customers cannot access the Health Cloud managed package, because its features are now built into the Salesforce platform. Setup now means enabling person accounts, installing Omnistudio, assigning Health Cloud permission set licences and turning on the FHIR R4-aligned data model. Earlier customers keep package access.

Choose Health Cloud if your workflows depend on clinical, insurance or care data, such as care plans, programs, referrals, authorizations or provider networks. Service Cloud may be enough for contact centre and case work that never touches clinical data. HIPAA alone is not the deciding factor, because Service Cloud is also covered under Salesforce's BAA.

TC

Twopir Consulting

Salesforce Partner · HubSpot Partner

Twopir Consulting helps growing and mid-market companies solve complex CRM, integration, and business system challenges. We implement, rescue, optimize, and integrate complex CRM and revenue systems, including Salesforce Health Cloud, Experience Cloud and MuleSoft for healthcare organizations, for 500+ clients over 12+ years.