Healthcare Content Strategy
Your last agency built something beautiful, and legal wouldn’t let you ship it.
Compliance, accessibility and records aren’t a checklist you run at the end. They’re the environment the work is built for, by people who’ve shipped inside health systems.
Tell us what you’re working on. You get a content structure that carries regulatory difference by design, review rubrics a non-specialist can apply, and a human approver kept in every workflow instead of engineered out of it.
Or text 562-726-2287. Tell us the regulated environment you’re working in.
30,000 URLs
Four domains into one, Intermountain
2,500+ pages
Shipped for a surgical college
3 case studies
All genuinely healthcare
The short answer
Healthcare content has a constraint most sectors don’t: someone qualified has to approve it, and that isn’t negotiable no matter how slow it makes things. So the goal is never to remove the approver. It’s to make everything up to that point fast enough that the approver stops being the bottleneck, and to make sure nothing reaches them that shouldn’t have.
Regulatory obligations differ by entity, and that’s a structure problem before it’s a compliance problem. When several health systems merge, they arrive with different obligations about what must be said, where. Those differences have to be modelled into the content structure, not handled by remembering them.
A scored rubric does more for compliance than a style guide. Written criteria that a non-specialist can apply catch problems before a clinician or a regulator sees them. And some content shouldn’t be yours to maintain: on Intermountain, an external medical information API replaced thousands of pages of clinical content, which is both cheaper and safer than maintaining it by hand.
Sound familiar
You’ve paid for this once, then paid again to redo it.
You spent six months and thousands with a general web agency, and the design they delivered was beautiful and unshippable, because it violated HIPAA and your accessibility requirements.
You had to rebuild the whole thing months after launch, because the first vendor never really understood the regulated environment it had to live in.
Compliance, accessibility and records got treated as an afterthought, bolted on near the end instead of being the environment the work was built for.
The safe political choice kept being the big brand-name vendor, even when you suspected a smaller senior team would do it better.
Several systems merged, each arriving with its own obligations about what has to be said and where, and the whole thing holds together on someone remembering.
Every clinical page waits on one qualified reviewer, so it sits in a queue while they’re buried, and nothing you do seems to unblock it.
None of this means the rules are the problem. They aren’t going anywhere, and they shouldn’t. Here’s the version where the work clears them the first time.
The version where this ships
The work clears legal, compliance and accessibility the first time, from a team that has shipped inside health systems.
Not a beautiful design that dies in review. Not a rebuild six months after launch. Compliance, accessibility and records are the environment the work is built for, not a checklist someone runs at the end. The approver still approves, because that never goes away, but nothing reaches them that shouldn’t have, and everything before them moves fast enough that they stop being the bottleneck.
The track record
Three healthcare engagements, and all three are published.
This vertical has more proof behind it than any other page on the site. A multistate health system, a federal health agency, and a global surgical college. Here’s what each one actually was.
| Organisation | The problem | What we did | Outcome |
|---|---|---|---|
| Intermountain Healthcare | A multistate health system that had acquired several smaller networks. 30,000 URLs across four domains, each network with its own regulatory requirements. | Content models with SEO considered during modelling, a hybrid governance model, and the Wolters Kluwer API integrated. Brought in by the primary agency, embedded in their team. | Four domains consolidated into one site, and redundant clinical content removed permanently. |
| The FDA and HHS | A weekly AI news digest for a federal health audience. Enormous volume, most of it press releases and clickbait, and very few project hours. | A scoring workflow, with the effort spent on the rubric, because the first version scored everything highly. | Processing cost cut by three quarters. 10 to 14 articles per category still go to a human before anything is sent. |
| American College of Surgeons | A global surgical education body with a content operations problem: an unfamiliar CMS, no dedicated copywriters, a distributed team, and a deadline about to be missed. | A scored review rubric, so designers and developers reviewed against criteria instead of taste. | 2,500+ pages shipped and thousands in overage avoided. Launched two months late, a rescue, not an early delivery. |
What we do
What we actually do.
The same method behind all three case studies, and it starts from the constraint instead of fighting it.
- Regulatory difference modelled into the structure. Obligations become a property of the content type, not something a person has to remember.
- Scored review rubrics a non-specialist can apply. So clinical reviewers see fewer drafts, and better ones.
- Governance designed across merged or federated organisations. When several systems become one, the structure holds instead of decaying.
- Content identified that should be licensed, not maintained. Some clinical content is cheaper and safer to buy in than to keep by hand.
- A human approver kept in every workflow. We design around the approver, not against them, because that requirement isn’t going anywhere.
Before you hire us
What we’re not.
We’re not your regulatory or legal advisor
We don’t tell you what your obligations are. We build the structure and process that make meeting them repeatable, and your compliance people stay the authority on what those obligations are.
We’re not clinical reviewers
Nothing we build removes the requirement for qualified review, and we’d refuse an engagement whose goal was to remove it. That requirement is the one that keeps people safe.
What it costs
What a healthcare engagement costs.
This page doesn’t quote a number, and that’s deliberate. Healthcare buyers don’t scope from a web page, and every relevant floor already lives on the pricing page, reached through the two enterprise spokes. Tell us the regulated environment you’re working in, and we’ll scope it against what it actually needs.
Related
If it’s a different problem.
Enterprise content strategy
The general version, without the regulated-sector specifics.
Enterprise CMS migration
If consolidation is the actual project.
AI content operations
For the scored rubric and workflow layer on its own.
Enterprise
The whole picture this page is one spoke of.
Questions we get
What people usually ask.
No, and we’d refuse an engagement that tried to. The goal is never to remove the approver. It’s to make everything up to that point fast enough that the approver stops being the bottleneck, and to make sure nothing reaches them that shouldn’t have.
No. We don’t tell you what your obligations are. We build the structure and process that make meeting them repeatable, and your compliance people stay the authority on what those obligations are.
Yes, that’s a core part of the work. Different obligations about what has to be said, and where, get modelled into the content structure, so they’re a property of the content type instead of something a person has to remember.
Written criteria a non-specialist can apply catch problems before a clinician or a regulator sees them. Review becomes consistent instead of depending on who’s on the rota, and your qualified reviewers see fewer drafts, and better ones.
Healthcare buyers don’t scope from a web page, so this one doesn’t quote a number. The relevant floors are on the pricing page, reached through the two enterprise spokes. Tell us the environment you’re working in and we’ll scope it properly.
Close
Ship it once, and clear compliance the first time.
Content models that carry regulatory difference, rubrics your team can apply, and a human approver kept in every workflow by design.
Three published healthcare projects behind this, and a human approver in every one.