Skip to content
Shawon
All projects

Hospital Management System

Live in production

An operations system for a private hospital — eleven departments, seven staff roles and nine ledgers, all running from one admin.

Live sitePrivate codebase

Highlights

  • Seven role-based portals, from doctors to NICU and pharmacy.
  • Eleven departments, each with its own billing and reporting.
  • Nine ledgers reconciling into one revenue view.
  • Print layouts for bills and statements in A4 and A5.

The problem

A private hospital was running its departments on separate ledgers and paper records. Pathology kept its own books, the pharmacy kept its own, NICU and the hospital office each kept theirs, and nobody could answer what the hospital earned in a day without adding it up by hand. Patient records, bed status and appointments lived in the same scattered way, so a doctor could not see what pathology had already done for the patient in front of them.

What I built

I led the frontend for a system that runs the whole hospital from one admin. Eleven departments are covered — admissions, appointments, doctors, patients, pathology, pharmacy, NICU, emergency, ambulance, store and birth and death records — each with its own billing, configuration and reporting. Seven staff roles each see only their own department, with admins able to reach across all of them. Nine ledgers roll up into one revenue view, and every bill and statement prints in the paper format the hospital already used. The same admin also runs the hospital's public website: pages, blog posts, homepage sections, header and footer.

Challenges

  • Seven roles that overlap instead of nesting

    A pathologist is not simply a doctor with fewer permissions — the two see different departments entirely, while a hospital manager overlaps with both in some places and neither in others. A single permission level could not describe that. I gave each role its own route guard that answers one question, and let the admin and super-admin roles satisfy every guard, so adding a department later means writing one guard rather than rewriting a permission tree.

  • Nine ledgers that have to agree

    Pathology, pharmacy, NICU, emergency, the hospital office, ambulance, appointments and the patient and doctor ledgers each bill separately, and the hospital needs a single daily revenue figure out of them. The risk is double counting: a pathology test billed inside an admission must not also appear as its own pathology sale. Each department writes to its own ledger and the revenue view reads from all of them, so a department can change how it bills without the total quietly breaking.

  • The hospital still runs on paper

    Staff needed printed bills, doctor statements and patient ledgers in the exact formats they already used, including A5 for the smaller counter slips. Browser printing is not forgiving — what looks right on screen breaks across page edges. I built dedicated print layouts rather than styling the screen views for print, so the printed page is designed as a page and the screen stays designed for a screen.

  • Staff who are not developers edit the public website

    The hospital's public site — homepage sections, about and diagnostic pages, blog posts, header and footer — is edited from the same admin the staff already use. That meant every editable area had to fail safely: an empty field cannot break the public page, and someone who has never seen HTML should not be able to put the site in a broken state from a form.

Outcome

In production and in daily use across every department of the hospital. The system replaced separate per-department books with one view of the day's revenue, and gave each role a single place to work instead of a mix of paper and spreadsheets.