Skip to content
Senior web & app development · 20 capabilities
oakstone.digital
Case study / Northstar Health

Turning complexity into a category leader.

A new website and patient portal made a specialist healthcare network easier to choose, understand and trust.

Industry
Healthcare
Duration
14 weeks
Division
Websites & Commerce
Year
2025
Northstar Health — healthcare web development project by Oakstone
Websites & Commerce / delivered
2.8×
qualified referral pipeline
+118%
organic traffic to condition pages
AA
WCAG 2.2 conformance
The challenge

Northstar ran eleven specialist clinics under one brand, each with its own referral pathway and each described in the language of the department rather than the patient. Referrers could not tell which clinic to send someone to, and patients arriving from search landed on pages that assumed clinical knowledge they did not have.

The site also failed basic accessibility checks, which for a healthcare provider is both an exclusion problem and a procurement one.

The move

We restructured the site around conditions and referral pathways rather than internal departments, so both audiences could self-select in one step. Every clinical page was rewritten with a reviewer in the loop and versioning recorded in the CMS.

A lightweight patient portal replaced a PDF-and-email intake process, holding the minimum data required with audited access. Accessibility was rebuilt at component level and verified with screen-reader testing on every referral journey.

The result

Referrals arrived at the right clinic without triage, and the intake team stopped re-keying forms. Organic traffic to condition pages more than doubled within two quarters as the new structure matched what people actually searched for.

The site now conforms to WCAG 2.2 AA with automated checks in CI, which unlocked two commissioning conversations that had previously stalled on accessibility evidence.

They brought strategic pressure that made every decision better. The work is beautiful, but the referral quality is what keeps showing up.
Jon Bell
Founder, Northstar Health
Stack
Next.jsTypeScriptSanity CMSPostgreSQLVercelAxeNVDA
Team

One strategist, one designer, two engineers, part-time accessibility specialist

Constraints
  • Clinical content required named reviewer sign-off before publication
  • Patient data limited to the minimum required, with audited access
  • Referrer workflows could not change during the transition
What we would do differently

We modelled conditions before we had mapped referral pathways, and rebuilt part of the content model in week six as a result. Pathways should have come first — they are the structure both audiences actually navigate by.

The accessibility work would have been roughly a third cheaper if the component annotations had existed at design stage rather than being retrofitted after the first build.

A better brief starts here

Your next proof point is waiting.

Bring us the hard thing. We will bring a point of view, a senior team and a clear next step.

Start a conversation