01Case study
Piedmont
A health system redesign on headless Sitecore.
- Role
- Front-End Dev
- Agency
- MERGE
- Platform
- Sitecore
- Year
- 2025

02Overview
Redesigning care for Piedmont.
Piedmont needed a website that did more than describe its services. Patients come to a health system's site with a job to do: find care nearby, see how long the wait is, book an appointment, or check their health records. The old experience made them work too hard for those answers. Piedmont's content team also needed to publish and update pages quickly without waiting on developers.
03The experience


04Development
Built on headless Sitecore.
A Modern Headless Platform
We paired Sitecore’s content management capabilities with a Next.js frontend using Sitecore JSS. This allowed the frontend and backend teams to work independently while maintaining a shared content model. Reusable components were developed and tested in Storybook, creating a scalable design system that could grow with the site.
Making Care Easier to Find
One of the biggest priorities was helping patients quickly find the right care. We built search experiences for providers, locations, services, and immediate care, with filtering, sorting, location-based results, and interactive maps. A persistent quick-access experience also gives patients access to important actions like Find Care and MyChart from anywhere on the site.
Connecting Patients to MyChart
We integrated Epic MyChart using SMART on FHIR, allowing patients to securely sign in and access personalized healthcare experiences without storing their health information on Piedmont’s web servers.
Smarter Search
Piedmont manages a large amount of healthcare content, so we created search experiences tailored to different content types. Patients can quickly search and filter providers, locations, medical services, articles, news, and patient stories rather than navigating through traditional page hierarchies.
Built for Content Authors
We created a library of roughly 50 reusable components that Piedmont’s content team can assemble directly within Sitecore. Components, global settings, SEO controls, and structured content were designed to give editors more control while reducing their dependency on developers.
Accessibility at Every Step
Accessibility was considered throughout development, including keyboard navigation, screen-reader support, focus management, responsive interactions, and mobile usability. The goal was simple: make essential healthcare information easy to access regardless of device or ability.
Reliable Delivery
Automated GitHub Actions pipelines supported development, QA, staging, and production environments. This allowed the team to continuously ship improvements while maintaining a stable production experience throughout a large, long-running implementation.
05Let's work together
Have a project in mind?
I'm always open to new opportunities, interesting projects, or just some good conversation.