We're at HIMSS 2026 in Las Vegas this week — come find usHIMSS 2026 Schedule a meeting
Case Study
Health System
A 12-hospital health system in the Southeast had attempted a Salesforce Health Cloud implementation 18 months prior with a large consulting firm. The project stalled after the discovery phase when the senior architects who led the sales process were replaced by junior consultants unfamiliar with clinical workflows and healthcare data models.
The resulting implementation was technically functional but clinically irrelevant. Care coordinators abandoned the platform within three months of go-live, reverting to spreadsheets and phone calls. The health system had invested significant budget with nothing to show for it.
Leadership required a new implementation partner who could guarantee that the practitioners who scoped the work would be the same people who delivered it. They also needed the new implementation to integrate with their Epic EHR for real-time ADT feeds and patient demographics, which the previous implementation had deferred indefinitely.
Selah Digital assigned a two-person senior team to the engagement: a Salesforce Health Cloud architect with ten years of healthcare CRM experience and a clinical integration engineer with deep expertise in Epic FHIR APIs and HL7v2 messaging. Both practitioners participated in every phase from discovery through production cutover.
The first four weeks focused entirely on clinical workflow analysis and integration architecture. Rather than configuring Health Cloud features immediately, the team mapped the care coordination workflows across all 12 facilities, identified the data dependencies for each workflow, and established the integration patterns with Epic that would support real-time patient context in Health Cloud.
The Health Cloud data model was designed with clinical governance from day one. A cross-functional steering committee including nursing leadership, care management directors, and IT reviewed every custom object, field, and automation rule before it was built. This governance process added two weeks to the design phase but eliminated the data model drift that had plagued the previous implementation.
MuleSoft was deployed as the integration middleware, handling ADT feeds from Epic via HL7v2, patient demographics via FHIR R4, and care plan updates bidirectionally. The integration architecture was completed and tested before any Health Cloud features were developed, ensuring that every feature was built on real data.
The implementation was completed in 16 weeks, four weeks under the contracted timeline. The same two senior practitioners who led the discovery delivered the final production cutover. There were zero post-sale handoffs and zero staffing changes throughout the engagement.
Care coordinator adoption reached 94% within the first 60 days of go-live, compared to less than 20% on the previous implementation. The difference was attributed to the clinical relevance of the workflows, the real-time patient data from Epic, and the fact that care coordinators had been involved in the design process.
Key quantitative outcomes included: care plan creation time reduced by 62%, from an average of 23 minutes to 8.7 minutes per patient. Readmission follow-up compliance improved from 71% to 93%. The integration layer processed an average of 14,000 ADT events per day with 99.97% uptime in the first six months.
A regional health plan built a unified member view across claims, eligibility, clinical, and engagement data using Salesforce Data Cloud with FHIR R4 integration.
A federal health agency deployed AI-assisted clinical documentation within a FedRAMP Authorized environment, meeting compliance requirements while reducing documentation burden.
Ready to Start?
At Selah, you talk to the person who will actually do the work — from the first call to go-live. No account managers. No bait-and-switch. No surprises.
