Salesforce Health Cloud Explained: Managing Patient Data at Scale
Managing patient data across fragmented systems is one of the most persistent challenges facing healthcare providers today. Electronic health records sit in silos. Claims data lives in separate platforms. Patient engagement happens through disconnected channels. The result is a fractured view of the patient that undermines care coordination, operational efficiency, and patient satisfaction.
Salesforce HealthCloud was built to address this problem. It provides a unified platform for aggregating clinical and nonclinical data, coordinating care across teams, and engaging patients through personalized interactions at scale.
This article breaks down what Salesforce Health Cloud is, how it fits into the broader Salesforce ecosystem, and what enterprise healthcare teams need to know before adopting it. The focus is on practical matters: data models, integration patterns, compliance requirements, and implementation realities.
What Is Salesforce Health Cloud and Who Is It For?
Salesforce Health Cloud is Salesforce’s healthcare-specific platform for managing patient, member, and consumer data at scale. It extends the core Salesforce platform with a specialized data model, user interface, and workflows designed for providers, payers, life sciences organizations, and public health agencies.
Health Cloud sits on top of the foundational Salesforce infrastructure, reusing CRM capabilities from Sales Cloud and Service Cloud while adding healthcare-specific objects and processes. It leverages the same security model, API framework, and metadata-driven architecture that powers Salesforce across industries, but tailors everything for regulated healthcare use cases.
This is not an electronic health record system. Health Cloud does not replace Epic, Cerner, MEDITECH, or other EHRs. Instead, it complements them by aggregating and operationalizing data across systems. Think of it as an engagement, coordination, and data unification layer that connects clinical systems of record with patient-facing and operational workflows.
The primary stakeholder roles for Health Cloud initiatives include:
CIOs and Heads of Digital/Clinical Transformation evaluating platform strategy
Salesforce platform owners managing existing enterprise deployments
Data and compliance teams responsible for governance and security
Clinical informatics leads bridging IT and care delivery
Health Cloud is typically adopted when organizations face one or more of these situations:
Post-2018 digital transformation programs requiring modern patient engagement infrastructure
Large contact centers handling high volumes of patient or member inquiries
Value-based care contracts demanding care coordination and population health capabilities
Multi-EHR environments where data unification is a strategic priority
Life sciences companies managing patient services programs or clinical trial engagement
How Health Cloud Fits Into the Salesforce Ecosystem
Health Cloud extends core Salesforce objects with healthcare-specific data structures. The standard Account, Contact, Case, and Task objects are augmented with objects like Patient, Care Plan, Care Gaps, Utilization Management records, and Risk Assessments. This layered approach means organizations with existing Salesforce investments can build on their current infrastructure rather than starting from scratch.
From a licensing perspective, Health Cloud is an add-on to Enterprise or Unlimited Edition Salesforce orgs. Salesforce offers different SKUs for providers and payers, reflecting the distinct workflows each segment requires. The specifics vary by region and contract, so organizations should work directly with Salesforce or partners to model costs for their use case.
Health Cloud connects with other Salesforce products to form a complete healthcare technology stack:
Marketing Cloud / Marketing Cloud Engagement: Powers HIPAA-appropriate patient outreach, engagement journeys, and preference management
Experience Cloud: Enables patient, member, and provider portals with self-service capabilities
MuleSoft: Provides integration middleware for connecting EHRs, claims systems, and other external data sources
Data Cloud: Aggregates and unifies data from multiple sources for analytics and activation
Tableau: Delivers reporting tools and analytics dashboards for operational and clinical insights
Shield: Adds enhanced security features including platform encryption, event monitoring, and field audit trail
The concept of Patient 360 is central to Health Cloud’s value proposition. This unified profile combines clinical data from electronic health records EHRs, claims history from payer systems, social determinants of health indicators, engagement history, and communication preferences into a single view. Care teams access this consolidated record to make informed decisions without switching between disconnected applications.
A simplified view of the architecture looks like this:
Left side: EHRs, claims systems, pharmacy systems, IoT devices, and lab results
Center: MuleSoft integration layer handling data transformation and orchestration
Right side: Health Cloud (Patient 360, care plans, UM workflows) connected to Data Cloud, Marketing Cloud, and Experience Cloud
Core Patient Data Model and Patient 360
The health cloud data model is purpose-built for healthcare, structured around Person Accounts, clinical data objects, care management entities, and utilization management records. Unlike generic CRM configurations, this clinical data model reflects the relationships and workflows healthcare professionals actually use.
Understanding the standard objects is essential for any Salesforce Health Cloud implementation:
Person Account: Represents the patient or member as a unified record, combining account and contact into a single entity
Care Plan: Captures individualized goals, problems, interventions, and tasks related to a patient’s health status
Care Team: Defines the group of providers, coordinators, social workers, and caregivers associated with a patient
Condition: Records diagnoses and health problems linked to the patient
Medication: Tracks current and historical prescriptions
Risk Assessment: Stores calculated risk scores for stratification and intervention targeting
Care Gap: Identifies missing preventive or chronic care actions (e.g., overdue screenings)
Encounter: Documents visits, admissions, and other clinical interactions
The patient timeline aggregates these records into a chronological view. Healthcare professionals can see encounters, referrals, care plan activities, outreach messages, and lab results arranged along a single timeline. This longitudinal record eliminates the need to piece together patient history from multiple screens.
Interoperability support includes HL7 v2 messaging for legacy systems, HL7 FHIR R4 for modern clinical APIs, and X12 standards for claims data. In most implementations, data arrives via integration middleware rather than manual entry, ensuring accuracy and reducing administrative burden.
Example: Consider a cardiology patient managing congestive heart failure. Their Health Cloud record displays clinical data from their cardiologist’s EHR, remote monitoring readings from a home scale and blood pressure cuff, pharmacy fill data showing medication adherence, and a complete history of outreach calls and secure messages from the care management team. A nurse reviewing this record can immediately identify that the patient gained three pounds overnight, missed their last diuretic refill, and hasn’t responded to two wellness check calls. This unified view enables faster intervention and better patient outcomes.
Key Health Cloud Capabilities for Enterprise Healthcare
This section covers the essential features that make Health Cloud suitable for enterprise-scale healthcare operations. Rather than a marketing feature list, the focus is on practical capabilities that support real workflows.
Care Coordination
Care coordination in Health Cloud centers on care plans, tasking, and team visibility. Care coordinators create and manage treatment plans with defined goals, interventions, and milestones. Tasks can be assigned across care teams, with clear ownership and due dates. Cross-disciplinary notes attach to patient records, so a social worker’s assessment is visible to the nurse coordinator and primary care physician. Escalation workflows trigger alerts when patients miss appointments, show declining metrics, or fail to engage with outreach. For complex patients with multiple chronic conditions, this connected care approach prevents gaps and reduces duplication of effort.
Contact Center and Engagement
Health Cloud provides customized consoles for nurses and contact center agents handling patient or member inquiries. When a call comes in, the agent sees the patient 360 view immediately, including recent encounters, open care gaps, benefits information, and communication preferences. Integration with telephony systems enables screen pops and call logging. Personalized engagement becomes possible when agents have context, and patient satisfaction improves when callers don’t have to repeat their medical history. Secure messaging, email, and SMS channels integrate into the same interface, supporting omnichannel patient engagement.
Utilization Management
For payers and integrated delivery networks, utilization management capabilities streamline prior authorizations, referrals, and appeals and grievances. Structured workflows guide staff through intake, clinical review, and determination. Health Cloud supports emerging standards like Coverage Requirements Discovery (CRD), Documentation Templates and Rules (DTR), and Prior Authorization Support (PAS) to automate documentation gathering and reduce manual back-and-forth between providers and payers. This reduces costs and accelerates decision timelines.
Population Health
Population health features enable risk stratification using claims and EHR data combined with social determinants. Care managers can identify cohorts of rising-risk patients, create outreach campaigns targeting specific gaps in care, and track adherence to care programs. Unified Health Scoring provides configurable composite scores that trigger interventions when thresholds are crossed. This supports advanced therapy management programs where proactive outreach can prevent hospitalizations.
Key outcomes organizations can expect from these capabilities:
Reduced readmissions through coordinated post-discharge follow-up
Shorter call handling times with immediate access to patient information
Faster prior authorization decisions through automated workflows
Improved patient progress visibility for care teams managing complex cases
Interoperability and EHR Integration at Scale
Large healthcare systems rarely operate a single EHR. A typical integrated delivery network might run Epic in acute care hospitals, athenahealth in ambulatory clinics, a legacy billing system from a previous acquisition, and various specialty department systems. Health Cloud must orchestrate data across all of these, not replace any of them.
Integration patterns typically rely on MuleSoft Anypoint Platform or similar middleware. Common approaches include:
FHIR APIs: For modern clinical data exchange, supporting Patient, Encounter, Condition, Observation, and other resources
HL7 v2: For legacy ADT (admit/discharge/transfer) messages, lab results, and orders
X12: For claims, eligibility, and benefits transactions with payer systems
Custom REST/SOAP: For older systems lacking standard interfaces
Concrete flow example: When a patient is discharged from an Epic hospital in 2025, a FHIR-based Encounter resource is generated. MuleSoft receives this via subscription or polling, transforms the data to match Health Cloud’s data model, and creates or updates the corresponding Encounter record linked to the Patient. The patient timeline immediately reflects the discharge, enabling care coordinators to initiate post-discharge outreach within hours rather than days.
Bidirectional vs. read-only patterns require careful design. Health Cloud often writes back patient communication preferences, consent status, and outreach history to systems of record. However, clinical documentation typically remains read-only in Health Cloud to avoid patient safety risks from conflicting information. The golden rule: Health Cloud is an engagement and coordination layer, not a clinical documentation system.
Handling large volumes demands thoughtful architecture:
Event-based integrations: For high-priority updates like abnormal lab results or hospital admissions that should trigger immediate workflows
Batch processing: For nightly loads of claims data, population health analytics, or historical data migrations
Near-real-time updates: For high-risk care programs where delays could impact patient care
Integration architecture for a typical implementation:
Left: Multiple EHRs (Epic, Cerner, athenahealth), claims systems, pharmacy benefit managers, lab information systems, IoT devices
Center: MuleSoft providing API management, data transformation, error handling, and audit logging
Right: Health Cloud (patient records, care plans, UM workflows) connected to Data Cloud for analytics and Marketing Cloud for outreach
Partners like Deselect help design integration architectures, API governance frameworks, and data contracts that prevent point-to-point sprawl. This is especially critical when implementations span dozens of source systems and millions of patient records.
Security, Compliance, and Data Governance
Healthcare organizations operate under strict regulatory requirements. Health Cloud can be deployed to support compliance with key regulations including:
HIPAA (U.S.): Protects patient health information with administrative, physical, and technical safeguards
HITRUST CSF: Provides a certifiable framework that maps to multiple regulations
GDPR (EU): Governs data subject rights, consent management, and data minimization
Regional standards: Such as NHS DCB 0129 in the U.K. for clinical safety
Core Salesforce security controls provide the foundation for protecting patient data:
| Control Type | Description |
|---|---|
| Role Hierarchy | Defines data access based on organizational structure |
| Profiles/Permission Sets | Controls object and field-level access by user type |
| Field-Level Security | Restricts visibility of sensitive fields like SSN or diagnosis |
| Sharing Rules | Enables record-level access based on criteria or ownership |
| Shield Platform Encryption | Encrypts data at rest with customer-managed keys |
| Event Monitoring | Logs user activity for security analysis and audit |
PHI access restrictions in Health Cloud typically include:
Care team–based sharing that limits record visibility to assigned team members
Record-level sharing rules that partition data by facility, region, or business unit
IP restrictions and geo-fencing for access from approved locations
SSO integration via SAML or OIDC with identity providers
Mandatory MFA for all users accessing patient information
For organizations with specific requirements, Salesforce offers Government Cloud for U.S. federal programs (available since 2021) and Hyperforce regions for data residency in the EU and other jurisdictions.
Governance practices that organizations should establish:
Data classification: Categorizing data by sensitivity (PHI, PII, public) to apply appropriate controls
Retention policies: Defining how long different record types are kept and when they’re archived or deleted
Audit logging: Capturing field history and user actions for compliance investigations
DLP processes: Controlling data exports to analytics tools, data lakes, and external systems
Partners such as Deselect focus on data architecture and governance, helping large enterprises standardize data models across multiple orgs and business units. This prevents inconsistent implementations that create compliance gaps.
Security posture checklist for evaluating Health Cloud:
[ ] BAA (Business Associate Agreement) executed with Salesforce
[ ] Shield Platform Encryption enabled for PHI fields
[ ] Role hierarchy and sharing model designed for clinical privacy requirements
[ ] SSO and MFA enforced for all user profiles
[ ] Event monitoring active with alerts for anomalous access patterns
[ ] Data classification documented for all custom and standard objects
[ ] Retention and archival policies defined and automated
[ ] Integration security reviewed (API authentication, data in transit encryption)
[ ] Export controls established for reporting tools and analytics platforms
Real-World Use Cases and Implementation Examples
Understanding how organizations actually deploy Health Cloud provides clarity that feature lists cannot. The following scenarios illustrate common patterns across different healthcare segments.
Multi-Hospital System: Post-Discharge Care Coordination
A U.S. multi-hospital system with 12 facilities implemented Health Cloud in 2023 to coordinate post-discharge care for orthopedic surgery patients. Epic served as the clinical system of record, while Health Cloud aggregated discharge summaries, follow-up appointment schedules, and home health visit records. Care coordinators used the patient timeline to monitor patient progress during the critical 30-day post-discharge window. Automated tasks triggered when patients missed physical therapy appointments or failed to complete post-op surveys. By delivering personalized care through targeted outreach, the system reduced 30-day readmissions for joint replacement patients by 18%.
National Payer: Streamlined Prior Authorization
A large commercial payer deployed Health Cloud’s Utilization Management capabilities to transform their prior authorization process. Previously, authorization requests took an average of 4.2 days to process, with significant manual document gathering. After implementation, structured workflows automated clinical documentation requests from provider EHRs via MuleSoft integration. Real time insights into pending cases enabled managers to allocate reviewer resources dynamically. Decision times dropped to under 24 hours for 78% of requests, improving customer satisfaction and reducing provider abrasion.
Digital Health Startup: Chronic Care Management
A chronic care management company combined remote monitoring devices with Health Cloud to manage patients with hypertension and diabetes. Blood pressure cuffs and glucometers transmitted readings via API into Data Cloud, which fed into patient records and Unified Health Scoring. When readings crossed clinical thresholds, automated workflows created outreach tasks for care managers. The patient experience improved as staff could reference complete device history during calls. Marketing Cloud Engagement powered personalized engagement through SMS reminders and educational content tailored to each patient’s condition and communication preferences.
Regional Health Authority: Vaccination Program Management
A regional public health agency used Health Cloud and Experience Cloud to manage a large-scale vaccination program. Citizen-facing portals allowed residents to schedule appointments, complete consent forms, and access vaccination records. Health Cloud managed appointment inventory, tracked doses administered, and identified populations with low vaccination rates. Outreach campaigns targeted zip codes with gaps using Marketing Cloud. The unified view of program data enabled leadership to allocate resources to underserved areas and improve health outcomes across the region.
Common patterns across these implementations:
Integration with existing systems via MuleSoft rather than data replacement
Patient 360 as the foundation for care team decision-making
Automated workflows triggered by data events (discharges, readings, missed appointments)
Analytics and reporting tools providing operational visibility
Multi-product Salesforce deployments combining Health Cloud with Experience Cloud and Marketing Cloud
Implementation Complexity, Risks, and Best Practices
Health Cloud implementations are complex undertakings, especially for organizations with legacy EHRs, fragmented CRMs, and strict regulatory oversight. Acknowledging this reality upfront prevents costly surprises during execution.
A phased implementation approach typically works best:
Phase 1 – Foundation: Establish the core data model, Patient 360, and primary integrations with key source systems
Phase 2 – Targeted Journeys: Implement specific workflows such as care management, utilization management, or contact center operations
Phase 3 – Advanced Capabilities: Add analytics, AI-driven risk scoring, population health programs, and virtual care integrations
Typical Risks
Organizations commonly encounter these pitfalls:
Attempting to replicate full EHR functionality in Health Cloud, creating duplicate documentation workflows and clinician resistance
Underestimating data migration and cleanup requirements, leading to poor data quality that undermines care coordination
Insufficient involvement from clinicians and nurses during design, resulting in workflows that don’t match real-world care delivery
Ignoring governance requirements until late in the project, creating compliance gaps and rework
Point-to-point integration sprawl that becomes unmaintainable as the number of connected systems grows
Overcomplicating initial scope instead of proving value with focused use cases
Recommended Practices
Start with 2–3 high-value use cases that demonstrate measurable impact (e.g., reduce readmissions, lower costs for prior auth processing)
Align with clinical leadership early, securing physician and nurse champions who can validate workflows
Design for interoperability first, establishing data contracts and API governance before building integrations
Establish a data governance council that includes IT, compliance, and clinical informatics representation
Plan for change management, including training programs and user feedback loops
Build performance testing into the project plan, especially for implementations handling millions of patient records
Involving an experienced Salesforce partner such as Deselect is particularly valuable for data architecture, integration strategy, and performance tuning. Partners with deep healthcare and Salesforce expertise help organizations avoid common mistakes and accelerate time to value.
Cost, Licensing, and Total Cost of Ownership Considerations
Salesforce does not publish fixed Health Cloud pricing that applies universally. Costs depend on edition (Enterprise vs. Unlimited), user counts, and add-on products required for the implementation.
Key cost drivers to model:
| Cost Category | Factors to Consider |
|---|---|
| Health Cloud Licenses | Number and type of users (care coordinators, agents, clinicians); provider vs. payer SKUs |
| Platform Add-Ons | Shield for enhanced security, MuleSoft for integration, Marketing Cloud for engagement |
| Data Storage | Volume of patient records, historical data, and attachment storage needs |
| Environments | Production, multiple sandboxes, development orgs for enterprise CI/CD pipelines |
| Integration Tooling | MuleSoft licensing tiers, API call volumes, connector requirements |
Indirect costs are often underestimated:
Internal change management resources and program leadership
Training programs for end users, administrators, and developers
Clinical engagement time for workflow design and user acceptance testing
Ongoing administration and DevOps support for the Salesforce platform
Governance overhead for data quality, security monitoring, and compliance
Organizations should build a 3–5 year TCO model comparing scenarios:
Do nothing: Continue with fragmented systems, accepting current operational inefficiencies
Extend EHR CRM modules: Use native engagement tools from Epic, Cerner, or other EHR vendors
Implement Health Cloud: Full investment in Salesforce-based patient engagement and care coordination
Partners can help optimize licensing strategies, such as mixing full Health Cloud licenses for power users with platform licenses for lighter use cases. Data architecture decisions also impact costs: designing efficient data strategies reduces unnecessary storage and integration expenses over time.
Assumptions finance teams should model:
[ ] Year 1 implementation costs (licenses, services, infrastructure)
[ ] Annual license growth as user counts expand
[ ] Integration maintenance and API consumption costs
[ ] Storage growth based on patient volume and data retention requirements
[ ] Internal FTE allocation for administration and enhancement
[ ] Training and change management investments per phase
[ ] Expected ROI metrics (readmission reduction value, contact center efficiency gains, UM time savings)
Is Salesforce Health Cloud the Right Choice for Your Organization?
Health Cloud is a strong fit when organizations face specific challenges that align with the platform’s strengths:
Multi-channel patient engagement needs spanning phone, portal, email, and SMS
Multiple EHRs requiring a unification layer for care coordination
Large contact centers handling patient or member inquiries at scale
Value-based care contracts demanding population health and care management capabilities
Strategic priority around Patient 360 and personalized patient experience
Health Cloud may not be ideal in certain situations:
Very small practices without existing enterprise Salesforce investments
Organizations seeking a full EHR replacement rather than an engagement layer
Environments unwilling to invest in integration infrastructure and data governance
Teams lacking internal Salesforce administration capacity or partner support
Decision checklist for moving forward:
[ ] Current Salesforce footprint assessed (existing clouds, licensing, technical debt)
[ ] Integration maturity evaluated (API capabilities, middleware in place, source system documentation)
[ ] Security and compliance requirements documented (HIPAA, HITRUST, GDPR, regional standards)
[ ] Internal admin and developer capacity confirmed or partner engagement planned
[ ] Executive sponsorship secured from both IT and clinical leadership
[ ] High-value use cases identified with measurable success criteria
[ ] Budget authority established for multi-year investment
Before committing to a full rollout, organizations should run a focused discovery phase lasting 6–12 weeks. This validates use cases, maps integration complexity, assesses data quality, and defines governance requirements. The discovery phase surfaces risks early when they’re cheaper to address.
Involving a Salesforce partner such as Deselect early in the process helps assess data architecture, patient-identity strategy, and interoperability roadmaps. Partners with experience in complex healthcare environments accelerate decision-making and de-risk implementation.
Health Cloud offers healthcare organizations a powerful platform for managing patient data at scale, but success depends on realistic expectations, thoughtful architecture, and commitment to integration and governance. Organizations that approach implementation strategically will see better outcomes for their teams, their operations, and most importantly, their patients.
