Case study
Meridian Health
A patient portal used by 40,000 people a month, rebuilt from a collection of inherited screens into a system its own team could extend without asking a designer first.
- Client
- Meridian Health
- Year
- 2026
- Role
- Design system, front-end
- Duration
- Five months
Meridian had eleven years of accumulated screens and no shared vocabulary between them. Four different date pickers, three definitions of "urgent", and a colour that meant error in one section and success in another.
The problem was governance, not pixels
A redesign would have produced a twelfth date picker. What the team needed was a way to make the next decision consistently, so the work started with an audit of every component in production and a map of which ones were genuinely different.
- Sixty components, down from an inventory of two hundred and forty
- Every state designed up front, including empty, loading, and error
- Contrast checked against WCAG AA before anything was built
What shipped
The system went out in three releases over five months, each one replacing a section of the portal rather than the whole thing at once. Nothing was thrown away in a single night, and support tickets about the interface fell by roughly a third.