Updated on 22 June 2026

How to choose hospital management software in India

A structured evaluation framework for Indian hospital administrators, medical directors and owners at 50–500 bed hospitals. Covers NABH 6th edition evidence generation, ABDM integration readiness, GST billing accuracy, offline capability, pricing models, deployment options and reference verification — with Indian Act and Rule citations where they apply.

By L.K. Monu Borkala, Founder & CEO, OneCity Technologies Pvt Ltd  ·  18 min read

Choosing hospital management software is not an IT procurement exercise. It is an operational decision that shapes every clinical, financial and administrative workflow in the hospital for years after go-live. The registration desk uses it. The doctor consults through it. The pharmacist dispenses from it. The lab reports through it. The biller invoices from it. The administrator audits from it. The NABH assessor judges the hospital through it.

Get the choice right and you eliminate billing leakage, cut discharge turnaround, pass accreditation assessments with screen-captured evidence, and give your clinical team one system instead of five logins. Get it wrong and you spend the next three years building workarounds — re-keying data, exporting to Excel, printing for the file, and explaining to assessors why the software cannot produce the report they need.

This guide is written for the hospital administrator at a 50–500 bed facility in a tier-2 or tier-3 Indian city — the segment where the choice matters most and the information gap is widest. Metro chain hospitals have procurement committees and IT departments. The hospital you run has an owner, an administrator, one accountant, and a deadline from the insurance company or the NABH pre-assessment team.

Why hospitals replace their software — the five triggers

Every vendor will present a feature list with 200 line items. That list is irrelevant until you know what problem you are solving. In our conversations with hospital administrators across Karnataka, Kerala, Uttar Pradesh and Madhya Pradesh, the same five triggers come up consistently.

Trigger 1: Compliance pressure

NABH 6th edition, published by the Quality Council of India, defines 651 objective elements across 10 chapters — AAC (Access, Assessment and Continuity of Care), COP (Care of Patients), MOM (Management of Medication), and seven others. A significant number of these elements require evidence that can only be generated reliably by software: medication error rates per 1,000 patient-days, hospital-acquired infection rates, average time from registration to consultation, clinical audit trails showing who recorded what and when, and quality indicator dashboards updated monthly. A full breakdown of what the ERP must cover for NABH is in our NABH 6th edition guide.

ABDM (Ayushman Bharat Digital Mission) is the second compliance driver. As of 2026, ABDM integration — specifically, ABHA ID verification and Health Information Provider (HIP) registration under the Health Facility Registry — is becoming a condition for PMJAY empanelment. The National Health Authority has signalled that CGHS and ECHS empanelment will follow. Our ABDM integration guide covers the implementation priorities in detail. If your current software cannot demonstrate ABDM sandbox integration today, it will not have production-grade integration by the time the mandate arrives.

The Digital Personal Data Protection Act 2023 (DPDP Act) adds a third layer. Every hospital processing digital patient data is a Data Fiduciary under the Act. This means explicit consent at registration, a right of access, a right of erasure (with medical-record retention exceptions), and a data breach notification obligation. Your software must support all four. See our DPDP Act 2023 compliance guide for the specific requirements.

Trigger 2: Billing leakage

In a typical 100-bed hospital with annual revenue of ₹5–8 crore, manual charge entry — where someone re-keys the doctor's order into the billing system — loses 3–8% of revenue. That is ₹15–40 lakh per year walking out the door as missed charges, under-coded procedures, and pharmacy issues that never made it to the bill. The fix is order-to-bill automation: every doctor order, lab test, pharmacy dispensing event and procedure captures a charge at the point of care and flows it to the bill without re-keying. If your clinical and billing systems are disconnected, you are leaking revenue — and you may not know how much because you have no way to measure what was never captured.

Trigger 3: Data fragmentation

Five vendors for five departments means five patient identifiers, five databases, five backup schedules, five sets of login credentials for staff, and zero unified view of a patient's journey through the hospital. When the NABH assessor asks for a six-month medication error rate, someone must collate data from the pharmacy system, the clinical notes system and the incident reporting spreadsheet. When the GST auditor asks for reconciliation between pharmacy sales and GSTR-1, someone must match line items across two databases. When the medical superintendent wants average length of stay by department, someone must cross-reference admission records from one system with discharge records from another. A unified system built on a single database eliminates all of this.

Trigger 4: Growth

You are adding 50 beds, opening a satellite clinic, launching a dialysis unit, or starting IVF services. Your current software does not support multi-location operations, or does not have a module for the new department, or charges ₹3 lakh per new module activation. This is the cleanest trigger for a switch — and the one where you have the most negotiating leverage because the vendor knows you are already evaluating alternatives.

