Salesforce Health Cloud Implementation

Health Cloud, Service Cloud, Marketing Cloud, and Sales Cloud configured for healthcare. Patient 360 views that pull from your EHR in real time. Care coordination workflows that connect clinical and non-clinical teams. Risk stratification, Agentforce, and EHR integration via FHIR R4 and HL7. I have done this with Epic and eClinicalWorks in production.

Salesforce in healthcare is not a CRM problem

Most organizations I talk to have one of two problems. Either they bought Salesforce, paid for Health Cloud, and have nothing to show for it because the implementation stalled. Or they know they need Health Cloud but nobody on their team has actually configured it, integrated it with an EHR, or gotten clinical staff to adopt it.

The first situation is more common than you think. A healthcare organization licenses Salesforce. A consulting firm does a discovery phase. They produce a roadmap. The roadmap sits in a Confluence page. Six months later the license renewal hits and nobody has logged into the org in weeks. The data model is half-built. The EHR integration was never started. The clinical team went back to spreadsheets and the patient portal.

The second situation is just as bad in a different way. The organization knows Health Cloud could solve their care coordination problems. They know Patient 360 would give their care managers a unified view instead of toggling between the EHR, a phone log, and a shared Google Sheet. But their IT team is maxed out on EHR upgrades and they do not have a Salesforce architect on staff. So they keep limping along with the tools they have, and the care gaps keep piling up.

Either way, the result is the same. Salesforce is costing money and delivering nothing. The clinical team does not trust it because it was never finished. Leadership is frustrated because they paid for a platform that nobody uses. And the patients, the people who actually benefit from better care coordination, get nothing.

My approach: assess, configure, integrate, train

Every engagement starts with an org assessment. I log into your Salesforce org, look at the data model, the existing objects and fields, the active workflows, and the integration state. I check what licenses you actually have versus what you are paying for. I look at the EHR side too: what system you are running, what APIs it exposes, what data you need flowing in and out.

Then I build. Not a roadmap. Not a phased rollout plan that stretches over twelve months. A configured, integrated Salesforce org that clinical staff can log into and use.

Org assessment

Before writing a single line of configuration, I figure out what you actually need versus what you were sold. This means:

• License audit. Health Cloud, Service Cloud, Marketing Cloud, Sales Cloud. Which ones you have, which ones you are using, which ones are idle. I right-size the license footprint so you are not paying for seats nobody occupies.
• Data model review. I look at the existing objects, custom fields, page layouts, and record types. I identify what was configured correctly, what was half-done, and what needs to be rebuilt from scratch.
• Integration inventory. What is currently connected to Salesforce? What APIs are active? What middleware is in place? MuleSoft, Boomi, native Salesforce Connect, custom REST endpoints. I document what exists and what is missing.
• User adoption data. Login frequency, last activity dates, feature usage. This tells me whether the problem is configuration or change management. Usually it is both.

Health Cloud configuration

Patient 360 is the core deliverable. A single view that pulls demographics, encounters, conditions, medications, care plans, and communication history from the EHR into Salesforce. The care manager opens a patient record and sees everything without toggling to another system.

Health Cloud gives you the data model for this. The configuration work is mapping your EHR data to Health Cloud objects, building the Lightning pages, and setting up the care program templates that drive your workflows.

• Patient 360. FHIR R4 and HL7 integration pulls live data from Epic or eClinicalWorks into Salesforce Health Cloud objects. Encounters, conditions, allergies, medications, lab results. The care manager sees current data, not a stale batch sync from last night.
• Care coordination. Care program templates for chronic disease management, care gap closure, and transition planning. Tasks assigned to clinical and non-clinical staff. Status tracking. Escalation rules. The workflow that keeps patients from falling through the cracks.
• Risk stratification. Risk scores and care gaps surfaced in the Patient 360 view. Care managers can filter by risk tier and prioritize outreach to the members who need it most. The data comes from the EHR, the workflow lives in Salesforce.
• Agentforce. AI-powered agent workflows for patient communication. Appointment reminders, care gap outreach, post-discharge follow-up. The agent handles the routine outreach so your care managers spend time on the cases that require human judgment.

