Buying a hospital management system in Pakistan: what to check
HMS projects fail slowly and expensively. The decisions that determine the outcome are made before anything is installed, mostly in how the evaluation is run.
Founder·1 September 2026·8 min read
Hospital software decisions are unusually consequential. The system will touch every department, every patient and every rupee, it will be in place for a decade, and switching later is genuinely painful.
Most of the risk can be removed during evaluation, if the evaluation tests the right things.
Test with your own worst day
Vendors demo a calm hospital. Ask instead to walk through your Friday evening: emergency arrivals, an unregistered patient in critical condition, a panel patient with an approval pending, a ward transfer, and a discharge with a family waiting.
How the system handles the unregistered emergency patient tells you more than an hour of feature slides.
The questions that matter most
- One patient identity across OPD, IPD, pharmacy, lab and radiology, or several with a matching process.
- Charge capture at the point of care, or a reconstruction at discharge.
- How the system behaves when the internet or power fails, which in Pakistan is a design requirement rather than an edge case.
- Whether reports come out of the system or out of an analyst's spreadsheet.
- Role based access and audit, because patient data and controlled substances both require it.
Deployment: be honest about your environment
Cloud reduces maintenance and makes multi site far easier. On premise gives control and keeps working when connectivity does not.
The right answer depends on your building, your connectivity and your policy, and a vendor who insists there is only one correct choice is selling their infrastructure rather than assessing yours.
Get the commercial and data terms right
- Data ownership and export, in writing, in a usable format.
- What support costs after year one, and what response time you are actually buying.
- Who pays for changes required by regulation.
- Training included, by role, and repeated after go live when the real questions appear.
- What happens to your data if the relationship ends.
Sequence the rollout so the hospital keeps running
Registration, OPD and billing first, because they touch the most patients and produce the fastest visible benefit. Then pharmacy and diagnostics, which is where money and stock control meet. Then inpatient, which is the hardest and benefits from a trained organisation. Then HR, payroll and management reporting.
Each phase should be usable on its own. A phase that only makes sense once the next one arrives is a plan that has not been thought through.
What we built
BBB HMS covers OPD, IPD, pharmacy, laboratory, radiology, EMR, billing, inventory, HR and payroll on one patient identity, deployed on premise or private cloud. It is designed around the ordinary realities of Pakistani hospitals rather than an imported model of how a hospital should work.
If your hospital genuinely needs something unusual, that is a conversation about scope rather than a reason to bend the hospital to the software. Our general view on that trade off is in off the shelf versus custom software.
Evaluate with your hardest workflows, insist on one patient identity, plan for power and connectivity failure, and get data ownership in writing. Those four decisions determine most of what the next decade looks like.
Frequently asked questions
How long does a hospital system implementation take?
For a mid sized hospital, plan in phases across several months rather than a single switch. Registration, OPD and billing first, then pharmacy and diagnostics, then inpatient, then the reporting and HR layers. Anyone promising a full hospital live in three weeks is describing an installation, not an implementation.
Should we buy a single system or best of breed?
For most hospitals in Pakistan, one system with a single patient identity beats several specialist ones stitched together, because the integration burden falls on you forever. The exception is a highly specialised department, such as an advanced imaging setup, where a dedicated system is genuinely better and a defined interface is worth building.
What about existing lab and pharmacy software?
Decide early whether they are being replaced or integrated, and get the integration scoped in writing before you sign anything. Half migrated hospitals, where the lab is on one system and everything else on another with manual re-entry between them, are the most common expensive outcome we see.
Who should lead the project inside the hospital?
Someone with authority over process, not only over IT. Most implementation decisions are about who does what and when, not about technology. A project led purely from IT stalls at the first workflow disagreement between departments.