What Is Salesforce Health Cloud?
Salesforce Health Cloud is an industry-specific CRM platform built for healthcare providers, health insurers (payers), and life sciences companies. It extends the Salesforce platform with clinical and administrative data models including patient timelines, care plans, care team coordination, referral management, and utilisation management.
Health Cloud was originally launched in 2016 for provider use cases, focused on care coordination and patient engagement. It has since expanded to cover payer member management, life sciences commercial operations, and — through the acquisition of Vlocity — benefits administration and claims processing workflows via OmniStudio.
From a licensing standpoint, Health Cloud is sold as a user-based subscription on top of the Salesforce platform. However, the total cost profile is complex: the base license, Einstein AI add-ons, Data Cloud for Healthcare, Shield (for HIPAA audit trails), and MuleSoft integration components are all separately priced. Before your next renewal, review our Salesforce licensing pillar to understand how Health Cloud fits within the broader Salesforce commercial structure.
Health Cloud Editions & Pricing
Salesforce Health Cloud is offered in two core licensing tiers plus an enterprise tier for large health systems. Pricing below reflects 2026 list prices — achievable negotiated prices are typically 25–40% lower for mid-to-large deployments.
Expert Advisory
Want independent help negotiating better terms? We rank the top advisory firms across 14 vendor categories — free matching, no commitment.
| Edition | List Price (User/Month) | Key Capabilities | Target Segment |
|---|
| Health Cloud Enterprise | $225 | Patient/member 360, care plans, care team, referral management | Mid-size providers, payers |
| Health Cloud Unlimited | $325 | Enterprise + unlimited API, Einstein analytics, enhanced sandbox | Large health systems, Tier 1 payers |
| Health Cloud Unlimited+ | $500+ | Unlimited + Agentforce, Data Cloud credits, MuleSoft integration | Enterprise health systems |
Pricing Reality
Most Health Cloud deployments at large health systems involve a combination of full Health Cloud licenses for care coordinators and clinical staff, with Platform licenses ($25/user/month) for administrative and operational staff. Correct user classification alone typically reduces total license cost by 20–30%.
Add-Ons and Hidden Costs
Health Cloud's add-on ecosystem is extensive. Salesforce's standard proposal strategy is to bundle the most compelling AI and compliance features into the initial pitch, then present them as separate line items with additional cost once you're committed to the platform direction.
| Add-On | List Price | Negotiability | Notes |
|---|
| Salesforce Shield (HIPAA) | 30% of net platform cost | Medium | Required for BAA/HIPAA workloads; push for inclusion in base deal |
| Einstein for Health | $75/user/mo | Medium | Clinical AI features; often unused in year 1 |
| Agentforce for Health | $2/conversation | High | Consumption-based; negotiate minimum commit & rollover |
| Data Cloud for Healthcare | $108k/yr base | High | Unified patient data; negotiate profile credits allocation |
| Health Cloud OmniStudio | Custom | Medium | Required for payer workflows; separate negotiation track |
| MuleSoft for Healthcare | Custom | High | HL7 FHIR integration; capacity units negotiable at deal stage |
| Slack for Health | $12.50/user/mo | High | Usually bundled at reduced rate in EA |
HIPAA Shield Trap
Salesforce Shield is typically required if you're processing PHI through Health Cloud. However, its standard pricing at 30% of platform cost can add $60–$100/user/month to your bill. Push to include Shield in the base Health Cloud pricing for any deployment over 150 seats — this is achievable in most EA negotiations and is often included in Unlimited+ deals at larger discounts.
Provider vs Payer vs Life Sciences Licensing
Health Cloud's licensing model differs meaningfully across verticals, and Salesforce prices accordingly. Understanding your vertical's specific requirements helps you avoid paying for capabilities you won't use.
Free Resource
Get the IT Negotiation Playbook — free
Used by 4,200+ IT directors and procurement leads. Oracle, Microsoft, SAP, Cloud — all covered.
| Segment | Core Use Cases | Key Add-Ons Required | Common Overpayment |
|---|
| Providers | Care coordination, patient engagement, care plans, referral management | Shield, MuleSoft (EHR integration), Data Cloud | Over-licensing clinical staff at full Health Cloud vs Platform |
| Payers | Member management, utilisation management, care management, benefits | OmniStudio, Shield, Agentforce (member service) | OmniStudio layer on top of full HC — often unnecessary for mid-market payers |
| Life Sciences | HCP engagement, patient support programs, medical affairs, access & hub services | Einstein for Health, Data Cloud, Agentforce | Buying full Health Cloud when Sales Cloud + Healthcare extensions suffice |
Life sciences firms should be especially cautious: Salesforce often sells full Health Cloud licenses to medical science liaisons and field sales teams that could operate effectively on standard Sales Cloud or Sales Cloud Einstein at significantly lower per-user cost. The patient services use case does require Health Cloud, but commercial operations often does not.
Negotiating a Health Cloud renewal or expansion?
Our advisors have benchmarked Health Cloud pricing across 60+ healthcare engagements.
Get Expert Help →
7 Health Cloud Negotiation Tactics
Tactic 01
Classify users by actual functional requirement, not role title
Care coordinators and case managers typically need full Health Cloud. Schedulers, billing staff, referral coordinators, and administrative personnel often need only Platform or limited Service Cloud licenses. In a 500-seat Health Cloud deployment, correct user classification typically reduces the full-license seat count by 25–35% and generates $400–$800k in annual savings.
Tactic 02
Push Shield inclusion into the base deal for deployments over 150 seats
Salesforce Shield (required for HIPAA BAA workloads) adds 30% to your platform cost if priced separately. For any deployment over 150 seats, negotiate Shield's inclusion in the base Health Cloud license price. Salesforce has significant margin in these deals and routinely absorbs Shield costs when pushed — frame it as a platform commitment, not an add-on. See our
EA renewal tactics guide for how to structure this ask.
Tactic 03
Negotiate Agentforce as consumption-based with guaranteed minimums
Agentforce for Health is priced at approximately $2/conversation. Salesforce will push for a committed minimum that locks in spend regardless of adoption. Counter with a lower minimum (reflecting realistic year-one utilisation) plus an option to expand at the contracted per-conversation rate. Also negotiate credit rollover — unused Agentforce credits should carry forward, not expire.
Tactic 04
Use EHR and competing CRM alternatives as leverage
Epic and Oracle Health (Cerner) are expanding their CRM and patient engagement capabilities. Microsoft Dynamics 365 has a dedicated healthcare offering. Even if you're committed to Salesforce as your platform, referencing a formal evaluation of Epic Cheers or Dynamics Health creates genuine competitive pressure that Salesforce AEs respond to. Use our
Salesforce vs Dynamics comparison as a framework for this conversation.
Tactic 05
Separate OmniStudio from core Health Cloud in payer negotiations
OmniStudio (the former Vlocity platform) is a separate product line that Salesforce sells bundled with Health Cloud for payer use cases. The two have different pricing mechanics and different negotiating levers. Negotiate them independently — OmniStudio capacity, FlexCard development rights, and integration cloud allocations each have distinct negotiation surfaces that can yield 20–35% savings versus accepting the bundled quote.
Tactic 06
Commit to a 3-year term in exchange for first-year price protection
Health Cloud pricing is subject to annual list price increases of 5–8%. Negotiate a 3-year price cap at the initial deal rate — meaning Salesforce cannot increase your per-seat price for the duration of the term. This is achievable for deals over $1M ARR and effectively reduces your total 3-year cost by 10–15% compared to annual renegotiation at rising list prices.
Tactic 07
Negotiate implementation support and training as concessions
Health Cloud implementations are expensive and complex — Salesforce-recommended SIs typically quote $800–$1,200 per day, and large deployments run 18–24 months. Negotiate Salesforce's Signature Success or Accelerator credits as part of the deal. A $200–$400k implementation support credit is achievable for multi-million-dollar ACV contracts and reduces total cost of ownership meaningfully.
HIPAA & Compliance Considerations
If you're processing Protected Health Information (PHI) through Health Cloud, Salesforce's Business Associate Agreement (BAA) is mandatory. The BAA covers only specific Salesforce products and configurations — not the entire platform. Critical compliance points for negotiation:
- Shield is required for PHI: Event monitoring, Field Audit Trail, and Platform Encryption are all Shield components required to meet HIPAA technical safeguard requirements. Negotiate Shield inclusion in the base deal.
- BAA scope: Confirm which Salesforce products are covered by the BAA before signing. New AI products (Agentforce, Einstein) may require separate BAA addenda.
- Data residency: If your compliance programme requires US-only data residency, negotiate this as a contractual commitment — Hyperforce regional deployment options add cost and need to be factored in.
- Audit log retention: Field Audit Trail provides up to 10-year retention. Confirm the retention period meets your compliance programme requirements and is included in your Shield pricing.
Pre-Renewal Checklist
◆
Classify all current Health Cloud users by functional role — identify who needs full Health Cloud vs Platform vs Service Cloud
◆
Confirm Shield scope — is it included in your current deal or priced separately? If separate, build inclusion into renewal negotiation
◆
Pull usage data for Einstein and Agentforce add-ons — identify under-utilised components to use as negotiation leverage
◆
Map renewal date against Salesforce fiscal quarter end — start formal negotiations 90 days before renewal
◆
Evaluate competing platforms (Epic Cheers, Dynamics Health) and build a formal alternatives document
◆
Review MuleSoft API transaction volumes against contracted capacity — negotiate capacity right-sizing or expansion in bulk
Frequently Asked Questions
Do I need Salesforce Shield for Health Cloud HIPAA compliance?
Yes, in most cases. If you are processing PHI through Health Cloud, Salesforce requires Shield (which includes Platform Encryption, Event Monitoring, and Field Audit Trail) as part of your HIPAA-compliant configuration. Salesforce's BAA covers Health Cloud with Shield but does not automatically cover all Salesforce products. Review your BAA scope carefully with your compliance team before purchasing.
What is the difference between Health Cloud Enterprise and Unlimited?
Health Cloud Unlimited adds unlimited API calls, enhanced sandbox environments, and deeper Einstein analytics compared to Enterprise. For most mid-size providers, Enterprise is sufficient. The primary driver to Unlimited is typically API volume for EHR integration (Epic, Oracle Health) — if your MuleSoft integration generates high API call volumes, Unlimited's unlimited API entitlement may be worth the premium.
Can a payer use standard Health Cloud or do they need OmniStudio?
Mid-market payers focused on member management and care management can typically operate on standard Health Cloud without OmniStudio. OmniStudio (formerly Vlocity) adds significant value for benefits administration, claims adjudication workflows, and complex product configuration — but it adds substantial cost. Evaluate whether your specific payer workflows actually require OmniStudio's capabilities or whether they can be handled with standard Health Cloud plus custom configuration.
What discount can I realistically expect on a Health Cloud renewal?
For deployments of 200+ seats with a 3-year term, achievable Health Cloud discounts typically range from 28–42% off list. The range depends on deal size, competitive situation, multi-product bundling, and quarter-end timing. The highest discounts are achieved when the customer has a credible competitive alternative, is consolidating multi-product spend onto Salesforce, and is timing the deal to Salesforce's fiscal quarter end.
Should I buy Health Cloud Unlimited+ with Data Cloud included?
Unlimited+ bundles with Data Cloud for Healthcare offer apparent value but require careful evaluation. The included Data Cloud profile credits may be insufficient for your patient population, forcing additional credit purchases. Alternatively, you may be paying for Data Cloud capability you won't use for 12–18 months. Negotiate Data Cloud separately if your data unification programme is not ready to deploy in year one of the contract.