Healthcare · Enterprise · Real-time
Medical ERP (SridharERP)
Healthcare · Enterprise · Real-time
A full-stack hospital management platform integrating patient management, EMR, pharmacy, laboratory, nursing, ward management, billing, staff administration and analytics into one real-time system.
- 8
- Technologies
- 2
- Domains
- 4
- Capabilities
- 1
- Public links
Who it's for
Hospitals and clinics that need every department — reception, doctors, lab, pharmacy, wards, billing — working from one live picture of the patient.
Where it fits
Clinical operations where a lab result or a freed bed must reach the right person instantly; eight distinct roles from doctors to accountants.
The hard part
The problem
Hospital operations sprawl across many roles and departments that all touch the same patient. Keeping registration, EMR, pharmacy, lab, wards and billing consistent — in real time — is the core challenge.
Architecture overview
A Django REST backend with PostgreSQL and Redis serves a Next.js frontend. WebSockets push live updates — lab results, pharmacy stock alerts, emergency notifications and bed-occupancy changes — across the modules, while Redis caches read-heavy dashboards. JWT authentication with role-based access control spans eight distinct clinical and administrative roles.
Patient record at the centre · real-time spokes
events pushed over WebSockets
How it works
What's actually in it.
- 01Patient management, EMR, pharmacy, laboratory, nursing/ward, billing, staff and analytics modules.
- 02Real-time notifications over WebSockets for lab results, stock alerts, emergencies and bed occupancy.
- 03JWT authentication with role-based access control across eight roles.
- 04Redis caching for read-heavy analytics dashboards.
Engineering decisions
WebSockets for cross-department events
In a hospital, a lab result or a freed bed is only useful if the right person sees it immediately. Rather than polling, the system pushes domain events over WebSockets so pharmacy, wards and reception react in real time.
The trade-off
Real-time push adds connection state and a channels layer to operate, but polling at hospital scale would be both slower and heavier.
Technical highlights
- Eight-role RBAC spanning clinical and administrative staff.
- Real-time operational events across every module.
Claims & evidence
Role-based access control across eight distinct roles: doctors, nurses, pharmacists, lab technicians, accountants, receptionists and administrators.
Qualitative · Medical ERP feature set
Every statement above carries its evidence class — nothing is invented.
Tech stack
- Next.js 14
- TypeScript
- Tailwind CSS
- Django REST Framework
- PostgreSQL
- Redis
- WebSockets
- JWT
Want to go deeper on Medical ERP (SridharERP)?
I'm happy to walk through the architecture and the decisions behind it.