I Built a Clinic Web App by Shipping Phase 1 First (No, It's Not Done Yet)

Mehdi Aghaei — Sat, 01 Aug 2026 07:00:00 +0000

I Built a Clinic App

The Problem

Clinics drown in paper. Patient history gets lost between visits. Staff re-enters the same information over and over. I wanted to fix that with software—but I knew that "build a full clinic system" is the quickest path to burnout.

What I Built

Health Hub is a deliberate, one-phase clinic app for a doctor and assistant to manage patient records without the paper. It handles:

Permanent, reusable patient profiles
Smart duplicate detection (because yes, people with the same name exist)
Clinic-scoped access and role-based workflows
Search by name, phone, or date of birth
Clean API architecture (Django REST + PostgreSQL)

What I Haven't Built (Yet)

Visits. Scheduling. Appointments. Queue management. Notifications. Estimates. Notes.

These aren't bugs—they're deliberately out of scope for Phase 1. And honestly? That's the secret. I forced myself to stop at "working patient records," not "a complete clinic system that does everything."

The Stack

Frontend: React + Vite (fast, modern)
Backend: Django REST Framework + PostgreSQL
Deployment: GitHub Pages (demo), Docker Compose (local dev)
Testing: Django unit tests + React browser testing

Live Demo & Code

Try it: sorooshaghaei.github.io/health-hub

Code: github.com/sorooshaghaei/health-hub

What's Next?

Phase 2 is planned (visits, scheduling, queue behavior). But I'm not starting it until someone says "yes, this solves my problem." That's the discipline: no work without validation.

Your Turn

If this scratches an itch—or you think Phase 2 should prioritize something different—let me know. Or if you want to sponsor the next phase, I'm listening.

DEV Community: Mehdi Aghaei