New: the AI scribe is live. Speak the consultation, review a coded draft. See Thravi’s AI
All posts

How to choose hospital management software in India: a buyer’s checklist

A hospital manager and doctor reviewing a software checklist beside a laptop

Most hospital management software looks capable in a demonstration. Patients get registered, a bill prints, a dashboard fills with charts. The differences that matter appear later: when a bill needs correcting, when a batch expires on the shelf, when a staff member leaves, or when you want your own data out.

This checklist is a set of questions to put to any vendor, ours included. It is written for clinic owners, nursing home administrators and hospital managers in India. Ask each vendor to show the answer on screen with a case from your own facility, and treat a slide as a weaker answer than a working screen.

1. Clinical data: is it coded, or only typed?

Ask what is stored when a doctor records a diagnosis. A line of free text is readable by people and by little else. A diagnosis stored against a standard terminology can be searched, counted, reported and exchanged with another system.

Ask which standards are used for diagnoses, symptoms, medicines and lab tests, and how a code gets attached. The doctor should pick a familiar term and the software should attach the code behind it. Then ask what happens to a term that has no match. Our explainer on why coded clinical data decides what your records are worth covers the three standards you will hear named.

2. ABDM readiness: what does “ready” mean here?

“ABDM-ready” is used loosely. Creating or verifying an ABHA, linking a facility's records to it, and fetching records from another provider with the patient's consent are separate pieces of work, and each is built and tested in the ABDM sandbox before it is used with real patients.

Ask which of these the vendor has completed, in which environment, and which external assessment steps remain. Ask to see the consent flow, including a patient declining. A vendor who is partway through should be able to say so plainly. For background, read ABDM explained for Indian clinics.

3. Modules: can you start with what you run today?

A clinic without an in-house lab should not be paying for, or navigating around, a laboratory module. Ask which functions are part of the base product and which are optional. Ask what happens to existing data when a module is switched on later: does the pharmacy see prescriptions already written, and does an inpatient bill pick up services already defined in your price list?

Ask the reverse question as well. If a module is turned off, what happens to the records it created, and can they still be read?

4. Data ownership and export

Your patient records are yours to keep, and the software should make that practical. Ask what you can export without raising a support request, in what format, and what it costs. Ask how patient documents such as scanned reports and generated PDFs are delivered. Ask what happens to your data if you stop paying, and for how long it remains available.

Before you sign, request a sample export for one patient with several visits, a bill, a payment and an attachment. Check that the identifiers connect the pieces. A vendor confident in the product will not find this an awkward request.

5. Roles, permissions and the audit trail

Every person should sign in as themselves. Ask how access is granted: by a handful of fixed roles, or permission by permission for each user? Fixed roles are quicker to set up. Individual permissions suit facilities where one person covers reception and billing in the morning and the pharmacy counter in the evening.

Then test the limits. Can an administrator read a doctor's consultation queue by default? Who can change a bill once it has been finalised, and what record is left behind? When someone leaves, how quickly can access be removed, and does their name remain on what they recorded? If staff work at more than one branch, ask how access differs between locations.

6. Billing and GST

Bring three cases from your own cash desk: a part payment, a refund, and a correction to a bill that has already been printed. Follow each through to the patient's balance and the day's collection report. A system that lets a finalised bill be quietly edited will produce a tidy screen and an unreliable ledger.

On GST, be specific about your own facility. Healthcare services are broadly treated differently from medicines sold at a pharmacy counter, and your accountant will know which of your lines need a tax breakup. Ask the vendor to show an invoice of each kind, and ask whether tax is recorded on each line at the time of sale or calculated afterwards for a report.

7. Pharmacy: batch, expiry and stock you can trust

Pharmacy is where weak software is found out fastest. Ask whether stock is held by batch with an expiry date, and whether the system prevents the sale of an expired batch or only warns. Ask how it chooses which batch to dispense first. Ask whether the selling price can exceed the MRP printed on the pack.

Follow one supplier invoice from entry to the shelf: free quantities, a scheme, GST, and the same batch arriving twice at different rates. Then ask how a stock figure can be explained. A quantity on hand is useful; a movement history showing every receipt, sale, transfer and write-off behind it is what settles an argument during a stock audit.

8. Lab reporting

Ask how reference ranges are defined, and whether they can differ by age and sex. Ask what a report shows when one test of several is still pending. Ask what happens to an already-issued report when someone edits a reference range in the settings. It should not change.

Ask whether results are entered by hand or received from analysers, and whether a result is verified by a second person before release. Neither answer is wrong for a small lab, but you should know which you are buying.

9. Onboarding and training

Ask who sets up the price list, doctors, departments and document templates, and how long it takes for a facility of your size. Ask what can be brought across from your present system and how the result will be checked. Ask to see your own letterhead on a prescription and a bill before going live.

Training should be planned by role. The front desk, the doctors, the pharmacist and the person who closes the cash each need a different hour. Ask whether training is repeated when staff change.

10. Support

Ask how to reach support, during which hours, and in which languages. Ask what happens on a Sunday evening when billing stops. Ask how updates are released and whether you are told before a screen your staff use every day changes. If you can, speak to a facility of your size that has used the product through at least one difficult month.

11. The pricing model

Prices vary too widely to compare on a single number, so compare the model. Is it charged per user, per facility, per module, or by usage? What is charged once and what recurs? Are SMS and WhatsApp messages, AI features, storage, extra branches and data migration included or billed separately?

Work out the cost for your facility as it is today and as you expect it to be in two years, with the extra doctors, the second pharmacy outlet or the new ward included. The cheaper product at today's size is not always the cheaper one after you have grown.

Where Thravi stands on this checklist

It would be odd to publish these questions without answering them. In brief:

Coded data. Symptoms and diagnoses are recorded against SNOMED CT, with ICD-10 on diagnoses. Medicines are linked to a national drug master and lab parameters can carry LOINC codes. The doctor picks a term from a search and the code is attached behind it; a term with no match stays as plain text.

ABDM. Thravi is ABDM integration ready. ABHA-enabled workflows, consent-based record exchange and FHIR-based interoperability are being implemented in line with the applicable sandbox and certification requirements. We do not describe the product as certified.

Modules. Registration, the OP queue, the EMR and billing are the base. Laboratory, Pharmacy and IPD are enabled for each facility as it needs them.

Access and audit. Permissions are granted to each user at each facility. An administrator does not inherit access to a doctor's consultation queue. A finalised bill cannot be edited in place: revising it needs a stated reason and an administrator's approval, and the change is written to a financial audit log.

Pharmacy and lab. Stock is held by batch and expiry, expired batches are excluded from sale, MRP is a hard ceiling, and each sale line records its HSN code and GST split. Lab reference ranges can vary by age and sex, and the range a value was judged against is stored with the result so an issued report does not change later.

Where we are not there yet. Lab results are entered by hand, without analyser interfaces, and there is no separate verification step before a result is released. OP and IPD service bills do not yet carry a tax breakup on their lines; pharmacy sales do. Billing is direct to the patient, without insurance or TPA workflows.

Onboarding and pricing. We are onboarding early adopter clinics and hospitals, and our team walks each facility through setup. Plans are built from the modules a facility runs. Patient messages and AI features draw on a prepaid credit balance.

Bring this list to a demo and hold us to it. Our overview of hospital management software for Indian hospitals and nursing homes describes the platform, and the plans page lets you sketch a setup for your facility before you talk to us.

Book a personalised demo

Tell us how your facility operates, and we’ll show you how Thravi can be configured for your setup.