Skip to content
About
Our WorkProductsBlogGet a Quote
Our WorkCase Study

Meridian Health

A patient portal and scheduling system built around careful data handling and a booking flow patients actually complete on the first try.

Industry

Healthcare

Services

Web Applications, UX Research

Platform

Web Application

Technology

Next.js, Laravel API, MySQL

Clinician reviewing the Meridian Health patient app on a smartphone
The Challenge

Meridian Health's booking flow was losing patients partway through — appointment scheduling asked for too much, too early, and the portal handled sensitive data without the careful structure that kind of information needs.

The challenge was a booking flow patients would actually finish, built on a foundation careful enough for real patient data.

Our Role
  • UX Research

    Understanding exactly where patients dropped out of the existing booking flow.

  • Web Applications

    Building the patient portal as a custom, carefully-structured web application.

  • Scheduling Systems

    Designing a booking flow around the fewest steps to a confirmed appointment.

Clinician reviewing the Meridian Health patient app on a smartphone, shown wide
Approach

From problem to product.

01

Discover

Traced exactly where patients dropped out of the existing booking flow.

02

Define

Scoped the rebuild around a shorter path to a confirmed appointment.

03

Design

Designed a booking flow patients could complete in a handful of steps.

04

Build

Built the patient portal with careful handling for sensitive health data.

05

Launch

Rolled the new portal out to patients alongside the existing scheduling system.

Design & Experience

A booking flow patients actually finish.

Clinician reviewing the Meridian Health patient app on a smartphone, detail view

The patient portal — redesigned around a shorter, clearer path to a confirmed appointment.

The booking flow's structure, abstracted — fewer steps between intent and a confirmed slot.

Engineering

Built for what comes next.

A patient portal engineered around careful data handling from the first layer up.

Layer 01

Patient Portal Layer

The patient-facing booking and records experience — responsive, and built for clarity.

Layer 02

Scheduling Logic Layer

Appointment, provider and availability logic built around the redesigned flow.

Layer 03

Patient Data Layer

Sensitive patient data structured and access-controlled with care.

Layer 04

Hosting & Delivery Layer

Infrastructure built with the reliability a healthcare platform requires.

Technology Used

NE
Next.js
LA
Laravel
MY
MySQL
AC
Access Control
Key Capabilities

What was delivered.

01Patient Portal
02Appointment Scheduling
03Secure Data Handling
04UX Research
05Performance Optimization
06Access Control
Outcome

Designed to work. Built to last.

A shorter, clearer booking flow changed how many patients actually completed scheduling — and a more careful data foundation gave the platform room to grow.

Have something worth building?

Tell us what you’re working on and let’s figure out what’s next.