In 2026, hospital management software in India costs roughly 12,000 to 1 lakh a year for a clinic, 2 to 5 lakh a year for 20 to 50 beds, 4 to 12 lakh a year for 50 to 150 beds, and 15 to 40 lakh a year above 200 beds if you buy it. Building your own runs 6 to 15 lakh for a small facility, 12 to 25 lakh for a 50 to 100 bed hospital, and 35 to 70 lakh and up above 150 beds.
There is a third number that appears in neither column and decides more build-against-buy arguments than either of them: what it costs to get your own software through ABDM certification. That section is below, and it is the reason most hospitals should buy.
What you pay to buy
| Facility | Typical annual cost | What it usually covers |
|---|---|---|
| Single clinic or polyclinic | 12,000 to 1 lakh | Registration, appointments, prescriptions, basic billing |
| 20 to 50 beds | 2 to 5 lakh | The above plus IPD, pharmacy, basic lab, discharge billing |
| 50 to 150 beds | 4 to 12 lakh | Full OPD and IPD, pharmacy, lab and radiology, insurance and TPA, reporting |
| 200 to 500 beds | 15 to 40 lakh | Everything, plus multi-site, blood bank, OT scheduling, NABH documentation |
Vendors quote this three ways: per bed per month (roughly 500 to 5,000 rupees depending on how many modules are switched on), per user per month (1,200 to 5,000 per doctor on the common per-seat plans), or as a flat annual licence. Enterprise products such as Insta are quoted differently again, around 20,000 to 80,000 a month with a 3 to 10 lakh implementation fee on top.
Two things to check before comparing any two quotes. Which modules the price includes, because pharmacy, lab and insurance are the three most often sold separately and are the three you will certainly need. And whether the per-bed count is sanctioned beds or occupied beds, which on a 100-bed hospital running at 60 percent occupancy is a 40 percent difference in the bill.
What you pay to build
| Facility | Cost | Timeline |
|---|---|---|
| Clinic or 10 to 30 beds | 6 to 15 lakh | 3 to 6 months |
| 50 to 100 beds, core modules | 12 to 25 lakh | 6 to 9 months |
| 150 beds and above, enterprise | 35 to 70 lakh and up | 12 to 18 months |
Maintenance afterwards runs 1.5 to 4 lakh a year for a mid-sized build, the usual 15 to 25 percent rule our app maintenance guide explains. Hosting, backups and disaster recovery for clinical data add 20,000 to 1.5 lakh a month depending on size and on whether you are running it on-premises.
The cost nobody puts in the build quote
Hospital software in India is not just software any more. If it is going to create or verify an ABHA number, or link a discharge summary to a patient's health account, it has to be certified under the Ayushman Bharat Digital Mission, and the certification is per software product, not per hospital.
That sentence is the whole argument. When you buy a certified HMS, the vendor has already paid for that path and spreads it across every customer. When you build your own, you have bought the path outright.
The milestones, as the National Health Authority defines them:
| Milestone | What the software must do |
|---|---|
| M1 | Create a new ABHA for a patient and verify an existing one at registration |
| M2 | Link records, discharge summaries, prescriptions, diagnostic reports and OP consultations, to the patient's ABHA |
| M3 | Fetch and use records held by other providers |
| M4 | Participate in NHCX, the digital claims exchange |
Getting there means sandbox integration and testing, a security audit by a CERT-In empanelled auditor, and a Safe-to-Host certificate submitted before production credentials are issued. Separately, the hospital registers in the Health Facility Registry and every clinician in the Healthcare Professional Registry.
Budget, for a build:
- CERT-In empanelled audit: 1 to 5 lakh, depending on how many applications and servers are in scope, and repeated when the application changes materially.
- Integration and sandbox exit: 10 to 25 person-days for M1 and M2, which is where most hospitals stop.
- Elapsed time: two to three months on top of the build, running partly in parallel if you start it early and entirely in series if you do not.
So a 20 lakh build is really a 23 to 28 lakh build, arriving two to three months later than the plan says, with an audit cycle that comes back around. None of that appears in the quotes we are asked to review, and it is not dishonesty so much as unfamiliarity: plenty of capable development companies have never taken a product through this.
Where the money goes: a worked estimate
A 60-bed multi-speciality hospital, core modules, insurance and TPA included.
| Work package | Person-days |
|---|---|
| Registration and the patient master, including ABHA create and verify | 10 |
| OPD: appointments, queue, consultation notes, prescriptions | 14 |
| IPD: admission, bed and ward management, transfers, discharge summary | 16 |
| Billing: tariff plans, packages, concessions, part payments, the final bill | 18 |
| Pharmacy: stock, batch and expiry, issue against prescription, returns | 14 |
| Lab and radiology: orders, sample tracking, results, report delivery | 14 |
| Insurance and TPA: pre-authorisation, claim files, the paperwork trail | 12 |
| Roles, permissions and an audit trail on every clinical record | 8 |
| Reports: daily census, collections, and the statutory returns | 6 |
| ABDM: M1 and M2 integration, sandbox exit, the audit cycle | 12 |
| Migration, a weekend go-live, and training every shift | 8 |
| Total | 132 |
At the blended 16,000 rupees a person-day we use across these guides, that is about 21 lakh, at the upper end of the 12 to 25 lakh band, over seven to nine months including certification.
Look at which line is biggest. Billing is 18 days, larger than OPD and larger than IPD. Hospital billing in India is genuinely the hardest module in the system: tariff plans that differ by scheme, package rates that behave differently from itemised ones, concessions approved by three different people, part payments across a stay, and a final bill that has to reconcile against an insurance claim. Every hospital we have spoken to about a failed HMS was failed by its billing, never by its appointment screen.
The crossover
For a single 60-bed hospital: the build above costs about 21 lakh, plus 4 lakh a year of maintenance and roughly a lakh a year amortised for the audit cycle. Over five years that is about 47 lakh, which is the same as buying at 9.4 lakh a year.
Since the market rate for that hospital is 4 to 12 lakh a year, buying wins unless you are at the very top of the band. For most single hospitals, it wins comfortably.
Now the group. Four 60-bed hospitals under one management, one system across all of them:
| Route | Five-year cost |
|---|---|
| Buy, four facilities at 6 lakh a year each | 1.2 crore |
| Build once for the group | about 76 lakh |
The economics invert, and they invert for the same reason they do in society management and fleet software: the build is paid once and the licence is paid per unit, forever. Never build for one hospital. Consider it seriously at three or more, or at one large enough that the per-bed bill has become a line the board asks about.
What breaks, and it is rarely the software
- The billing counter at discharge. If a patient waits two hours for a bill, the system has failed regardless of what it does elsewhere. Test this before go-live with real tariffs and a real insurance case, not with sample data.
- The night shift. Software designed around the day team's workflow falls apart at 2am when one person is doing three roles. Watch a night shift before you design anything.
- Pharmacy stock. Batch and expiry tracking is where custom builds most often turn out to be shallower than the product they replaced, and the discrepancy surfaces at the first audit.
- Doctors not using it. Consultation notes typed by a doctor in three minutes get used; anything that takes seven minutes gets written on paper and typed in later by someone else, which destroys the data you built the system for.
- The migration. Patient history, outstanding bills, pharmacy stock and pending lab orders all have to land correctly in a single weekend. This is a project in itself and deserves its own line in the quote.
How to read an HMS quote
- Ask whether it is ABDM certified, and to which milestone. M1 only is common and is not the same as being ready for health records.
- Ask which modules are in the price and which are separate. Pharmacy, lab and insurance, every time.
- Ask whether per-bed means sanctioned or occupied.
- Ask what the data export looks like when the contract ends. Patient history is yours, legally and morally, and getting it out in a usable form is not always simple.
- Ask who does the migration and what it costs, separately from the licence.
- Ask for a reference hospital of your size and call them about the billing counter.
- For a build, ask who on the team has taken a product through the sandbox exit and a CERT-In audit. If nobody has, your timeline is a guess.
The general version of this checklist is in how to hire a development company in India.
How to spend less
- Buy the HMS, build the gap. The pattern that works most often is a certified product for the regulated core, plus a small custom tool for the thing your hospital genuinely does differently.
- Start with OPD, pharmacy and billing. Lab, radiology and insurance can follow a quarter later and the hospital still runs.
- Negotiate on the occupied-bed figure, or on a flat annual licence, rather than accepting a sanctioned-bed count.
- Do not build a patient app in version one. Appointment booking and report delivery over WhatsApp costs a fraction and is used more; the channel costs are in our WhatsApp AI agent cost guide.
- Put the front desk's phone load somewhere else. For many hospitals the cheapest improvement is not the HMS at all, and the figures are in our AI receptionist for clinics guide.
Questions people ask
How much does hospital management software cost in India?
Buying costs 12,000 to 1 lakh a year for a clinic, 2 to 5 lakh for 20 to 50 beds, 4 to 12 lakh for 50 to 150 beds and 15 to 40 lakh above 200 beds. Building costs 6 to 15 lakh for a small facility, 12 to 25 lakh for a 50 to 100 bed hospital and 35 to 70 lakh and up above 150 beds, plus 15 to 25 percent of the build a year to run it.
What does hospital software cost per bed?
Roughly 500 to 5,000 rupees per bed per month depending on how many modules are enabled, with per-doctor plans at 1,200 to 5,000 a month as the common alternative. Confirm whether the vendor counts sanctioned or occupied beds, which on a hospital running at 60 percent occupancy changes the bill by about 40 percent.
Should a hospital buy or build its management software?
Buy, for a single hospital, in almost every case. A 60-bed build costs about 47 lakh over five years including maintenance and the audit cycle, which is the same as buying at 9.4 lakh a year against a market rate of 4 to 12 lakh. Building becomes sensible at three or more facilities under one management, or at a single hospital large enough that the per-bed licence has become a board-level line.
What does ABDM certification cost?
For a hospital buying certified software, nothing directly; the vendor has already paid for it. For a hospital building its own, budget 1 to 5 lakh for the CERT-In empanelled security audit, 10 to 25 person-days of integration work for milestones M1 and M2, and two to three months of elapsed time for sandbox exit and production approval. The audit recurs when the application changes materially.
What are the ABDM milestones M1 to M4?
M1 is creating and verifying an ABHA at registration. M2 is linking records such as discharge summaries, prescriptions and diagnostic reports to that ABHA. M3 is fetching and using records held by other providers. M4 is participating in NHCX, the digital claims exchange. Certification is per software product, not per hospital, so each facility then registers separately in the Health Facility Registry.
How long does it take to implement a hospital management system?
Three to six months to build for a small facility, six to nine months for a 50 to 100 bed hospital and 12 to 18 months above 150 beds, with two to three months of ABDM certification that can partly run in parallel. Implementing a bought product takes four to twelve weeks, most of which is migration and training rather than software.
Which module causes the most problems?
Billing. Tariff plans that differ by scheme, package rates, concessions with approval chains, part payments across a stay and a final bill that must reconcile against an insurance claim make it the largest line in the estimate and the place failed implementations usually fail. Test it with real tariffs and a real insurance case before go-live.
Is cloud or on-premises better for a hospital?
Cloud, for almost every facility under 200 beds, because backups, disaster recovery and the security posture come with it rather than becoming your job. On-premises is worth the extra cost where internet reliability is genuinely poor or where a specific contractual requirement demands it, and in that case budget for the hardware refresh as well as the software.
Getting a real number
Ranges end where your hospital's actual workflow begins, and in healthcare the workflow is the whole project. We will look at your bed count, your module list and your ABDM position, and tell you honestly whether a certified product covers it. More often than not it does.