Skip to content
HMS Basics

Hospital Management System Modules List: What You Need

By DevOrbital Team · · Updated · 6 min read

HMS Basics

Hospital Management System Modules List: What You Need

● DevOrbital HMS

The short answer

A complete hospital management system typically has modules for patient care (OPD, IPD, emergency, OT), diagnostics, pharmacy and stores, finance and insurance, HR and payroll, medical records, reports and system administration. Not every hospital needs all of them on day one. Start with registration, OPD and billing, then add modules by where your delays or leakage are.

Key takeaways

  • Core modules for almost every hospital: registration, OPD, billing, and a way to manage users and permissions.
  • Inpatient hospitals add IPD, nursing documentation, pharmacy, diagnostics, insurance/TPA and discharge.
  • Support modules such as HRMS, stores, MRD and reports are easy to postpone but costly to ignore for long.
  • Add-ons like ABDM, telemedicine, patient app, WhatsApp alerts and token management extend the core and can be added later.
  • Judge a module by whether it shares data with the others, not by whether it exists on the feature list.

What modules does a hospital management system include?

Most hospital management systems are organised into the same eight families. The names change from vendor to vendor, but the underlying work does not. Below is a plain list of what each family contains, what to check for, and who uses it. For the bigger picture, read our complete guide to hospital management systems first.

1. Registration and OPD

What it does. Registers the patient, issues a UHID, checks for duplicates, records payer details, and manages department and doctor-wise queues. The OPD screens handle live consultation case sheets, prescriptions and follow-up.

What to check.

  • Quick re-registration of returning patients by phone, name or UHID.
  • Appointment and walk-in handling in the same queue.
  • Prescription templates that suit your specialties.
  • Printable OPD slips in your format.

Explore the OPD management system for the typical flow.

2. IPD and bed management

What it does. Handles admission, bed and ward allocation, doctor and nursing notes, medication administration, transfers, deposits and discharge. Labour room and birth and death documentation often sit here too.

What to check.

  • A visual view of ward and bed occupancy.
  • Charges that post automatically against the admission.
  • Discharge that draws on notes, results and billing in one place.

We cover it in depth in the IPD management system guide and the hospital bed management system article.

3. Emergency and casualty

What it does. Rapid registration, colour-coded triage, MLC documentation, and deferred billing for accident cases so care is not held up by payment. Orders flow to lab and radiology ahead of routine queues.

What to check.

  • Registration with minimal fields and later completion.
  • A triage board visible to the whole team.
  • MLC data captured in a structured way.

See emergency triage and MLC software.

4. Operation theatre

What it does. Schedules surgeries, manages consents and statutory forms, runs a safety checklist, and records the procedure and team.

What to check. Consent forms in the right languages, a WHO-style checklist, and OT schedule visibility across surgeons and anaesthetists.

5. Diagnostics: pathology, radiology and more

What it does. One order-to-report workflow for pathology, radiology, cardiology, endoscopy and other services: order, collect, process, validate, report, bill.

What to check.

  • Walk-ins and emergency orders in the same queue.
  • Manual entry and typed reports with templates, so a machine is not mandatory.
  • Optional analyzer and imaging integration, scoped per device.

See the laboratory information system guide and the lab analyzers integration page.

6. Pharmacy and central stores

What it does. Pharmacy handles counter sales and IPD order fulfilment, with one or more pharmacy units. Central stores run requisition, approval, purchase and issue with document uploads, and track ward-level stock.

What to check.

  • Batch and expiry tracking.
  • Separate billing and stock for each pharmacy unit.
  • Indents from wards that reduce on-the-spot requests.

See the pharmacy management system and our article on pharmacy inventory and expiry management.

7. Finance: billing, insurance and TPA

What it does. Unified billing with discounts that need approval, a bill archive, deferred payment for emergency and MLC cases, and insurance modules with contracts, rate cards and claims for TPAs, corporates and government schemes.

What to check.

  • Discount approval rules by role.
  • Package billing and deposits.
  • Claim status tracking from pre-authorisation to settlement.

See hospital billing software and TPA insurance claim management.

