Xenara
← All notes·Healthcare·9 min read

What an HMS actually costs in Pakistan

Real cost bands for a hospital management system in Pakistan, from a 50-bed clinic to a 250-bed NABH deployment, and where the budget usually goes wrong.

By·Founder, Xenara·Published

Almost every HMS quote in Pakistan is given without a scope, which is why the numbers you hear range from PKR 800,000 to PKR 40,000,000 for what sounds like the same thing. They are not the same thing. The spread is real, and it is almost entirely explained by four variables: bed count, whether you need accreditation-grade audit trails, whether the deployment is on-premise, and how many departments go live at once.

These are the bands we actually quote, what sits inside each one, and the three places hospital budgets reliably go wrong. Figures are directional — a real number needs a scoping conversation — but they are the ranges we work in rather than marketing anchors.

The cost bands

PKR 1.5M–3.5M — single-department or OPD-first pilot (roughly 20–60 beds). Patient master, OPD registration and queueing, consultation notes, basic pharmacy dispensing, and cash billing. One department live in 8–10 weeks. This is the right starting point for most clinics and small hospitals, and it is also how we prefer to start larger deployments — prove the workflow on OPD before touching IPD.

PKR 4M–9M — full hospital, mid-size (roughly 60–150 beds). Adds IPD admission and discharge, ward and bed management, laboratory with result entry, radiology orders, inventory, multi-tier billing, and role-based access across departments. Six to eight months, phased so no department cuts over cold.

PKR 10M–22M — 200–300 beds with accreditation requirements. Everything above, plus the parts that only matter at scale: full audit logging on every clinical and financial record, structured discharge summaries, panel and insurer claim workflows, procurement, HR and duty rosters, and management reporting that holds up in a board meeting. This is the band a NABH-track 250-bed hospital lands in.

PKR 25M+ — multi-facility groups or heavy integration. Multiple hospitals under one group with shared patient identity, HL7 or FHIR integration with existing lab and imaging systems, or a migration off an entrenched legacy HMS with a decade of historical records that must survive the move.

The bed count sets the floor. Accreditation, on-premise hosting, and integration set the ceiling — and buyers routinely underestimate all three.

What actually drives the number

  • Multi-tier billing. Pakistani hospitals bill self-pay, panel, insurer, and corporate-discount patients simultaneously, often on the same visit. If the billing engine treats these as exceptions rather than first-class cases, you will pay for it in rework. This is the single most underestimated item in every HMS scope we have reviewed.
  • On-premise hosting and connectivity resilience. Many hospitals require on-prem with no inbound internet, and the system has to keep working through power and broadband gaps. That means local deployment, offline-tolerant clients, and a sync model — not a cloud app pointed at a local server.
  • Accreditation-grade audit trails. NABH, NABL, and JCI inspections want to see who accessed and changed what, when. Retrofitting audit logging after the fact costs multiples of building it in.
  • Bilingual printing. Receipts, prescriptions, and discharge summaries frequently need Urdu typography set properly in Noto Nastaliq Urdu. Cheap to do at build time, expensive and ugly to bolt on.
  • Payment rails. JazzCash, Easypaisa, 1Link and NIFT-routed cards, plus cash, often on hybrid receipts. Billing has to close a sale cleanly across rails.

The three places budgets go wrong

1. Buying every module on day one. The instinct is to scope the whole hospital and go live everywhere at once. It is the most expensive and highest-risk way to do it. An OPD-first pilot costs a fraction, surfaces the workflow problems while they are still cheap to fix, and gives staff a working system to trust before IPD, lab, and pharmacy follow. We describe how that sequencing runs in the 250-bed hospital HMS archetype.

2. Treating data migration as an afterthought. Historical patient records, outstanding balances, and inventory positions have to move. On a hospital with years of records this is a project in its own right, and a quote that does not mention it has not accounted for it.

3. Ignoring the run cost. Licence or hosting, support, and the changes you will want in year two are real. Budget 15–25% of build cost annually. A quote with no ongoing number is not cheaper; it is incomplete.

When not to buy custom

If you run a single clinic under about 20 beds with straightforward cash billing and no accreditation ambition, an off-the-shelf product is very likely the right answer, and we will say so. Custom starts paying back when your billing model, your compliance requirements, or your integration surface stops fitting what the packaged products assume — typically at multi-tier billing, accreditation, or multi-facility scale.

The honest test: list the three things your current system forces you to do manually every day. If they are configuration gaps, buy a product. If they are structural assumptions in how the product models a patient visit, no amount of configuration will fix it.

How we quote

A two-week discovery sprint produces the scope, the phase sequence, and a fixed number before any build commitment — and it is a deliverable you own whether or not you continue with us. See hospital management system development for what the engagement looks like, the AIMS deployment for a 250-bed reference, or how requirements change between Pakistan and Canada if you operate in both markets. City-specific engagement terms are on the Lahore, Karachi, and Islamabad pages.

More from the blog