Skip to content

Meridian Health · Healthcare

Patient portal serving 40 clinics

A HIPAA-conscious patient portal that cut phone-based scheduling by 62%.

Industry
Healthcare
Services
Custom Software, Web Application, API Development
Stack
Next.js · Node.js · PostgreSQL · AWS
Timeline
9 months
Region
United States

-62%

phone scheduling reduced

71%

patient adoption in 6 months

99.98%

uptime since launch

0.9s

p95 page load

01

The challenge

Meridian's 40-clinic network ran scheduling, results delivery, and billing questions through call centers. Patients waited on hold; staff drowned in repetitive calls; no-show rates climbed. Two prior vendor attempts had stalled on integration with their legacy EHR.

02

The solution

We built a patient portal around the workflows patients actually need — book, reschedule, see results, message the care team, pay bills — with an integration layer that speaks to the legacy EHR through a hardened API gateway. Accessibility was a first-class requirement: the portal serves patients from 16 to 96.

03

Architecture & engineering

A Next.js frontend backed by a Node.js API layer; a dedicated integration service translates between modern JSON APIs and the EHR's HL7 interfaces, with an audit trail on every data access. Infrastructure runs in a HIPAA-eligible AWS environment with BAA coverage, encrypted at rest and in transit.

04

The outcome

Within six months, 71% of active patients had portal accounts and phone-based scheduling fell 62%. No-show rates dropped 18% on the back of automated reminders. The call center now handles exceptions, not everything.

Two vendors failed at this before Sydova. They shipped in nine months, and our patients actually use it — that's the whole story.
Danielle OkaforVP of Digital, Meridian Health

Services used

How we did it

Start a similar project

Facing a challenge like Meridian Health's? We'll show you how the same discipline applies to your roadmap.