For years, healthcare organizations have had the data and the automation to drive better patient engagement. What they've lacked is a central content layer that connects to both. Content lives in marketing tools, SharePoint folders, websites, and apps that don't talk to anything else.
Salesforce's agreement to acquire Contentful changes that.
Contentful is a headless CMS used by more than 4,800 organizations. That number includes around 30% of the Fortune 500 and more than 3,500 healthcare brands. It holds structured content like marketing copy, media, templates, and web components. The beauty of headless CMS is that you can put this content in one place, and it gets delivered across any channel. Once it sits inside the Salesforce ecosystem alongside Data 360 and Agentforce for healthcare, it becomes a single system that knows who the patient is, what they need, and what to say to them.
Contentful in Healthcare
Most industries struggle with personalization that goes beyond piping a person's name into an email. That's still a problem in healthcare, but we're also fighting data fragmentation.
Then when you multiply those issues across every channel a patient interacts with, it quickly becomes clear why a headless CMS is so attractive.
At a typical healthcare provider, content lives all over the place. Sometimes it's decentralized in a Word or Google doc. Marketing content doesn't live in the same system as clinical content. That means marketing and clinical teams are creating redundant content that lives in a vacuum.
With Contentful, marketing and clinical content are stored as structured, reusable entries in the same place. That includes provider bios, service line pages, condition explainers, care plan instructions, appointment prep guides, and more. This content can then be served to every patient-facing asset, including the website, patient portal, mobile app, and in-room TVs.
The Architecture: What Each Piece Actually Does
Before getting into the use cases, it's worth being specific about how these tools fit together, because the pitch of "Contentful plus Salesforce equals better engagement" misses the point.
Health Cloud is the relationship layer. It holds the patient's care context, their care team, their active conditions, and their communication history. Data 360 is the identity and signal layer. It unifies behavioral data from every channel, resolves anonymous visitors into known patients, and keeps segments current as a patient's situation changes. Agentforce is the orchestration layer. It reads the context from Health Cloud, reads the signals from Data 360, and decides what content to surface, when, and through which channel. Contentful is the warehouse all of that points to.
Without Contentful, Agentforce knows who to reach and when to reach them, but it might be pulling from a generic template library. With Contentful, it's pulling from structured, clinically reviewed, procedure-specific content that's been approved by your compliance and clinical teams and never repurposed where it doesn't belong. That's the actual architecture. And none of it is hypothetical. We've built the Health Cloud, Data 360, and EHR integration side of this stack for health systems across the country. Contentful adds the content management component we've always had to source separately.
Contentful for Health Systems
This is where our imagination takes over.
The real value is personalization as a clinical and operational tool.
Take a knee replacement. The journey starts months before surgery and runs well past discharge. At every stage, the content a patient receives either reflects where they actually are, or it doesn't.
Today, it mostly doesn't.
Research and Awareness
A patient researching knee pain at 11pm finds a condition page that has nothing to do with what they've already read. They schedule a consultation and get a welcome email with generic "here's what to expect" copy that repeats information they found on their own two weeks ago. Their pre-op prep arrives as a PDF that covers seven different procedure types. Post-discharge, they get a portal message that says "please follow your discharge summary." Six weeks into recovery, nobody follows up.
With Contentful sitting inside the Salesforce stack, that same journey looks different at every step.
The condition page they land on at 11pm is tagged in Contentful by diagnosis category. Data 360 picks up the visit, starts an anonymous profile, and flags orthopedic intent. When they come back two days later and request a consultation, that profile merges with their new Health Cloud record. The welcome email that fires isn't generic. It pulls a surgeon bio, a procedure-specific explainer, and a "what to expect at your consultation" guide, all from Contentful, all scoped to knee replacement.
Pre-Op
Pre-op preparation arrives in weekly sequences tied to how far out surgery is. Week five is nutrition and activity. Week two is home prep and medication instructions. The content isn't rewritten for every patient. It's stored once in Contentful, structured by procedure and timeline, and Agentforce handles the delivery.
Post-Discharge
Post-discharge is where the real gap exists today. Most patients go home with paper or a generic portal message. With this architecture, discharge instructions are scoped to the actual procedure and the care team's protocols, delivered within hours, in the patient's preferred language, through the channel they actually check. A patient who has only ever opened portal messages gets a portal message. One who's been engaging through the mobile app gets a push notification.
Recovery content updates automatically based on where the patient is in the timeline. Week one exercise guidance looks different from week six. The portal doesn't have to be manually updated. The care team doesn't have to remember to send anything. Contentful holds the content library, Data 360 tracks where the patient is, and Agentforce activates.
And when the recovery is complete, the relationship doesn't go quiet. The system transitions the patient into long-term wellness content based on their history, demographics, and what they've engaged with throughout the journey. Annual joint health reminders. Mobility content relevant to their age. A request to share their story.
That's one procedure. Multiply it across every service line, every care pathway, and every patient population your health system serves.
The HIPAA Question
Contentful holds content. Patient health information lives in Data 360 and the EHR.
How they connect matters a ton for compliance.
The compliance work here is how patient identifiers are passed between systems, how content requests are scoped to avoid exposing PHI in unintended places, and how logging and audit trails are maintained across the stack. None of this is unsolvable. But it requires someone who has built HIPAA-compliant data architectures on Salesforce before.
Where Most Salesforce Partners Will Get This Wrong
The pitch from many Salesforce generalists will go something like: "Contentful plus Marketing Cloud means better campaigns." That's not untrue, but it's vague.
Health systems should not run marketing campaigns in isolation. You should be running patient experiences that involve clinical, operational, and compliance teams. A post-discharge message is not a marketing email. The architecture that handles these workflows has to account for Epic FHIR APIs, HL7 data flows, provider attribution, and PHI adjacency rules. That's a different build than what a generalist does on the daily.
Penrod's work sits at exactly this intersection. We design the content architecture that handles PHI compliantly, connects EHR data to marketing profiles, and serves clinical and administrative workflows alongside the communications team. We've done it for health systems across the country. The Contentful acquisition does not change our approach. It adds a content management component to an architecture we already know how to build.
The Timing Question
Health systems with active Health Cloud deployments should be having this conversation now. The architecture decision you make in the next six to twelve months can set you up to use Agentforce-driven content delivery at scale.
If you want to understand what this means for your specific environment, that conversation starts with a straightforward question: what does your current content and patient communication architecture actually look like, and where are the gaps? We can help you answer it.
Penrod is a healthcare technology consulting firm. We build Salesforce, data integration, and AI solutions for health systems. If you want to talk through what the Contentful acquisition means for your organization, reach out.