Healthcare · Case study

Paper records and long queues replaced with one hospital system

A four-department hospital moved from paper files and spreadsheets onto one patient record, starting with the queue at the front desk.

All case studies
Buddha Hospital (placeholder photo)
Client
Buddha Hospital
Sector
Healthcare
Engagement
Custom Software Development
Status
Live, in daily use
The problem

Four departments, four versions of the same patient

Patient records, billing and departmental handoffs ran on paper and disconnected spreadsheets. Registration meant finding a file, and finding a file meant walking to another room.

The immediate symptom was queue length at the front desk. The underlying problem was that four departments each kept their own version of the same patient, and none of them agreed. Billing reconstructed charges after the fact, from notes.

Nobody in the hospital was asking for software. They were asking why a patient who had been treated last month had to be registered from scratch.

Constraints

  • Clinical staff could not stop work for training — the system had to be learnable in a single shift.
  • Existing paper records going back years had to remain retrievable during and after migration.
  • Intermittent power and connectivity meant the system could not assume the network was always up.
What we did

Discuss, Design, Develop

The same three steps as every engagement, applied to a hospital that could not stop working while we built.

  1. Discuss

    Two weeks on site, following patients from the front desk through consultation, pharmacy and billing. We mapped every handoff and every place a record was rewritten.

    What you get

    • Patient journey map, four departments
    • Written problem statement
    • Phase order agreed with department heads
  2. Design

    One patient record as the single source of truth, with department-specific views on top of it. Screens were designed around what staff already did, using their own terminology.

    What you get

    • Role-based workflow design
    • Registration and billing screens
    • Migration plan for paper records
  3. Develop

    Registration went live first, because the queue was the loudest problem. Billing, pharmacy and reporting followed once the front desk trusted the system.

    What you get

    • Four departments on one system
    • Historic records digitised and searchable
    • Staff trained, documentation handed over
The solution

One record, four department views

Registration, consultation, pharmacy and billing read and write the same patient record, each seeing only what that role needs.

Screenshots require written client permission and may need patient data redacted or replaced with demo records.

Outcome

What changed, measured

  • 12 → 3 min

    Registration time

    Median time from patient arrival to consultation-ready.

  • 100%

    Records digitised

    Historic paper records indexed and searchable.

  • 4

    Departments on one system

    Front desk, consultation, pharmacy and billing.

Technologies

Chosen for an unreliable network, not for a CV

Application

  • React
  • Node.js

Data

  • PostgreSQL
  • Offline-tolerant sync

Deployment

  • On-premise server
  • Nightly backup

They spent two weeks understanding how we actually work before writing a line of code. What came out of it fits the way we run, not the way software usually assumes we run.

Client name to be confirmed Operations Head, Buddha Hospital
Start with a conversation

Tell us what you are trying to do. We will scope it.

Priced per project or per engagement, no public rates. A 30-minute call is enough to tell whether we are the right fit.

WhatsApp us
Emailmail@bitgarage.com.npPhone / WhatsApp+977 985 787 3476
Time zoneNPT (UTC+5:45) · Sun–Fri, 10:00–18:00
WhatsApp