Trigger 5: Cost

Your current vendor charges ₹3–5 lakh per year in annual maintenance, and every request beyond the standard workflow is quoted as a change request at ₹500–₹2,000 per hour. At some point, the cumulative AMC and change-request cost exceeds what a modern SaaS subscription would cost for the same hospital. Run the three-year total cost of ownership comparison before you start looking at demos — it tells you whether switching is a financial decision or just a frustration.

Twelve questions to ask every vendor

These questions separate a good demo from a good product. Send them in writing before the demo. Insist on written answers. A vendor who cannot answer in writing is a vendor who has not built the feature.

Question 1: Is this one database or multiple systems connected through sync?

Many vendors market an "integrated" solution that is actually three or four separate applications sharing data through HL7 feeds, flat-file imports, or API calls on a cron schedule. The patient exists in the registration database, again in the lab database, and again in the billing database — linked by a shared identifier, but stored in three separate places.

Ask to see the database schema. If patient registration, laboratory, pharmacy and billing are in separate databases with synchronisation jobs running every 5 or 15 minutes, that is integration — not unification. Synchronisation jobs fail silently. They create race conditions when two departments update the same patient record within the sync interval. They make cross-department reporting a data-engineering exercise instead of a single query. A unified system — one database, one patient record, one bill, one audit trail — does not have these failure modes.

Question 2: Generate the NABH evidence for me, live, from the demo data

Do not ask "are you NABH compliant?" — every vendor in India says yes. Ask instead: "Generate the AAC.3 registration-to-consultation time report for the last six months from your demo environment." Or: "Show me the MOM.7 medication error trend by type for the current quarter." Or: "Pull up the COP.7 clinical audit trail for a specific patient — who recorded what, when, with what role."

If the vendor's demo only shows the data entry screens and not the output reports and dashboards that an NABH assessor inspects, the product supports data entry for NABH but not data extraction for NABH. Data entry without extraction is paperwork without evidence. See the NABH standards page for the official 6th edition documentation.

Question 3: Show me ABDM ABHA verification, live

The vendor should demonstrate three things: ABHA number or address lookup against the ABDM gateway, demographic verification (name, gender, year of birth matching), and a Health Information Provider (HIP) data push — creating a health record that would be available to the patient through the ABDM consent flow. If the demo shows a mock screen with placeholder data and an "ABDM Connected" badge but no actual gateway call, ask for the ABDM sandbox URL and test credentials. Any vendor who has completed ABDM sandbox integration can show you a live verification. Any vendor who has not will show you a screenshot.

Question 4: How does billing handle GST correctly?

Hospital billing under GST is among the most complex in any sector. Room charges below ₹5,000 per day (excluding ICU) are exempt from GST. Room charges at ₹5,000 and above attract 5% GST without input tax credit (Notification 11/2017-CT(R), entry 33). Pharmacy items attract 5% or 12% depending on formulation and HSN classification. Diagnostic services attract 18%. Canteen services above ₹7,500 per month may attract GST. Cosmetic surgery, hair transplant and similar elective procedures are taxable at 18%.

The billing engine must auto-apply the correct rate per line item. It must auto-switch between Tax Invoice (when GST is charged) and Bill of Supply (when all items are exempt) per CGST Rule 49. If the hospital has a GSTIN, it must appear on Tax Invoices and not on Bills of Supply. Ask the vendor to generate a single bill with room rent (exempt), pharmacy (5%), diagnostics (18%), and a consultation fee — and verify that each line item carries the correct HSN code and rate. See the CBIC GST portal for official rate notifications.

Question 5: What happens when the internet drops?

If your hospital is in Hubli, Raipur, Varanasi, Siliguri, or any other tier-2/3 city, your internet link is 2–10 Mbps on a good day and it drops. A cloud-only system with no offline capability will halt OPD registration, ward vitals entry, medication administration recording, and pharmacy dispensing — the four workflows that cannot wait for a reconnection.

Ask the vendor: "Which specific modules work without internet connectivity? For how long? What is the maximum offline duration supported? How does the system synchronise when connectivity returns? How are conflicts resolved — for example, if a doctor changes a prescription offline while the pharmacist is dispensing the original version online?" The answer should be a detailed, specific list — not a one-sentence "yes, we have offline mode."

Question 6: What is the data migration plan?

Your existing data — patient master, visit history, billing records, lab results, pharmacy stock — needs to come with you. The quality of data migration determines whether the first month on the new system is productive or catastrophic.