EHR integration

This is where most Salesforce implementations fail. Health Cloud is useless if it does not talk to your EHR. I have integrated Salesforce with Epic and eClinicalWorks using FHIR R4 APIs and HL7 interfaces. The integration is bidirectional: clinical data flows into Salesforce, and outreach, communication logs, and care plan updates flow back to the EHR.

• FHIR R4. Patient demographics, conditions, encounters, medications, allergies, and lab results pulled via FHIR R4 endpoints. This is the modern standard and the one I prefer. It is structured, versioned, and well-documented.
• HL7. For EHR systems or specific data flows that still rely on HL7 v2 messaging, I configure the interfaces and map the segments to Salesforce objects. ADT messages for admission/discharge/transfer events trigger care workflows in Salesforce.
• Epic. My Sandbox and production integration experience with Epic includes FHIR R4 patient data APIs and ADT event subscriptions. I have worked with Epic's integration engine to set up the data flows that feed Health Cloud.
• eClinicalWorks. REST API integration for practice management and clinical data. I have pulled patient demographics, encounter data, and care gap information from eClinicalWorks into Salesforce for care coordination workflows.

Change management

Configuration without adoption is expensive shelfware. I build change management into every engagement because I have seen too many Salesforce orgs get configured beautifully and then ignored.

• Role-based training. I train care managers, providers, and administrative staff separately because they use the system differently. A care manager needs to know how to work care programs and filter by risk tier. A provider needs the Patient 360 view and the communication log. An admin needs reporting and user management.
• Workflow documentation. Step-by-step guides for every common workflow. Not a 200-page PDF nobody reads. Short, specific procedures for the tasks people actually do every day.
• Adoption monitoring. I track login frequency, feature usage, and workflow completion rates after go-live. If a care manager is not using the care program module, I find out why and fix it. Could be a training gap, a configuration issue, or a workflow that does not match how they actually work.

Deliverables

Every engagement produces working systems, not documentation that describes systems someone might build someday.

• Configured Salesforce org. Health Cloud data model, Lightning pages, care program templates, risk stratification views, and workflow automation. Ready for clinical staff to log in and use.
• EHR integration. FHIR R4 and/or HL7 connections between your EHR and Salesforce. Patient data flowing in real time, not from a nightly batch sync. Communication logs and care plan updates flowing back.
• Agentforce workflows. AI-powered patient outreach configured for your use cases. Appointment reminders, care gap closure, post-discharge follow-up. Running in production, not in a sandbox.
• Role-based training. Training sessions for care managers, providers, and administrative staff. Customized to how each role actually uses the system.
• Documentation. Configuration documentation, integration specifications, workflow guides, and a runbook for day-to-day administration. Your team can maintain and extend the system after the engagement ends.

Proof points

These are not theoretical. This is work I have delivered.

• 5 to 250 users. I have configured Salesforce orgs serving small care teams of five and organizations with 250+ users across multiple clinic locations. The data model and workflows scale. The training approach changes because a five-person team and a 250-person organization have different adoption challenges.
• 5,000+ daily clinical calls. Salesforce Service Cloud handling thousands of daily calls in a clinical contact center. Queues, routing, case management, and reporting that keep the operation running without manual triage.
• 4 Salesforce certifications. I hold certifications across the Salesforce platform that cover Health Cloud, Service Cloud, and the architecture decisions that make these systems work in production healthcare environments.
• Epic and eClinicalWorks integration. Production integrations with both EHR platforms. FHIR R4 for patient data, HL7 for real-time events, bidirectional sync so Salesforce and the EHR stay current.

Related reading

I have written about the cost, timeline, and operational realities of Salesforce in healthcare: