What roles does the RBAC system support?

Four: Chief Admin, Specialist Doctors, Reception/Staff, and Patients — each with a workflow tailored to what that role actually needs day to day, not a shared dashboard with hidden buttons.

Does the AI diagnostics feature replace a doctor's judgment?

No — it's a second read on imaging (X-ray, CT, MRI) that localizes anomalies with confidence scores, surfaced to doctors as an assist, not a replacement for clinical judgment.

Is there a live demo?

Not currently — the project is available to review on GitHub, with the codebase demonstrating the full RBAC, diagnostics, and prescription-builder implementation.

HMS: Designing a Hospital Management System Around Roles, Not Just Features

Q: What does the bed/ward matrix actually show?

A live visual status grid across ICU, Emergency, General Wards, and Deluxe Suites with one-click admission, discharge, and sanitize toggling, so status reflects real-time operations instead of a stale count.

Most "management system" projects start from a feature list: add patients, add appointments, add billing. HMS started from a different question — who is going to open this screen — because a hospital's software has four completely different users doing four completely different jobs, and a single generic UI serves none of them well.

That framing is what shaped the whole architecture: role-based access control isn't a permissions afterthought bolted onto a finished app, it's the thing the app is organized around from the first screen.

Four roles, four workflows

Chief Admin — oversight across the whole system
Specialist Doctors — patient records, diagnostics, prescriptions
Reception / Staff — admissions, scheduling, day-to-day operations
Patients — their own records and appointments, nothing more

Each role gets a tailored workflow rather than the same dashboard with some buttons hidden — which matters more than it sounds, because a doctor's actual daily friction (fast access to a patient's vitals and history) is nothing like a receptionist's (fast bed/ward status and admission flow).

AI-powered diagnostics

Beyond the RBAC layer, HMS includes a computer-vision diagnostics module that analyzes X-rays, CT scans, and MRIs to localize anomalies and return confidence scores — giving doctors a second read on imaging rather than replacing their judgment, surfaced directly in the same interface they already use for patient records.

The live bed and ward matrix

Hospital operations live and die on bed availability, and a static "beds: 12/40" counter doesn't tell staff what they actually need to know. HMS renders a visual status grid across ICU, Emergency, General Wards, and Deluxe Suites, with one-click admission, discharge, and sanitize-status toggling — so the system reflects real-time operational state instead of a number that's stale the moment someone's discharged.

E-prescriptions with real vitals, not just a text box

The prescription builder captures real-time vitals — blood pressure, heart rate, SpO2, temperature, weight, BMI — alongside a multi-drug dosage builder with dietary guidance, and outputs an instantly printable/PDF-formatted prescription. The goal was to make the digital version strictly better than a paper pad, not just a digitized copy of one.

Why "who uses this" beats "what does this do"

Starting from roles instead of features forced earlier decisions about data access, UI layout, and even database schema (permissions modeled at the query layer, not just hidden in the frontend) that would have been much more painful to retrofit after the fact.