Ask: "What data categories do you migrate? What source formats do you accept? Who builds the mapping? What is the timeline? What is the cost? Is there a parallel-run period where both old and new systems operate simultaneously? How do you validate migration completeness — row counts, checksums, spot-checks?" A good vendor has a documented migration protocol with at least 8 steps. A vendor who says "we will handle it" without showing a protocol is not a vendor who has done this before.

Question 7: What is the total cost for three years?

Get the complete number in writing: licence or subscription fee, implementation and configuration, data migration, on-site training (number of hours, number of trainers), customisation for your specific workflows, hosting charges (if SaaS), SMS and WhatsApp notification credits, per-transaction charges (e-invoice generation, ABDM API calls), hardware requirements (if on-premise), and annual maintenance charges after year one.

Many vendors quote a low headline licence fee and recover through AMC (18–22% of licence cost, annually), per-user charges, per-module activation fees, and change requests. The three-year TCO is the only honest comparison. It is also the number your hospital's board or owner needs to approve — so get it before the demo, not after.

Question 8: Who owns the data?

Under the DPDP Act 2023, the hospital is the Data Fiduciary for all patient data. You are legally responsible for it. This means you must be able to export all patient data in a standard, machine-readable format — CSV, FHIR R4 Bundle, HL7 v2 — at any time, without paying an exit fee and without depending on the vendor's cooperation. If the vendor's contract does not include a data portability clause, or if it charges a per-record export fee, add the clause before signing. This is not negotiable — it is a legal obligation under Section 11(2) of the DPDP Act.

Question 9: How is the pharmacy controlled?

Ask about Schedule H/H1/X drug dispensing enforcement per the Drugs and Cosmetics Rules 1945. Schedule H1 drugs (antibiotics, anti-tuberculosis drugs, certain hormones) require a separate register with the prescriber's name, patient name, drug name, quantity and date — the software must force this entry at dispensing, not allow bypass. Ask about the NDPS register for narcotics per NDPS Act 1985, Section 42 — the register must be tamper-evident with no post-hoc editing. Ask about batch and expiry tracking, drug interaction alerts, and return-to-vendor workflows. If the pharmacy module is limited to "issue and bill" without schedule enforcement, batch traceability and NABH MOM chapter reporting, it will not survive a Drug Inspector visit or a NABH assessment.

Question 10: What is the deployment timeline?

For a 100-bed hospital, a realistic go-live for core modules — registration, OPD, IPD, billing, pharmacy, lab — is 8–12 weeks including configuration, data migration, training and parallel run. If a vendor promises 2 weeks, they are either skipping training (which means your staff will reject the system) or skipping configuration (which means you will use the default workflows, which are never your workflows). If they say 6 months, they are over-scoping the phase-one deployment. Ask for a week-by-week project plan with specific milestones and your team's obligations at each stage.

Question 11: What is the uptime SLA?

Cloud vendors should guarantee 99.5% monthly uptime with a financial penalty clause. That is a maximum of 3.65 hours of downtime per month. Ask for actual uptime data for the last 12 months — not a promise, a record. On-premise vendors should specify the backup and disaster recovery plan: RPO (Recovery Point Objective — how much data you lose in a disaster) and RTO (Recovery Time Objective — how long until the system is back). For a hospital, an RTO above 4 hours is unacceptable for clinical systems.

Question 12: Can I speak with three reference hospitals of my size?

Not the 500-bed corporate chain hospital featured on the vendor's website — a 50–150 bed hospital in a tier-2 city, live on the system for at least six months. Call the hospital administrator directly, not a contact provided by the vendor. Ask: "What broke in the first three months? How fast was it fixed? What does the system not do that you expected? Would you buy it again knowing what you know now?" A reference check takes 20 minutes and is worth more than a two-hour demo.

Deployment models: cloud, on-premise, or hybrid

Cloud (SaaS) is the right choice for most tier-2/3 hospitals. No server room investment, no IT staff for maintenance, automatic software updates, accessible from any device with a browser. The risk is internet dependency — addressed by offline-capable modules for critical workflows. Cost is predictable: a monthly or annual subscription per bed, per doctor, or per encounter.

On-premise suits hospitals with strict data residency requirements imposed by institutional policy or by the nature of their patients (military hospitals, certain government facilities). The cost is higher upfront — server hardware, UPS, air conditioning, IT staff — but there is no recurring subscription. The risk is maintenance: the hospital owns the backup schedule, the security patches, and the upgrade cycle.

Hybrid runs time-critical clinical modules (OPD, pharmacy dispensing, vitals, medication administration) on a local server for speed and offline resilience, and synchronises to a cloud instance for reporting, backup, remote access and administrative workflows. This is emerging as the practical model for Indian tier-2/3 hospitals — local speed where clinicians need it, cloud safety where administrators need it.

