Write your scenarios first
Ten real situations from your own hospital, sent to every vendor before the demo.
Buying guide
How to choose hospital management software in India: a 25-point checklist
Choose hospital management software by testing it, not by reading its brochure. Write down how your hospital actually works, then make every vendor show each of the 25 points below on screen, with your own patients, drugs and tariffs, signed in as the person who will use it. This guide says what to check and how to test it in a demo. It names no vendors and ranks none; at the end we answer the same checklist for MedBrains, including where the answer is "not yet".
Book a demoBefore the first demo
Most hospital software looks the same in a sales deck. The differences show up at the registration desk at 10 a.m., at the pharmacy counter and at discharge when the TPA has not replied, so run the demo the way the hospital runs.
Bring the people who will use it: front desk, a doctor, a nurse, the pharmacist, billing, medical records and IT. Ask for a trial login you can use after the demo.
Patients and clinical care
One patient, one record, one UHID
The commonest failure is the same person registered twice, Ramesh Kumar today and R. Kumar next month, with two histories that never meet. The system should check for a likely duplicate by name, phone, date of birth and ID before it issues a new UHID, and every department should work on that one record. In the demo: register a patient, then register them again with a misspelt name and the same phone. Does it stop you?
A case sheet a doctor will use
If the consultation screen is slower than paper, doctors will write on paper. Vitals, history, diagnoses, orders and the prescription should sit on one screen, and repeating last visit's prescription should take one action. In the demo: have your busiest OPD doctor run a follow-up visit, start to finish, and time it.
NABH workflows on the screen, not in a binder
NABH assessors look for patient identification, medication safety, consent, incident reporting and complete records. Good software makes these the normal path: consent before a procedure, a discharge summary that cannot be finalised with required fields empty, and quality indicators counted from the records rather than typed in. In the demo: try to finalise a discharge summary with a field missing, and ask to see the NABH indicator report.
Lab and radiology without gaps
Orders should flow from the case sheet to the lab, the worklist should name every patient, a critical value should reach the ordering doctor with the alert recorded, and a result should not be released half-done. In the demo: enter a critical potassium and watch where the alert goes. See lab management software for what this looks like in practice.
Wards, beds and discharge
Admission with a ward and bed picker, transfers, nursing charting and a discharge that moves through billing, pharmacy and nursing clearance as steps you can see. In the demo: admit, transfer and discharge one patient, and ask where the bed shows as free.
Pharmacy and drug law
Schedule H, H1 and X at the counter
Under the Drugs Rules, prescription-only drugs need a prescription, Schedule H1 sales need a register entry with the prescriber, patient and quantity, and Schedule X needs more again. The software should enforce this at the counter, not leave it to memory. In the demo: try to sell a Schedule H1 antibiotic without a prescription. It should refuse.
NDPS register
Narcotic and psychotropic stock under the NDPS Act needs its own register with every receipt, issue and balance. In the demo: dispense a controlled drug and open the register entry it created.
Allergy, interaction and formulary checks
A dispensing system should catch a documented allergy (including a cross-reacting class), a drug interaction with the patient's other medicines, and a drug off your formulary, and it should record who overrode a warning and why. In the demo: record a penicillin allergy, then prescribe amoxicillin.
Batches, expiry and FEFO
Stock by batch and expiry, first-expiry-first-out picking, near-expiry and dead-stock views. In the demo: ask which batch the system picks when two are in stock. More in pharmacy management software.
Billing, insurance and money
Charges captured where they happen
Billing leakage happens when a service is done and never charged: a lab test added late, a consumable used in the ward, a room day missed. Charges should come from the department that did the work, from one charge master. In the demo: order a test from the OPD and check it appears on the bill without anyone typing it.
GST on the right lines
Most healthcare services by a clinical establishment are exempt, but pharmacy sales, some consumables and room rent above ₹5,000 a day outside the ICU are not. Each line needs its HSN or SAC code and the right tax, and the bill needs your GSTIN. In the demo: bill a room above the threshold and a pharmacy item on one invoice.
TPA, insurance and the IRDAI cashless clocks
IRDAI's Master Circular of 29 May 2024 asks insurers to decide cashless requests within one hour and final discharge authorisation within three. Your software should show when each request was sent and answered, so you can see which ones ran late. In the demo: walk a cashless admission through pre-authorisation, enhancement and discharge. Our cashless discharge guide explains the clocks.
Day close, refunds and audit
Cashier day close, refunds and credit notes with a reason, and a deleted bill that stays on record but no longer counts against the patient. In the demo: delete a bill and check the patient's balance. See hospital billing software.
ABDM, privacy and your data
ABDM M1 to M3, and how to verify the claim
The milestones are M1 (create or verify a patient's ABHA), M2 (link your records to the ABHA and share them under consent) and M3 (fetch records from elsewhere under consent). Many vendors say "ABDM-ready". Ask which milestones, whether they have passed NHA's certification for production or only work in the sandbox, and check the vendor against the list of integrated applications on the official ABDM website, abdm.gov.in. A sandbox login is not a certification. In the demo: create or verify an ABHA and link a visit to it. Our ABDM incentive guide explains what the incentive scheme needs.
DPDP Act data handling
The Digital Personal Data Protection Act's main duties apply from May 2027: notice and consent by purpose, security, breach reporting to the Board within 72 hours, retention and patients' rights. Ask how the software records consent, tracks a breach, and handles a patient's request to see or correct their data. In the demo: withdraw a patient's consent for WhatsApp messages and see what stops. Our DPDP readiness guide has a checklist.
Who saw what
Role-based permissions, an audit log of every change, an access log per patient record, and, if the vendor hosts several hospitals, isolation of each hospital's data in the database itself. In the demo: ask to see who opened one patient's record this week.
Data ownership and export
Your contract should say the data is yours, in what format you get it if you leave, and how fast. Ask for a sample export before you sign. In the demo: export one patient's record and open the file.
Moving in from your current system
Ask what can be uploaded and how mistakes are caught: departments, beds, staff, tests, drugs and tariffs at least. A good import shows you every problem before anything is saved. In the demo: upload a sheet with a deliberate error. If you are on registers or spreadsheets today, read hospital software vs paper and Excel.
Running it every day
On-premise or cloud
Cloud means no server room; on-premise keeps patient data in the building on your local network. Ask whether both run the same product, and who patches the server.
Backups and uptime
Ask how often the database is backed up, where the copies go, how long they are kept, when a restore was last tested, and what uptime the vendor commits to in writing. A backup that sits on the same disk as the database does not survive the disk.
When the internet goes down
Ask exactly what still works with no internet: registration, billing, the pharmacy counter, results. "It's cloud, it's always up" is not an answer for a hospital on a single broadband line.
Phones, TV boards and kiosks
Native apps for doctors and nurses on rounds, a patient app, token boards in waiting areas and a self check-in kiosk. Ask whether the TV boards need special hardware. In the demo: call a token and watch the board. See OPD queue management.
Training and support
Who trains your staff, in which language, and what happens at 2 a.m. when billing stops. Ask for written response times and whether there is a user guide inside the product.
Total cost, including hardware
Add up five years: licence or subscription, implementation, migration, servers or cloud, PCs, printers, scanners, TVs, tablets, training and maintenance. Ask what is extra: users, modules, SMS, integrations.
References you call yourself
Ask for two hospitals of your size and type that went live in the last two years, and call them without the vendor on the line. Ask what went wrong in the first month and how long it took to fix.
How MedBrains answers this checklist
We hold ourselves to the same list. This is what MedBrains does today; where the honest answer is "not yet", it says so. Check any line in a demo.
| Point | MedBrains today |
|---|---|
| 1. One record, one UHID | A duplicate check runs before a new UHID is issued; every department works on the same record. |
| 2. Case sheet | One case sheet per visit; last visit's prescription repeated in one action. |
| 3. NABH workflows | Identification, consent, incident reporting and NABH indicators; incomplete discharge summaries can't be finalised. |
| 4. Lab and radiology | Named worklists, critical values flagged to the doctor, no half-released results. |
| 5. Wards and discharge | Bed picker, transfers, nursing charting and a step-by-step discharge. |
| 6. Schedule H, H1, X | Enforced at dispensing; Schedule X also needs a witness and a duplicate prescription. |
| 7. NDPS register | Kept by the pharmacy module from every movement. |
| 8. Allergy and interactions | Allergy, interaction, AWaRe Reserve and formulary checks; overrides recorded with a reason. |
| 9. Batches and FEFO | FEFO picking, near-expiry and dead-stock views. |
| 10. Charge capture | Charges added by the department that did the work, from one charge master. |
| 11. GST | HSN or SAC per line, CGST and SGST, the hospital's GSTIN on every bill. |
| 12. TPA and IRDAI clocks | Pre-authorisations over NHCX timed against the one- and three-hour limits. NHCX is built for and sandbox-tested, not yet certified. |
| 13. Day close and audit | Day close, refunds and credit notes; deleted bills kept for audit but out of every balance. |
| 14. ABDM M1 to M3 | Built for M1 to M3 on the v3 APIs and tested in the ABDM sandbox. Not yet certified by NHA for production. |
| 15. DPDP | Consent by purpose and channel, a breach register with the 72-hour clock, rights requests from the patient portal. |
| 16. Who saw what | Role permissions, audit log, per-patient access log, each hospital isolated by row-level security. |
| 17. Data export | A patient can download their record as FHIR R4. Self-serve export of the whole hospital's data: not yet. On your own servers, the database and its dumps are yours. |
| 18. Migration | Onboarding workbook (departments, wards, beds, staff) with a dry run; CSV import for lab tests and drugs. Self-serve patient list import: not yet. |
| 19. On-premise or cloud | Both, on the same product. |
| 20. Backups and uptime | Daily database dump, optional point-in-time backups, an alert if backups stop. A published uptime commitment: not yet. |
| 21. No internet | On-premise keeps running on the local network; camps record offline and sync. Offline mode for the cloud web app: not yet. |
| 22. Phones, TVs, kiosks | Native staff and patient apps (iOS, Android), token boards on any TV browser, self check-in kiosk. |
| 23. Training and support | An in-app user guide, still being filled module by module. |
| 24. Total cost | Ask us for a written quote for your hospital; hardware is your own. |
| 25. References | Ask us; we would rather you speak to a hospital than read a claim here. |
How to run the evaluation
Bring your own data
Your drug list, tariff and a few anonymised patients, not the vendor's sample hospital.
Test and score as each role
The front desk, a doctor, the pharmacist and the cashier each drive their own screens and mark each point pass, partly or no.
This is general guidance on choosing software, not legal advice. The laws and circulars named here change; check the current version with your own advisers.
Questions
What is the best hospital management software in India?
There is no single best hospital management software in India for every hospital. A 30-bed nursing home and a 300-bed multi-specialty hospital need different things. The right one for you is the one that passes this checklist in a demo run with your own scenarios, your own data and your own staff, and whose references confirm it.
What should I look for in hospital management software?
One patient record with a duplicate check, clinical screens doctors will use, NABH workflows built in, drug-law rules at the pharmacy, GST and TPA billing, ABDM and DPDP handling, clear data ownership, backups, a plan for internet outages, training, and a five-year total cost.
How do I check a vendor's ABDM claim?
Ask which milestones (M1, M2, M3) are live, whether the software has passed NHA's certification for production or only works in the sandbox, and look for it on the official ABDM website. Then create or verify an ABHA in the demo.
Is cloud or on-premise hospital software better?
Cloud avoids running a server and keeps updates simple. On-premise keeps data in the building and keeps working on the local network when the internet drops. Choose a product that offers both so you can change your mind later.
How much does hospital management software cost?
Compare a five-year total, not the first-year price: subscription or licence, implementation, migration, servers or cloud, PCs, printers, scanners and TVs, training and maintenance. Ask what counts as extra.
Does NABH require a particular hospital software?
No. NABH assesses how the hospital works: identification, medication safety, consent, records and quality indicators. Software that builds those into the daily screens makes them easier to show an assessor.