Health Cloud Setup
Health Cloud Setup is the Salesforce Setup node that configures Health Cloud, the Salesforce Industries product for healthcare and life-sciences organizations.
Definition
Health Cloud Setup is the Salesforce Setup node that configures Health Cloud, the Salesforce Industries product for healthcare and life-sciences organizations. The node bundles every Health-Cloud-specific configuration: enabling the data model (Patient, Provider, Care Plan, Health Condition, Medication, EHR sync mappings), assigning Health Cloud permission sets, configuring the Patient Card and Care Team layouts, and turning on integrations like the EHR connector and the Patient Service Console.
Health Cloud sits on top of Service Cloud as an industry-specific layer. The base Service Cloud licenses still apply for agent seats; Health Cloud adds the medical data model (managed package + standard objects), the patient-centric UI components, and the regulatory configuration (HIPAA-aligned auditing, consent management, FHIR integration patterns). Health Cloud Setup is where the entire configuration surface for these capabilities is collected, so a Health Cloud admin lives in this node during initial provisioning and during every release upgrade.
Everything Health Cloud Setup actually configures
Enabling Health Cloud and the managed package
The first step under Health Cloud Setup is enabling Health Cloud Settings. The toggle activates the managed package data model and installs the standard objects (Patient, Provider, Care Plan, Health Condition, Medication, Care Team Member). Permission sets like Health Cloud Standard User and Health Cloud Admin become available. The toggle is one-way; disabling it after setup is not supported without a Salesforce Support case.
The patient-centric data model
Health Cloud uses Person Accounts (or Contacts) as the foundation for the Patient record, with a managed-package Patient object overlay that holds clinical details. Health Conditions, Medications, and Care Plans are child objects with their own page layouts and reporting. The data model maps to FHIR R4 resources for EHR integration. Admins configure which standard fields map to which managed-package fields under Health Cloud Setup, Patient Card.
Patient Card configuration
The Patient Card is the central Lightning component that surfaces patient summary on every record page. Health Cloud Setup exposes a Patient Card Configurations node where admins pick which fields appear, in what order, and with what styling. Configurations can vary by user role (provider vs. care coordinator vs. patient access representative) so each team sees the relevant summary first.
Care Plan templates
Care Plan templates are the structured handoff mechanism in Health Cloud. A care manager defines a template (a set of Care Tasks, Goals, and Problems for a specific condition like Type 2 Diabetes), and the template can be applied to any patient. Setup exposes the Care Plan Templates node for designing and versioning templates. Applied templates create live Care Plan records that the patient''s care team uses to coordinate work.
EHR connector and FHIR mapping
Health Cloud ships connectors for Cerner, Epic, and FHIR-compliant EHRs. Health Cloud Setup includes an EHR Integration node where admins configure the connection parameters, the field mappings between EHR resources and Salesforce objects, and the polling or webhook cadence. Integration also flows through MuleSoft when the EHR exposes a non-FHIR interface.
Consent management
Health Cloud Setup has a Consent Management node that configures the consent objects (Authorization Form, Authorization Form Consent, Communication Subscription Consent) used to track HIPAA-aligned consent grants. Admins define consent templates, the systems-of-record they apply to, and the retention rules. The consent records become the legal basis for any marketing or coordinated-care outreach.
Permission sets and licensing
Health Cloud licensing is per-user and additive to base Service Cloud. Each Health Cloud user gets the Health Cloud Standard User permission set plus role-specific permission sets (Health Cloud Patient Service Console, Health Cloud Provider Console). Health Cloud Setup includes a Permission Set Assignment dashboard that audits which users have which permission sets.
Stand up a new Health Cloud org
The setup loop takes a few days for the technical configuration plus weeks of business process design. Health Cloud is a deep product; budget time accordingly.
- Provision the Health Cloud org
Coordinate with the Salesforce account team to enable Health Cloud licensing on the org. Confirm the Patient license type (Person Accounts vs. Contacts) before provisioning, because changing it later requires a major migration.
- Enable Health Cloud Settings
Setup, Health Cloud Settings, toggle Enable Health Cloud. The toggle installs the managed package data model and unlocks the rest of the Health Cloud Setup nodes.
- Configure the patient data model
Decide on Person Accounts vs. Contact + Account. Configure Patient Card layouts. Set up Health Condition, Medication, and Care Plan page layouts for the relevant roles.
- Define Care Plan templates
Create templates for the most common conditions in your population. Diabetes, hypertension, post-surgical recovery, and behavioral health are common starting points.
- Set up EHR integration
Pick the connector (Epic, Cerner, FHIR), configure connection parameters, map fields, and run a sandbox integration test before going live in production.
- Assign permission sets and train users
Roll out Health Cloud Standard User to providers, care coordinators, and patient access representatives. Train each role on the Patient Card, Care Plans, and Consent capture in front of patients.
- Person Accounts vs. Contact is a one-way decision. Migrating after go-live requires a major data project.
- HIPAA compliance lives in Salesforce''s Business Associate Agreement plus the org''s configuration. Setup alone does not make the org compliant; consent, audit, and shield encryption are layered controls.
- EHR connectors require dedicated user provisioning in the EHR. Plan the integration as a cross-team project, not a Salesforce-only configuration.
- Health Cloud release notes ship per Salesforce release. Read them every release; the managed package evolves rapidly.
Trust & references
Cross-checked against the following references.
- Health Cloud Admin GuideSalesforce Help
- Enable Health CloudSalesforce Help
Straight from the source - Salesforce's reference material on Health Cloud Setup.
- Health Cloud Data ModelSalesforce Help
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. What customer experience metric would Health Cloud Setup help improve?
Q2. How does Health Cloud Setup help support agents be more productive?
Q3. Which Salesforce Cloud includes Health Cloud Setup as a key feature?
Discussion
Loading discussion…