CASE STUDY

Example buildWeb App

Clinic Appointments & Records

Appointments, patient history and prescriptions in one place, with reminders that cut the empty slots.

Type
Web app
Build time
About 7 weeks
Platforms
Desktop at the desk, phone for patients
Starts at
₹20,000*

This is an example build. HumansOfCoding is a new studio with no client work to show yet. This page describes how the project would be scoped and built — the same thinking you would get on a real one. Nothing here is a past client, and no number on this page is a result.

THE SITUATION

What's actually broken.

A two-doctor clinic books appointments in a paper diary and keeps patient history in files. Patients are given a vague time and wait. Records are hard to find when someone returns after a year.

Patient data raises the stakes here. This is health information: it needs proper access control, an audit trail, and an honest conversation about where it is stored before a line is written.

  • Appointments in a diary that only the front desk can see

  • Patient history in paper files that go missing

  • Waiting rooms full because everyone was told “morning”

  • No reminder, so a fifth of slots are no-shows

VERSION ONE

What we'd build first.

Every item here earns its place by being something a real user would miss on day one.

Real appointment slots

Per doctor, with actual durations, so a patient is given a time rather than a session.

Patient records

History, visits, prescriptions, and uploaded reports, searchable by phone number — the only identifier patients reliably remember.

Prescriptions

Written on screen, printed on the clinic's letterhead, and kept against the visit.

Reminders

A message the day before and an hour before. This alone typically pays for the system.

Access control and audit

Reception sees the schedule, not clinical notes. Every record opened is logged, with who and when.

DELIBERATELY NOT IN V1

What we'd leave out.

Not because these are bad ideas. Because each one is designed better once the first version has told you something.

  • Insurance claim processing — a specialist domain with its own integrations and its own experts.
  • Lab and pharmacy modules, unless the clinic runs them in-house.
  • Video consultations. Link an existing tool from the appointment.

UNDER THE HOOD

How it's put together.

Web app
React, used at the desk and in the consulting room
Backend
Node with Postgres, with access logging built in rather than bolted on
Storage
Reports encrypted at rest, in an Indian cloud region
Reminders
SMS or WhatsApp, with the clinic name in the message
Backups
Automated daily, and restored once in front of you so you know the restore works

HOW IT RUNS

Week by week.

  1. 01

    Week 1

    The visit flow, and a decision about where patient data lives and who may see it.

  2. 02

    Weeks 2–4

    Appointments, the schedule and the front-desk view.

  3. 03

    Weeks 5–6

    Records, prescriptions and uploads.

  4. 04

    Week 7

    Reminders, access logs, backup restore test, live.

BEFORE YOU START

Worth knowing.

Patient records carry legal obligations in most places, including India. I build the access control, encryption and audit trail; you should still have someone confirm your specific compliance duties. I will tell you what the system does and does not cover, in writing.

MVPs start at ₹20,000*. Final pricing depends on features and project scope. Third-party costs — cloud hosting, domains, external libraries, APIs, app-store fees and any other paid service — are billed separately and are not included.

Want this built for your business?

Tell us what you're thinking. We'll figure out the next step together.

Free 20-min idea call · No obligation

Book a Free Call