The riskiest part of a hospital management system is not choosing it, it is going live. A hospital cannot close for a week while staff learn new software. This is the module-by-module implementation plan we use, shaped by digitising a large government medical college without stopping it.
Why a big-bang go-live fails
Switching every department on the same day means every problem happens at once: untrained staff, missing master data, network gaps and unexpected workflows, all in front of patients. Going live one module at a time keeps problems small, and each success builds confidence for the next department.
Phase 1: Prepare
- Map workflows. Visit every department and record how registers, slips and reports work today.
- Check infrastructure. PCs, printers, network points, power backup, and a server room or cloud connectivity.
- Agree reports. Collect every register and report format the administration needs.
- Name owners. One responsible person per department, plus an overall project lead.
Phase 2: Set up master data
Departments, doctors, rooms, users and roles, test catalogues, medicine lists and opening stock must be right before anyone uses the system. Poor master data is the most common cause of a bad first week.
Phase 3: Go live in the right order
| Order | Modules | Why this order |
|---|---|---|
| 1 | OPD and IPD registration, token queue | Creates the patient identifier every other module needs |
| 2 | Pathology, radiology, cardiology | High volume; results start building against real records |
| 3 | Central drug store and department stores | Needs accurate opening stock and department structure |
| 4 | Wards, casualty, blood bank, record room | Clinical and legal records where audit matters most |
| 5 | Staff attendance, helpdesk, ABDM sharing | Builds on sign-ins, users and existing records |
ABHA at registration can start in phase 1 if the hospital is ready; record sharing follows once the facility is onboarded as a Health Information Provider.
Training that works on a hospital floor
- Train at the actual counters and wards, on the screens staff will use.
- Keep registration keyboard-first so experienced staff stay fast.
- Train a “super user” in every department to help colleagues.
- Have the vendor’s team on site for the first days of each module.
Data migration: be selective
Migrating decades of paper registers is rarely worth it. Migrate what staff need to look up daily, such as current stock and active patient records, and keep older registers archived. Decide this early so it does not delay go-live.
Parallel running and cut-over
For a short period, a department may keep its paper register alongside the system to build trust. Set a firm end date; parallel running that never ends doubles the work.
Measure success
- Registrations per hour at peak time
- Share of lab reports delivered online
- Stock mismatches found at audit
- Support tickets per week, trending down
- Reports produced without manual counting
How we implement Swastik HMS
This is how Darbhanga Medical College & Hospital went live with our platform in 2024: registration first, then diagnostics and stores, then wards, blood bank and records, each proven in daily use before the next. Support continues through the built-in helpdesk with ticket tracking. Read more in how Swastik HMS works.
Planning a rollout? Ask for a module-by-module plan for your hospital.