Healthcare organisations run on relationships and handoffs: referral to appointment, discharge to follow-up, enquiry to enrolment. Electronic health records are built to document clinical care, not to manage these journeys. That gap is where Salesforce Health Cloud fits.
This guide to Salesforce Health Cloud implementation explains what the product does, where it creates value for providers, payers and health services companies, how it integrates with the EHR, what compliance requires and how to plan a rollout that clinicians and operations teams actually adopt.
What is Salesforce Health Cloud?
Salesforce Health Cloud is a customer relationship management platform built for healthcare and related industries. It extends Salesforce with a healthcare data model, patient and member records, care coordination tools and industry-specific workflows, while keeping the flexibility, security and ecosystem of the wider Salesforce platform.
It is used by hospitals and clinic networks, home health and specialist providers, health insurers, and companies that support patients, such as medical device and patient services organisations.
Core Health Cloud capabilities
- Patient and member 360: a unified view of demographics, care team, conditions, coverage, communications and timeline, using person accounts and the Health Cloud data model.
- Care plans and care programs: structured goals, tasks and interventions for chronic care, post-discharge follow-up or patient support programmes.
- Referral and intake management: capture, triage, assign and track referrals from any channel through to scheduling.
- Appointment and scheduling tools for patient access teams.
- Provider network and relationship management for referral sources and network participation.
- Utilisation management capabilities for payers, such as prior authorisation workflows.
- A clinical data model aligned with HL7 FHIR standards, which simplifies integration with modern EHR APIs.
- Patient engagement through portals built on Experience Cloud, messaging and marketing tools.
High-value Health Cloud use cases
| Organisation type | Use case | What improves |
|---|---|---|
| Hospital or clinic network | Referral management and patient access | Referral leakage, time to appointment, visibility by referral source |
| Provider | Post-discharge care coordination | Follow-up completion, readmission risk management, care team handoffs |
| Specialist or elective care | Enquiry-to-treatment journey | Conversion of enquiries, patient communication, self-service booking |
| Payer or insurer | Member services and care management | Member experience, case handling, prior authorisation turnaround |
| Medtech or patient services | Patient support programmes | Enrolment, adherence support, field and hub team coordination |
Our homepage describes a representative engagement: closing the loop on patient access, where every referral carries a status, an owner and a next action while the EHR stays the clinical system of record.
How does Health Cloud work with the EHR?
The most important design principle is simple: Health Cloud complements the EHR; it does not replace it. Clinical documentation, orders and results stay in the EHR. Health Cloud manages the journey around care.
Typical integration design
- Patient identity: match and link patients using EHR identifiers, with clear rules for duplicates.
- Read clinical context: selected data such as upcoming appointments, conditions, care team or discharge summaries via FHIR APIs.
- Write back operational outcomes: for example scheduled appointments or referral status, where the EHR supports it.
- Event-driven updates: admission, discharge and transfer events can trigger follow-up tasks in Health Cloud.
- Integration layer: MuleSoft or another integration platform handles transformation, security and monitoring across EHR, scheduling, telephony and billing systems.
For the trade-offs between integration approaches, see MuleSoft vs custom APIs for Salesforce integration.
Compliance and security considerations
- United States: put a HIPAA business associate agreement in place with Salesforce for the services you use, and apply the minimum necessary standard to data you store.
- United Kingdom: meet UK GDPR requirements, and if you work with NHS data, align with the Data Security and Protection Toolkit expectations for suppliers and partners.
- India: plan for the Digital Personal Data Protection Act, 2023 and its rules, particularly consent and data principal rights.
- Platform controls: least-privilege permission sets, field-level security for sensitive attributes, and Salesforce Shield capabilities such as Platform Encryption, Event Monitoring and Field Audit Trail where required.
- Consent management: record communication preferences and consent explicitly and respect them in every automation.
Our guide to Salesforce security and access control covers the underlying model.
A phased Health Cloud implementation roadmap
- Discovery (3–6 weeks): choose the first workflow, map the current journey with frontline staff, define measures such as time to appointment, confirm compliance requirements and integration scope.
- Design (3–4 weeks): data model decisions including person accounts, security and consent design, integration architecture, and prototypes of key screens with real users.
- Build (8–12 weeks): configure Health Cloud, build Flows and components, develop integrations, migrate reference data such as providers and locations.
- Test (3–5 weeks): integration testing with EHR test environments, security testing, and user acceptance testing with clinical and access teams.
- Pilot and launch: start with one service line or site, provide at-the-elbow support, then refine.
- Scale: add care coordination, portals, additional service lines or AI-assisted workflows using what you have already built.
Data model decisions to make early
A few design choices shape everything else in a Health Cloud project, and they are expensive to reverse later:
- Person accounts: Health Cloud represents patients and members as person accounts. Enabling person accounts cannot be undone in an org, so confirm how they affect existing business-to-business processes, integrations and reports before switching them on.
- Patient identity: decide which system assigns the master identifier, and how duplicates are detected and merged.
- Clinical data scope: store only the clinical information the workflow needs, and display the rest from the EHR where possible.
- Households and relationships: caregivers, guardians and care team members need clear relationship rules and access controls.
- Consent and preferences: model consent by channel and purpose, and make every automation check it.
How much does a Health Cloud implementation cost?
Costs depend on the number of workflows, EHR integration complexity, portal requirements, data migration and compliance validation. A focused first phase is usually a mid-sized project, while multi-site programmes with several integrations are enterprise-scale. Health Cloud licences are separate and priced per user. Our Salesforce implementation cost guide explains the drivers in detail.
Which KPIs show Health Cloud is working?
Agree measures and capture a baseline before launch, so success is visible to clinical, operational and executive stakeholders from the first release.
| Workflow | Measures to track |
|---|---|
| Referral management | Time from referral to first appointment, referrals without an owner, conversion and leakage by referral source |
| Care coordination | Follow-up tasks completed on time, patients contacted after discharge, care plan adherence |
| Patient access | Abandoned enquiries, time to schedule, self-service bookings, no-show rates |
| Member services | Case resolution time, repeat contacts, member satisfaction |
| Adoption | Active users by role, and work managed in Health Cloud rather than spreadsheets or email |
Common Health Cloud implementation pitfalls
- Trying to rebuild the EHR in Salesforce instead of integrating the data that matters.
- Designing without frontline staff: schedulers, nurses and coordinators know where the real handoffs fail.
- Skipping the person account decision early; it affects the whole data model.
- Treating consent as a checkbox rather than a rule enforced in automation.
- Over-customising care plans before testing standard capabilities with real users.
- Launching everywhere at once rather than proving value in one service line.
Readiness checklist before you start
- An executive sponsor and a named clinical lead
- One clearly defined first workflow with baseline metrics
- Access to EHR integration documentation and test environments
- Privacy and security stakeholders engaged from discovery
- A plan for training and supporting frontline users
- Reasonably clean provider, location and service data
If you already run Salesforce, an org health check before adding Health Cloud reduces surprises during design.
Implement Health Cloud with Groviya
Groviya delivers Health Cloud programmes for providers and healthcare services organisations, from referral management and patient access to care coordination and EHR integration, with delivery teams in India, the UK and the USA. Explore our Salesforce implementation services or discuss your first Health Cloud workflow with our team.
