Setting up Health Cloud is a multi-quarter exercise touching data model design, clinical system integration, compliance configuration, and workflow design for the specific healthcare role (provider, payer, life sciences). Most successful implementations engage a healthcare-specialist consulting partner with both Salesforce and healthcare domain expertise.
- Identify the healthcare role and use cases
Provider workflows differ from payer workflows differ from life sciences. Document the role, the regulatory environment, the integration touch-points with EHR/claims/lab systems, and the priority use cases. The document drives every configuration choice.
- Execute the Business Associate Agreement with Salesforce
Before handling PHI, complete the BAA with Salesforce. The BAA establishes the HIPAA compliance framework. No PHI should flow into Salesforce before this agreement is in place.
- Provision Health Cloud and configure the base
Salesforce provisions Health Cloud as a managed package. Install in the target org. Configure base permissions, sharing model, and user profiles for Care Coordinators, Care Team Members, and other healthcare-specific roles.
- Set up the Patient/Member data model
Configure Person Accounts for individuals. Customize the Patient or Member record page for the use case. Build relationships to Care Plans, Health Conditions, Medications, and other clinical objects.
- Configure clinical data integration via FHIR
Set up the FHIR endpoint connection to source EHR or claims systems. Map FHIR resources to Health Cloud objects. Validate data flow with sample patients before going live.
- Build Care Programs and Care Plan templates
For care management use cases, build Care Programs for the conditions managed (Diabetes, CHF, Post-Discharge). Define interventions, escalation paths, and outcome metrics. Make Care Plans easy for coordinators to launch from a patient record.
- Configure HIPAA-compliant sharing and audit
Set up Private OWD for PHI-containing objects. Configure Sharing Sets and Sharing Rules to grant minimum-necessary access. Enable Field Audit Trail and Setup Audit Trail. Configure encryption for sensitive fields.
- Train clinical and operational staff
Health Cloud adoption depends on clinician and coordinator training. Build workflows that respect clinical reality, not just CRM logic. Adoption succeeds when the system makes clinical work faster, not slower.
Provider, Payer, Life Sciences, or Medical Device. Each role has different data models, workflows, and integrations.
Connection to EHR systems via FHIR endpoints. Foundation of clinical data interoperability.
Sharing, encryption, audit, BAA. The compliance foundation for handling PHI in the US.
- Health Cloud handles PHI. Without a Business Associate Agreement and proper HIPAA compliance configuration, PHI should not flow into the system. Compliance is the foundation.
- Healthcare integration via FHIR is more complex than typical CRM integration. The data shapes are domain-specific; testing with real clinical data is essential before production cutover.
- Clinical workflows must respect clinical reality. CRM-style configuration that ignores how clinicians actually work produces low adoption and patient-safety risk.
- The Person Account architecture has specific quirks. Health Cloud relies on Person Accounts; teams used to standard Business Accounts need to learn the differences.
- Industry-specific consulting expertise matters. Healthcare projects with only generic Salesforce consultants miss regulatory and clinical considerations that specialist partners catch.