Pricing models decoded

Hospital software pricing in India follows five models. Each has a profile that suits a different hospital type.

OneCity's pricing starts at a free tier for up to 5 doctors with all 120 modules included — no feature gating. Paid plans use a per-bed model starting at ₹999 per month. No setup fee, no lock-in contract.

Red flags in a vendor evaluation

Pause or walk away if you observe any of these during the evaluation.

The demo runs on pre-loaded data and the vendor will not let you register a test patient, admit them, order labs, dispense medication, and generate a bill end-to-end. A demo that only shows screens is a slideshow, not a product. You need to see the complete patient journey — not individual screenshots.

The contract has no data export clause, or it charges a per-record fee for data extraction. Under the DPDP Act 2023, you have a legal obligation to access and port patient data. A contract that restricts this is a contract that makes you non-compliant.

The vendor says "NABH compliant" without specifying which edition. NABH 5th and 6th editions have different chapter structures and different objective elements. A claim of compliance without an edition number is a marketing statement, not a product capability.

There is no written SLA for bug resolution. "We will fix it" is not an SLA. "Critical defects resolved within 4 business hours, major within 24 hours, minor within 5 business days" is an SLA. The distinction matters at 9 PM on a Saturday when your OPD billing has stopped working.

The vendor's reference hospitals are all 300+ bed metro facilities. If your hospital is 80 beds in Belgaum, you need a reference from a comparable setting — not from Fortis or Manipal.

The evaluation process: a six-week sequence

A structured evaluation prevents both analysis paralysis and impulse buying. Here is the week-by-week process that works.

Week 1 — Requirement definition. List every department, every workflow, every compliance obligation. Write your own requirements document — do not rely on the vendor's feature checklist, which is designed to make their product look comprehensive. Include: number of beds, OPD volume per day, number of departments, pharmacy locations, lab test volume, insurance/TPA mix, current pain points, compliance deadlines (NABH assessment date, ABDM empanelment date, insurance empanelment renewal date).

Week 2 — Shortlist. Identify 3–4 vendors. Sources: software directories (G2, Capterra, SoftwareSuggest), peer recommendations from hospital administrators you trust, your NABH consultant's suggestions, and industry events (HIMSS India, AHPI conferences). Send each vendor your requirements document and the 12 questions above.

Week 3 — Demos. Conduct structured demos. Have each vendor walk through the 12 questions with your department heads present — lab manager for LIS, chief pharmacist for pharmacy, billing head for invoicing, medical superintendent for clinical workflows. Score each vendor on a 1–5 scale for each question. Use the same scorecard for every vendor so the comparison is apples-to-apples.

Week 4 — Reference checks. Call two hospitals per shortlisted vendor. Use the questions from Question 12 above. Spend 20 minutes per call. Take notes. The gap between what the demo showed and what the reference hospital describes is the gap you will experience.

Week 5 — Negotiation. Get the three-year TCO in writing. Negotiate on: data portability clause, SLA penalty terms, training hours, customisation scope included in the base price, payment terms, and a 90-day exit clause with data export. Do not negotiate only on price — negotiate on scope and protection.

Week 6 — Decision. If two vendors score within 10% of each other on your scorecard, pick the one with the stronger reference check. Demos are rehearsed. References are lived experience.

Why this decision is harder in 2026 than it was in 2023

Three regulatory shifts in the last 24 months have raised the stakes for this purchase.

First, ABDM integration is moving from voluntary to functionally mandatory. The National Health Authority's roadmap links ABDM registration to PMJAY claim processing. Hospitals that cannot verify an ABHA ID at registration will face friction on government scheme claims — and government scheme patients are 30–60% of revenue for most tier-2/3 hospitals.

Second, the DPDP Act 2023 rules are being notified. The Act was passed in August 2023; subordinate rules are being published in phases. Once the relevant rules for health data are notified, every hospital will need software that supports explicit consent capture, data access requests, data erasure (with medical-record-retention carve-outs per Indian Medical Council regulations), and breach notification workflows. Retrofitting these capabilities into an old system is more expensive than choosing a system that has them built in.

Third, NABH 6th edition assessment rigour has increased. Assessors are now asking for software-generated evidence, not folder-based documentation. A hospital that picks software in 2026 without checking NABH 6th edition evidence generation, ABDM gateway readiness, and DPDP consent workflows will be replacing that software within 18–24 months. The cost of switching — data migration, staff retraining, workflow disruption, and the three months of productivity loss during transition — is 3–5x the cost of choosing correctly the first time.