Salesforce Health Cloud: Complete 2026 Guide (Patient 360, Care Plans & Agentforce for Healthcare)

TL;DR

• Health Cloud is Salesforce's industry vertical for healthcare and life sciences. Built on core CRM with healthcare-specific data model and workflows.
• The household data model is the central differentiator — patients are modeled with relationships to family, payors, providers, and caregivers.
• Care Plans drive longitudinal care coordination; Care Programs drive cohort-based engagement (e.g., diabetes management).
• FHIR + HL7 integration via MuleSoft Health Cloud Accelerators connects to Epic, Cerner, Meditech.
• HIPAA compliance requires Shield for encryption + audit trail.

If you're stepping into a Health Cloud project from a core Salesforce background, the data model alone takes weeks to internalize. This guide is the canonical mental map: what Health Cloud is, how its objects fit together, where it integrates with Epic/Cerner, what changed in 2026 with Agentforce, and the implementation roadmap that doesn't blow up at month four.

What Health Cloud is (and isn't)

Health Cloud is:

• A vertical industry SKU built on the Salesforce Platform.
• A healthcare-specific data model (Patient → Care Team → Conditions → Care Plans → Encounters).
• A bundle of pre-built UI components for clinical and care-coordinator workflows.
• An integration framework for Epic, Cerner, Meditech, and other EHRs (via MuleSoft Accelerators or custom).
• Compliance-aware: designed to be deployable in HIPAA-regulated environments (with Shield).

Health Cloud is not:

• An EHR. It doesn't replace Epic. It complements EHR data with CRM-style relationship management.
• A clinical decision support system. Diagnoses live in the EHR.
• A free upgrade. Health Cloud is a separate license tier with significant per-user cost.
• A magic compliance bullet. HIPAA compliance requires you to configure Shield and build with the right architectures.

The household data model

The most distinctive feature of Health Cloud. Patients are not just Accounts and Contacts; they sit in a network of relationships modeled as objects.

Core objects:

• Person Account — the patient (Account + Contact merged into one record). Most Health Cloud orgs use Person Accounts; some use B2B-style separate Accounts for payors/providers.
• Patient (Contact-based or Person Account-based) — the individual receiving care.
• Household — a Salesforce Account that groups related Person Accounts (family unit, billing unit).
• Care Provider — physicians, nurses, specialists. Often modeled as another Person Account or a separate object.
• Care Team — junction between Patient and Care Providers, with role and responsibility.
• Conditions — chronic and acute conditions tracked over time.
• Encounters — appointments, hospital admissions, telehealth visits.
• Medications — current and historical.

The data model is verbose. Plan for ~25 standard objects out of the box, plus custom extensions per implementation.

Care Plans vs Care Programs

Two related but different concepts.

Care Plan

A Care Plan is patient-specific — a longitudinal plan for one individual. It tracks goals, interventions, and progress for that patient's specific health journey.

Example: "Care Plan for Jane Doe — manage Type 2 Diabetes."

• Goals: HbA1c < 7.0, blood pressure < 130/80
• Interventions: medication review monthly, dietitian quarterly, lab tests every 3 months
• Progress notes: timestamped updates from care team

Care Program

A Care Program is cohort-based — a structured engagement program for a group of patients sharing a condition or risk factor.

Example: "Diabetes Management Program — 500 enrolled patients."

• Enrollment: criteria-based (HbA1c > 8, age > 45)
• Curriculum: educational content sequence
• Touchpoints: scheduled emails, calls, telehealth check-ins
• Outcomes: tracked across the cohort

The pattern: Care Programs run for a population; Care Plans run for an individual. A patient enrolled in a Care Program typically also has a personal Care Plan.

FHIR and HL7 integration

This is where Health Cloud meets the rest of healthcare's tech stack.

• HL7 v2 — the dominant legacy interface protocol. Pipe-delimited messages flowing between EHRs, lab systems, billing.
• FHIR (Fast Healthcare Interoperability Resources) — the modern REST/JSON-based standard. Used in newer integrations and required by US regulations (CMS interoperability rules).

Salesforce ships Health Cloud Accelerators for MuleSoft that handle the most common patterns:

• Patient demographics sync (Epic → Salesforce)
• Encounter ingestion (real-time on appointment creation)
• Lab result delivery
• Medication reconciliation

For everything else, custom MuleSoft flows or Apex callouts.

Advanced Therapy Management

A 2024–2025 addition that's matured in 2026. Designed for CAR-T, gene therapy, and other complex specialty therapies where a single treatment involves dozens of steps across weeks.

Tracks the full journey:

1. Patient identification + qualification
2. Insurance authorization
3. Cell collection scheduling (for autologous therapies)
4. Manufacturing + shipping logistics
5. Treatment infusion + monitoring
6. Long-term outcomes tracking

The complexity is what justifies building on Health Cloud rather than rolling it from scratch — these workflows touch 8–12 stakeholders and have hard regulatory requirements.

Agentforce for healthcare

The 2026 layer that's transforming Health Cloud workflows.

Common Agentforce-on-Health-Cloud patterns:

• Patient self-service: an agent answers eligibility questions, schedules appointments, and triages symptoms before routing to a nurse.
• Care coordinator copilot: suggests next interventions on a Care Plan based on recent encounter notes; drafts patient communication.
• Insurance pre-auth: an agent gathers required documentation, files prior authorization, and follows up.
• Medication adherence outreach: outbound voice or text agent contacts patients who missed refills.

Critical constraints in healthcare:

• HIPAA-compliant grounding. Patient data only flows through the Trust Layer with your masking config. PHI must not leak to model providers.
• Strict identity resolution. A wrong-patient match in a healthcare agent is catastrophic. Identity rules must be tighter than in retail/B2B.
• Care team handoff. Agents triage but humans deliver care. The handoff to a clinician must be smooth and auditable.

HIPAA compliance + Shield

Health Cloud doesn't make you HIPAA-compliant. The architecture does.

Required:

• Salesforce Shield — Platform Encryption (PII at rest), Event Monitoring (audit trail), Field Audit Trail (detailed change history).
• Sandbox Anonymization — masks PHI in non-prod environments.
• Strict access controls — Role Hierarchy + OWDs + Sharing Rules calibrated to "minimum necessary" access principles.
• BAA (Business Associate Agreement) with Salesforce — covers their handling of PHI.
• Audit logs — multi-year retention for HIPAA's documentation requirements.

Don't:

• Store PHI in unencrypted custom fields.
• Email PHI via unencrypted standard email.
• Sandbox-refresh full prod data without Anonymization configured.
• Assume the Trust Layer auto-handles PHI — it masks based on YOUR configuration.

Implementation roadmap

The pattern that works for new Health Cloud implementations.

Phase 1: Foundation (months 1–2)

• Stand up a sandbox; enable Health Cloud + Shield.
• Configure Person Account model.
• Set OWDs and base sharing model for HIPAA.
• Stand up basic Patient + Provider + Care Team objects.

Phase 2: Integration (months 2–4)

• MuleSoft + Health Cloud Accelerators for Epic/Cerner integration.
• Patient demographics sync (one-way from EHR).
• Encounter ingestion.
• First Care Plan templates.

Phase 3: Workflow (months 4–6)

• Care coordinator UI.
• Care Plan authoring + execution.
• Notifications + tasks for care team.
• Reporting + dashboards for care managers.

Phase 4: Engagement (months 6–9)

• Care Program enrollment + automation.
• Patient-facing portal (Experience Cloud).
• Marketing automation for outreach (via Marketing Cloud).
• Telehealth integration.

Phase 5: Agentforce (months 9–12)

• Self-service patient agents.
• Care coordinator copilots.
• Outbound adherence agents.
• HIPAA review of all agent flows.

This is a 12+ month roadmap for a serious Health Cloud implementation. Compressing below that means cutting integration depth or workflow coverage — both painful later.

Common pitfalls

• Ignoring the household model. Treating patients as standalone Contacts loses the Health Cloud value. Use Person Accounts and Households.
• Custom data model when you don't need it. The standard Health Cloud objects cover ~80% of real cases. Extend; don't replace.
• Assuming standard validation rules cover HIPAA. They don't. HIPAA requires more discipline than typical CRM data quality.
• Skipping Shield. Eventually it becomes mandatory; configure from day one.
• No identity resolution rules. "Wrong patient" mistakes are not acceptable; tune rules early and quarterly.
• Single Apex namespace for all integrations. Refactor by integration domain (EHR, billing, lab, etc.) early.
• Treating Care Plans as "rich tasks." They're a longitudinal data model with goals + outcomes, not a task list.

Frequently asked questions

How is Health Cloud different from Service Cloud? Service Cloud is generic case management. Health Cloud is healthcare-specific data model + UI + integration. Most Health Cloud orgs include Service Cloud capability for non-clinical service operations.

Is Health Cloud HITRUST-certified? The platform has HITRUST CSF certification. Your implementation needs to be assessed separately.

Do I need Marketing Cloud for outreach? Not strictly — Health Cloud + Email Studio basics work for many. Marketing Cloud unlocks more sophisticated cohort engagement.

What's the relationship to Data Cloud (Data 360)? Data 360 federates clinical data, normalizes patient identities across systems, and grounds Agentforce. For complex multi-EHR environments, Data 360 + Health Cloud is the modern stack.

Does Agentforce handle PHI? Only with proper Trust Layer configuration. Mask all PHI fields in your prompt template paths. Audit every agent action.

What's the cost? Per-user pricing significantly higher than core CRM. Add-ons (Marketing Cloud, MuleSoft, Shield) compound. Plan budget conservatively.

What to read next

• Health Cloud, Care Plan, Care Program, Person Account — the dictionary entries.
• What Is Agentforce 360? — the agent platform that powers Agentforce-for-Healthcare.
• Data Cloud Is Now Data 360 — the data foundation for cross-EHR identity.

Health Cloud is one of the most rewarding Salesforce specialties — and one of the most demanding. The combination of data model depth, regulatory complexity, and clinical-workflow nuance keeps it interesting for years.