Skip to main content
TRITECH Software

Case study · Web Application

MediPortal

CityCare Health Network runs eight clinics and was booking every patient over the phone. Appointment slots were managed on paper boards in each clinic. The network wanted a patient portal that reduced front-desk load while keeping patient data secure.

Client
CityCare Health Network
Industry
Healthcare
Year
2025
Duration
7 months
Team
5 engineers, 1 clinical lead, 1 designer
mediportal.build / productionLive
MediPortal interface preview

Results — in the client's own numbers

reduction in front-desk phone volume
41%
average booking time, down from phone calls
2.1 min
privacy incidents across 8 clinics
0

01The Problem

What wasn't working

A growing health network let patients book appointments by phone only, leaving front-desk staff overwhelmed and records fragmented.

02The Challenge

Where it started

The network's clinics each had their own scheduling rules: different consultation durations, different walk-in policies, and limited specialist availability. Any portal had to respect those rules per clinic without making the booking flow complicated for patients.

03Research & Planning

Finding the real problem

We observed front-desk staff across three clinics and mapped common call reasons. Booking took up most calls, but a surprising amount of call volume was 'where are my results?' and 'how do I get a record?' — which the portal could answer without staff involvement.

04Design

Designing for the people who use it

The portal needed to feel calm and trustworthy. We used a clean, high-contrast interface with large touch targets for patients booking from phones. Appointment statuses use clear, friendly language — no clinical jargon — while records views follow strict role-based visibility.

05Architecture

The technical blueprint

A Next.js application over a Node.js API, with PostgreSQL behind a schema that separates clinical data from scheduling. Access is governed by a role and relationship model (patient, guardian, staff, admin). Every record view writes to an immutable audit log. The system runs in Docker on the network's own cloud environment.

06Development

Building in shippable increments

We delivered the booking module first so clinics could retire paper boards, then added messaging, reminders, and records. A parallel-run period with one clinic caught scheduling edge cases before the network-wide rollout. Security testing focused on authorization boundaries between patients, guardians, and staff.

07Final Solution

What shipped

A secure patient portal with online booking, record access, and two-way messaging — built to local healthcare privacy standards.

All eight clinics now use MediPortal. Front-desk staff spend their time on patients who are actually in the clinic instead of managing phone queues, and patients get answers about their records without making a call.

08Key Features

What the product does

  • Online appointment booking with live availability
  • Secure patient record and document access
  • Two-way secure messaging with staff
  • Automated appointment reminders via SMS and email
  • Guardian-managed access for dependents
  • Audit log for every record view

09Technology

The stack

  • React
  • Next.js
  • TypeScript
  • PostgreSQL
  • Node.js
  • Redis
  • Docker

10Screenshots

The interfaces in production

Select any screenshot to view it up close. Use the arrow keys to move between them.

  • 01Patients book and manage appointments with live clinic availability.
  • 02Secure access to results and records, with a full audit trail.

Our front desk can finally breathe. Patients like it more than we expected — the reminder messages alone cut our no-show rate noticeably.

Dr. Grace Mendoza

Medical Director, CityCare Health Network

11Related work

More projects like this

View all work
  • Nexa CRM preview
    Web Application

    Enterprise Services · 2025

    Nexa CRM

    A 400-agent service organization tracked customers across spreadsheets and email, with no single view of a relationship.

    shorter average resolution time
    32%
    from kickoff to first usable release
    14 days
    faster new-agent onboarding
    3.5×
  • LedgerFlow preview
    SaaS

    Financial Technology · 2025

    LedgerFlow

    A fintech startup needed a subscription billing platform that could handle complex pricing — without building billing from scratch in-house.

    merchants onboarded in the first year
    2,300+
    scheduled invoice accuracy
    99.9%
    reduction in failed payment revenue loss
    38%