Hospital management system in Pakistan: what to demand before you buy

A hospital management system in Pakistan has one job that matters more than any feature list: a single patient record that registration, the ward, the lab, pharmacy and billing all trust. Most hospitals we meet run five to eight tools that each hold part of that record, and the clerks are the integration — re-typing the same CNIC and encounter into one screen after another. This guide is what to demand from any vendor, including us, before you sign.

It is drawn from replacing seven systems for a multi-facility hospital group in Punjab: 34 weeks, not one hour of downtime, and patient waits about a third shorter at the measured sites. The case study is here. Two earlier replacements at the same group — one from a multinational, one from a local vendor — had been abandoned, and why they failed is most of what follows.

One patient, one record

The CNIC is the obvious key, and it is not enough on its own. Children are registered on a B-form, emergency patients arrive with no documents, foreign patients carry passports, and the same family name is spelled three ways in English and once in Urdu. A system built for Pakistani hospitals detects likely duplicates on name, father's or husband's name and phone number, lets a supervisor merge records with an audit trail, and carries the medical record numbers over from the old system so that last year's files still mean something.

The modules that matter on day one

• Registration, OPD tokens and appointments, so the queue at the counter is the first thing that gets shorter.
• Admissions with a live bed and theatre board the duty manager can actually use, instead of three phone calls.
• Pharmacy with batches and expiry dates, dispensing against the doctor's prescription rather than a handwritten slip.
• Lab and radiology orders and results, attached to the patient rather than to a printout.
• Billing that handles cash, corporate panels, insurers and government health-card schemes, plus consultant shares — usually the most complicated rules in the building.

What can wait for phase two: HR and payroll, general store inventory beyond the pharmacy, and the patient mobile app. They are real needs, and none of them is why the counter queue is long.

Integration is not optional

Lab analysers, imaging systems, the accounting package and SMS reminders all need to talk to the HMS. HL7 FHIR is the standard way to do the clinical part, and a vendor who supports it should be able to show you a live interface rather than a slide. Ask specifically about the analysers you already own: an integration that works with one manufacturer's machine does not automatically work with yours.

Built for the ward, not the boardroom demo

Ward Wi-Fi drops out, rounds happen on tablets, and the night shift is not the day shift. Look for screens that tolerate a weak connection without losing an entry, Urdu and English interfaces, and access controlled down to the individual field so a receptionist cannot read a diagnosis. Then ask how training is delivered. Ours happened on the floor, across every shift, during Ramadan rosters as well as ordinary weeks — because a system nobody was trained on at 3 a.m. is a system that gets bypassed at 3 a.m.

Migration is where hospital systems fail

Both failed projects at our client promised a weekend cutover: switch off the old systems on Friday, switch on the new one on Monday. In a hospital that never happens cleanly, and when it goes wrong patients wait while staff fall back to paper.

We built the single patient record first and ran it beside the old systems, syncing both ways. Once ward staff trusted it, we moved admissions, then pharmacy, then billing, each with a rollback plan. The last legacy login was switched off in week 31, and no facility lost a working system for an hour. Ask every vendor for their migration plan in writing; if it fits on one slide and ends on a Monday, keep looking.

Patient data and audit

Medical records are the most sensitive data most organisations will ever hold. Every view of a record should be logged with who looked and when, not just every edit. Backups should be restored on a schedule, not assumed. If your board or a regulator requires data to stay in Pakistan, that is a hosting decision to make at the start. And ask the vendor which of their own staff can see patient data in production — the right answer is a short, named list.

What it costs, and when custom is the wrong answer

If a packaged HMS fits a single hospital's workflow, buy it; it will be cheaper and faster. Custom pays for itself when you run several facilities, when your billing has panels and consultant shares the package cannot express, or when the new system has to sit alongside ones you are keeping. A custom hospital system sits in our ERP band, from $35,000 and sixteen to forty weeks; the Punjab group's ran 34 weeks with seven engineers, a designer, QA and a project manager.

Questions to ask any vendor

• Show us duplicate detection and merging on records like ours — Urdu and English names, missing CNICs.
• Show us a live HL7 FHIR interface, and tell us which analyser models you have connected before.
• Walk us through billing for a panel patient with a consultant share, end to end.
• Put the migration plan in writing: what runs in parallel, in what order, and how each step is rolled back.
• Who trains the night shift, and when?
• Who at your company can see our patients' data, and how is that access logged?

If you are weighing a replacement, our ERP and hospital systems team will run a fixed-price discovery sprint against your real workflows, and you keep the findings whichever vendor you choose.