Hospital Software Go-Live Checklist and Common Mistakes

Most hospital software projects succeed or fail in the weeks around go-live, not in the demo. A calm switch-over needs clean data, trained staff and a clear cutover plan. Use this checklist and learn from the mistakes that hospitals repeat.

Four to six weeks before go-live: prepare the data

• Tariff list. Collect every chargeable item: consultation, bed categories, procedures, nursing charges, lab tests, radiology and consumables. Agree one official list and fix inconsistencies before entering anything.
• Doctor master. Names, departments, consultation fees, follow-up rules and any share arrangements.
• Ward and bed master. Wards, categories, bed numbers and daily rates.
• Pharmacy stock. Do a physical count with batch numbers and expiry dates. Opening stock is only as good as this count.
• Lab test catalogue. Tests, sample types and the reference ranges your lab uses. These come from your pathologist, not from the software company.
• Patient list. Export active patients from any existing file. Decide how far back to import and clean duplicates first.

Three weeks before: set roles and print formats

List every staff member and the role they will have. Decide who is the system administrator and who approves concessions or cancellations. Review each print format: OPD ticket, receipt, final bill, lab report and discharge summary. Check spellings, logos, registration numbers and signatures on a printed sample.

Two weeks before: train by counter

Group training by role. Reception practises registration, search and tokens. Cashiers practise receipts, deposits, refunds and day closing. Nurses practise admission, bed transfers and charge entry. Pharmacy staff practise purchase, issue and returns. Doctors practise viewing the queue and ordering tests. Use realistic dummy patients and let staff make mistakes in the training copy.

Include night staff. A system that only the day team understands will be bypassed after dark.

One week before: parallel run

Run the new system alongside the paper register for a limited period. At the end of each day compare totals: patients registered, cash collected, bills raised. Any difference points to a missing tariff, a wrong fee or a habit that needs correcting. Keep a shared list of issues and assign each one.

Check	Paper total	System total	Difference and reason
OPD patients
OPD cash
Lab tests done
Pharmacy sales
Admissions and discharges

Cutover day

1. Choose a quieter day and start at the beginning of a shift or fiscal period if possible.
2. Close the paper register with a clear last number.
3. Enter currently admitted patients with their deposits and charges to date.
4. Post a contact sheet at each counter with the support number and the internal administrator.
5. Keep paper forms ready as a fallback for the first days in case of a power or network problem.
6. Take a backup at the end of the day and confirm it exists.

The first week

Expect questions, not disasters. Hold a ten-minute meeting each morning to collect issues. Fix tariff errors the same day. Watch for staff who quietly return to paper and ask them what is slowing them down. Review the daily closing report with the accountant to confirm figures match cash.

Common mistakes

• Entering messy data. Duplicate patients and inconsistent test names stay with you for years. Clean first.
• No owner inside the hospital. Someone must have time and authority to make decisions. If everyone is responsible, nobody is.
• Everyone is administrator. Broad rights defeat the purpose of an audit trail.
• Skipping night and weekend training. Problems appear when the project team is away.
• Switching all modules at once. A phased rollout is easier to manage. Start with front-of-house, then widen.
• No backup routine. Decide who checks it every day, and test a restore.
• Changing the tariff mid-migration. Freeze it until the system is stable.

Who does what on the project

Name the roles clearly at the start. The hospital needs a sponsor (usually the director) who makes decisions quickly, a project lead who coordinates staff and the vendor, a champion in each department who knows the daily work, and an administrator who will manage users and backups afterwards. The vendor provides set-up, import, training and support. Write the names on one page and review progress weekly. Projects stall most often because a decision, such as which tariff is final, waits for a meeting that never happens.

Keep a simple issue log with the date, who raised it, what was decided and who fixed it. This log becomes the training material for new joiners and a useful record if you later change a process.

After the first month

Review the reports. Which departments have rising dues? Which doctors have the longest queues? Are any beds always empty? This is when software starts to inform decisions. Plan the next module, such as a dedicated lab system if your lab outgrows the built-in one, or SMS reminders for follow-ups.

Next step

Pick a target go-live date about two months away and work backwards with this list. WebsNP supports this planning as part of our hospital management software rollout, including data import and training. Message us at +977 9846280400 and we will draft a plan around your wards and counters.

Get a demo and quote for Hospital Management Software

Tell us about your business and we will reply the same working day with a demo and a clear quote. No obligation.

Chat on WhatsApp

Or call / WhatsApp +977 9846280400

Your name Phone / WhatsApp Email (optional) Business / organisation What do you need?

Request demo

More guides on Hospital Management Software