Overview
Hospital Management System work spans OPD, IPD, pharmacy requests, lab orders, and accounts — each with different roles and audit needs.
Problem statement
Patient data and billing were copied between desks, causing delays and disputes at discharge.
Requirements and constraints
Role-based access for admin, doctors, nurses, lab, pharmacy, and accounts. Bed state visible to admission. Bills tied to services rendered. Reports for management without exporting sensitive rows to this public site.
Proposed architecture
Laravel admin, relational schema per department, PDF receipts, and optional print layouts for local regulations when configured.
Database design
Patients, visits, beds, services, bills, payments, and users separated with foreign keys and soft deletes where recovery is required.
API design and authentication
Primarily server-rendered; mobile or kiosk APIs can be added per deployment.
Security
Health data stays on client infrastructure. This portfolio does not host or sample real patient records.
Performance
Indexing on visit date and patient lookup fields keeps front desk search responsive.
Testing and deployment
Acceptance testing follows client workflows: admit, order, bill, discharge.
Challenges and lessons
Hospitals name the same step differently. Labels and forms follow the client, not a generic HMS template.
Verified results
One operable HMS pattern documented here; go-live details remain with the client.