8. HRMS and payroll

What it does. Staff directory, attendance, duty roster, payroll with TDS, PF and ESIC, doctor fee settlements, and separate views for doctors, nurses and executives.

What to check. Roster rules that match your shifts, and settlement logic for visiting consultants. Our post on hospital payroll with TDS, PF and ESIC covers the details.

9. Medical records (MRD)

What it does. Maintains a single chronological read-only record across departments, tracks completeness before archival, merges duplicate UHIDs, keeps a retention register and handles record requests.

10. Reports and analytics

What it does. Revenue, expense and purchase reporting with filters for department, doctor and date, payment-mode splits and trends.

What to check. Whether reports come from the same transactional data or from exports you have to stitch together.

11. System administration

What it does. Configures beds, wards, labs, pharmacies and departments, manages users and module-level permissions, and logs every create, edit and delete in an audit trail.

This is the module nobody demos and everybody needs. It decides whether a new department can be set up in a day or a month.

Which add-on modules are worth considering?

Add-ons extend the core and can usually come later:

Add-onUseful when
ABDM moduleYou want to create or link ABHA-based records. See the ABDM guide
Telemedicine and patient portal/appYou offer remote consultations or want patients to view reports and book
WhatsApp / SMS alertsReducing no-shows and sending report-ready messages
QR-code registration and token managementFront-desk crowding
IVR bookingPhone-heavy appointment desks
Health checkup packagesCorporate and preventive health programmes
Accounting integrationYour accountants use a separate accounting package
Ambulance, dietary, housekeeping and linen, mortuary, canteenLarger campuses with those functions

How should you prioritise modules?

If you cannot take everything at once, rank by pain, not by prestige.

  1. Where is money lost? Missing charges, unrecovered claims and discount abuse point to billing, insurance and pharmacy.
  2. Where do patients wait? Long queues point to registration, OPD, lab and discharge.
  3. Where are you exposed? Missing consent forms, incomplete files and untraceable edits point to OT, MRD and the audit trail.
  4. Where is manual work heavy? Month-end payroll, stock counting and reporting point to HRMS, stores and analytics.

A useful numbered starting plan for a new 30-bed nursing home might be:

  1. Registration, OPD and billing.
  2. IPD with bed management and nursing notes.
  3. Pharmacy and basic diagnostics.
  4. Insurance and TPA.
  5. HRMS, MRD and reports.

You can try the module selector to build your own order, and read how nursing homes usually stage it.

Can modules run independently?

Some products are monolithic, others are modular. In DevOrbital HMS, every module can run on its own, and the same patient record connects them when bundled. This matters for hospitals that already have, say, a working lab system and want to replace only billing first. Whatever product you choose, ask the vendor to show a stand-alone module connecting to another in a live demo.

Common mistakes when evaluating modules

  • Counting screens. A module with 12 screens is not better than one with 5 that fit your workflow.
  • Ignoring the hand-offs. Value lives at the boundaries: order to result, result to bill, bill to claim.
  • Assuming add-ons are included. Always get a written list of what is in the base and what is separate.
  • Skipping the admin module. Without roles and audit, growth gets messy.

Next steps

To see how these modules fit together, open the hospital management system overview. For the department where most outpatient hospitals begin, see the OPD management system, and for stock and counter sales, the pharmacy management system.

Frequently asked questions

There is no standard number. Vendors count modules and screens differently, so a count of 40 from one vendor and 25 from another may cover the same ground. Compare by workflow coverage instead.

Registration, OPD, billing and user management are the starting set. If you have beds, add IPD, nursing notes and discharge. A pharmacy and a lab are the next common additions.

Some platforms let each module run on its own and connect when bundled. Ask whether a stand-alone module can later share a patient record with the rest without data migration.

Add-ons extend the core with specialised functions, for example ABDM, telemedicine, a patient portal and app, WhatsApp or SMS alerts, QR registration, IVR booking, token management, health checkup packages and ambulance management.

Keep exploring

Related reading and systems

Read this next

All articles →

See the platform for yourself

Tell us about your facility and we will walk you through the modules that fit — one department or the whole hospital.