A healthcare website can look “fine” and still be slowing the organization down.
Content teams can’t make basic updates. Patients can’t easily find the right clinic, specialist, or service. Newly acquired entities sit on separate platforms with different branding, different workflows, and different rules. The site still loads, but behind the scenes, everyone is working around it.
That’s when a healthcare CMS stops being a website problem and becomes an operational problem.
APAX recently worked with UK HealthCare to bring St. Claire and King’s Daughters into the UK HealthCare digital ecosystem. The project was not just about a new look or a cleaner page structure. It was about modernizing the content platform so multiple healthcare entities could operate on a shared, mature foundation while still keeping their own business decisions, permissions, and configuration.
For hospitals and health systems considering a healthcare CMS modernization project, there are a few lessons worth paying attention to.
A CMS should help your team communicate clearly with patients, providers, staff, and the community. When the system makes that harder, the symptoms show up quickly.
You may recognize some of these:
That was the kind of problem UK HealthCare needed to solve after acquiring St. Claire Regional Medical Center and King’s Daughters Health System. Both needed to be brought into the UK HealthCare brand, CMS, and broader digital ecosystem. Their previous platform was limiting enough that even rudimentary changes were difficult. Re-theming the sites to match UK HealthCare’s brand was not realistic inside the old setup.
At that point, the issue was not whether the old system technically existed. It was whether it could support the organization going forward.
Health system websites do not operate like simple brochure sites.
A healthcare website needs to serve patients, families, providers, internal content teams, marketing teams, service lines, administrators, and sometimes acquired entities with their own structure and needs.
UK HealthCare also has a large academic and informational presence. Like other major academic health systems, people may come to the site not only to find a location, but to understand a condition, treatment, test, specialist, or service. Those pieces of information need to connect in a way that makes sense.
That creates a lot of complexity.
A patient may start with a symptom. Another may search for a condition. Someone else may look for a provider, clinic, treatment, test, or location. Internal teams need to manage that information without needing a developer for every change.
A good healthcare CMS has to support all of those paths.
APAX built what the team refers to as UK Core: a Drupal multi-site solution that allows UK HealthCare, St. Claire, and King’s Daughters to operate from one shared code base.
The UK HealthCare codebase was not new. APAX has been maintaining, supporting, and improving it for years. Instead of starting over from scratch, the team was able to extend a mature foundation and bring the acquired entities into that ecosystem.
The result is a shared architecture with separate control where it matters.
Each entity can make site-level configuration decisions. Content permissions and publishing controls can be managed separately. Business decisions do not have to be identical across all three sites just because the codebase is shared.
That is one of the quiet strengths of a well-planned Drupal multi-site approach. The organization gets consistency, maintainability, and cost efficiency without forcing every site into the same exact operational mold.
For health systems that are growing through mergers or acquisitions, digital consolidation is rarely simple.
Each entity may come with its own website, CMS, vendor relationship, content habits, location data, provider information, and internal expectations. If every acquired entity becomes a fully separate rebuild, the cost and maintenance burden grows quickly.
A shared multi-site architecture can make that work repeatable.
Once the core platform is established, the next site does not have to start from zero. New entities can inherit mature functionality, proven content structures, and shared technical patterns. That gives the parent organization a faster path to brand alignment and a better experience for users.
In this case, St. Claire and King’s Daughters gained access to the broader UK HealthCare toolset much faster than they would have through a completely separate build.
That included the look and feel, content editing permissions, publishing capabilities, configurable patient tools, and a stronger search experience.
Healthcare CMS modernization has to improve both sides of the experience.
For patients, the goal is simple: help them find what they need. That may mean a specialist, a location, a service, or a care option. Strong search and well-structured data relationships are critical.
The APAX team emphasized the importance of relationships between conditions, treatments, tests, providers, and locations. Those relationships help users move through the site in ways that match real patient behavior.
Location information is a good example. It is not enough to list a large complex address and hope the patient figures it out. Healthcare locations often involve specific buildings, offices, hours, proximity, and service availability. Those details matter when someone is trying to get care.
For content teams, the goal is control. They need to update pages, manage patient tools, support campaigns, and publish accurate information without waiting on technical help for every change.
That is where a mature CMS earns its keep. It gives internal teams the ability to act without creating chaos.
If your hospital or health system is considering a CMS modernization project, start with these questions:
If your CMS is starting to feel outdated, do not start by shopping platforms.
Start with a short internal audit.
Ask your team:
Those answers will tell you whether you need a redesign, a CMS modernization, a content governance reset, a platform consolidation, or some combination of all four.
Healthcare CMS modernization is not just about replacing an old website. It is about giving patients clearer paths to care and giving internal teams better tools to manage complex information.
For UK HealthCare, the opportunity was to bring St. Claire and King’s Daughters into a shared digital ecosystem without losing the ability for each entity to make its own decisions. A mature Drupal multi-site architecture made that possible.
For other health systems, the takeaway is simple: do not underestimate the number of ways people use your site. Patients, families, providers, content teams, marketing teams, and administrators all depend on it in different ways.
The right CMS should support that complexity without making the experience feel complex.
If your healthcare organization is working through an outdated CMS, acquired entities, disconnected content, or a site that no longer fits how your teams work, APAX can help you think through the next right step.
