One registration number, every department
The registration counter creates the patient record once. Every other module (queue, diagnostics, stores, wards, records and ABDM) adds to that same record instead of starting a new one.
A patient’s day in HMS
Not every patient takes every step, but every step they take lands on the same record.
-
Registration
The counter registers the patient once, with department, doctor and ABHA number, and prints the OPD slip.
-
Token and queue
A daily token is issued for the department and room, and the waiting-hall display calls it.
-
Diagnostics
The lab, radiology and cardiology record tests and results against the same registration number.
-
Medicines
Medicines are issued to the patient from department stock, building their medicine history.
-
Admission
If admitted, ward or casualty staff open the admission from the OPD record, and blood is issued from blood bank stock.
-
Reports to the patient
The patient looks up lab reports online with their registered mobile number, and prints them if needed.
-
Medical records
Case sheets, injury, death and X-ray records are scanned into the record room with ICD codes.
-
Shared with consent
Visits and reports become care contexts the patient can link to their ABHA and share with consent.
Module by module, never a single switch-over
A hospital can’t stop for a software change. Each module goes live on its own and is proven in daily use before the next one follows, on the hardware and network the hospital already has.
See how DMCH rolled out-
1
Registration first
OPD and IPD registration go live first, because they create the identifier every other module depends on. Counter staff are trained on a single, keyboard-first screen.
-
2
Diagnostics and stores
Pathology, radiology and cardiology attach to that identifier, followed by the central drug store and department medicine stores.
-
3
Wards, blood bank and records
IPD, the casualty ward, blood bank and record room follow: the areas where a lost entry has clinical consequences.
-
4
Staff and support
Staff attendance and the helpdesk come last, on the same servers and the same support line.
Under the hood
Simple to run on the hospital floor, dependable on the server.
Runs in the browser
Nothing to install on counter PCs. HMS runs in a modern web browser on the computers the hospital already has.
Your server or the cloud
Deploy on a server in the hospital or on cloud infrastructure, whichever your data policy needs.
Built for the morning rush
Designed around hundreds of patients queuing before 9 am, with caching and background jobs keeping counters quick.
A proven stack
Django and PostgreSQL, with Redis and Celery for caching and background work such as delivering ABDM records.
Prints on any printer
Slips, reports and registers print from the browser, with no special printer drivers.
Monitored and supported
Availability is monitored around the clock, and issues come in through the built-in helpdesk.
See Swastik HMS with your hospital’s departments
Book a walkthrough focused on the modules you want to start with.