What is a hospital management system, and which modules does it include? IPD, wards, OT, pharmacy, lab and TPA desks explained, and when a clinic does not need any of it.

A hospital management system (HMS) is software that runs the whole operation of a hospital: outpatient registration, admissions and beds, wards and nursing, the operating theatre, pharmacy stock, the laboratory, billing with insurance and TPA claims, and discharge. The word that separates it from clinic software is admission. Once a patient is given a bed, every other module exists to track what happens to that patient and what it costs until discharge.

If you are deciding between the two kinds of product, our comparison of hospital management software and clinic software is the shorter read. This post opens the HMS up module by module. For the acronyms (HIS, HMIS, EMR) see HIS, HMS, HMIS and EMR explained.

Which modules does a hospital management system include?

Vendors cut the list differently, but the same functions appear under most names. The table lists them by the desk that uses each one.

What does each of the hospital-only modules actually do?

IPD, wards and beds

The IPD module turns a visit into a stay. It records the admission, assigns a bed, charges the bed per day, moves the patient between wards or to the ICU, and keeps a running bill against a deposit. Nursing screens hang off it: the doctor's orders, the drug chart, the vitals chart. None of this has a use in a clinic where the patient goes home after the consultation. The conduct regulations the NMC applies also treat indoor patients separately: clause 1.3.1 asks every physician to maintain the medical records of "indoor patients" for three years from the start of treatment in the prescribed proforma. Our post on how long to keep medical records covers the retention rules for OPD and IPD.

Operating theatre

The OT module schedules theatres, books surgeons and anaesthetists, lists consumables used in each case so the bill picks them up, and stores the operation notes. A clinic that does minor procedures in a treatment room does not need a theatre roster; a procedure note in the consultation record and a line on the bill does the job.

Pharmacy stock

Hospital pharmacy software tracks purchases, batches and expiry, ward indents and counter sales, and prints the records a licensed pharmacy keeps. A clinic that dispenses a small stock of medicines to its own patients is in a different position, and the rules for that are covered in our post on Schedule K and dispensing at a clinic. A full stock module is overkill for a shelf of twenty items; a simple purchase and sale register may be enough.

Laboratory

A lab module takes orders from the ward or the OPD, tracks the sample, receives results from the analyser or by hand, and prints the report. Clinics without an in-house lab send patients out and receive a PDF or a paper report. For them the relevant question is whether the consultation record can note which test was advised and when the result came back, not whether the software can talk to an analyser.

Insurance and TPA

Cashless treatment is an inpatient process: pre-authorisation before admission, running updates, a final claim with the discharge summary and itemised bill. The TPA desk module manages that paperwork and the outstanding claims. OPD consultations are mostly paid at the counter, and where a patient wants reimbursement for an OPD visit they need a proper bill, covered in our post on OPD bills for insurance reimbursement, not a claims module.

When does a clinic not need a hospital management system?

The Clinical Establishments (Registration and Regulation) Act, 2010 defines a clinical establishment as "a hospital, maternity home, nursing home, dispensary, clinic, sanatorium or an institution by whatever name called" that offers diagnosis, treatment or care. The law puts them in one basket for registration; the software they need splits on one fact. If no patient stays overnight, you run an OPD, and an OPD needs registration, a queue, the consultation and prescription, billing and the day's reports.

• No beds: skip IPD, wards, nursing, OT and discharge modules. They will sit unused and still appear on the invoice.
• No in-house pharmacy counter: skip the stock module unless you hold a dispensing stock large enough to need batch and expiry tracking.
• No in-house lab: skip the lab module. Note advised tests and attach or file the outside report.
• No cashless admissions: skip the TPA desk. Print clear OPD bills instead.
• Day-care procedures with a few hours' observation: this is the grey zone. Ask whether the clinic software can record a procedure, a short observation and a package bill without a bed module. If you plan to add beds within a year, look at a small HMS now.

A useful question for any vendor is which modules in the demo your clinic would open in a normal week. If the honest answer is five out of twelve, you are paying for a hospital you do not run, and your front desk will be learning screens it never uses. The glossary entry on OPD versus IPD has the short definitions.

When does a clinic need one?

You need an HMS, or at least its IPD and billing modules, the day you admit a patient and charge for a bed. Nursing homes, maternity homes and small hospitals with 10 to 30 beds run on exactly these modules. The signs that you have outgrown clinic software: a deposit is collected at admission, a bill runs over several days, nurses need to record what was given at what hour, an insurer asks for a pre-authorisation, or a discharge summary has to be produced from the record. At that point buy the hospital product and expect the setup to take weeks, not an afternoon.