How to Build a Hospital Management System, OPD, IPD, OT, Pharmacy, Lab, Billing, and ABDM Integration 2026

Running a hospital without a Hospital Management System in 2026 is like running a bank without core banking software. Every patient interaction, registration, consultation, investigation, surgery, billing, discharge, generates data that must flow in real time between departments.

When that flow is broken, when the pharmacy does not know the doctor prescribed a new antibiotic, when billing does not know the patient was moved to ICU, when the lab result is not visible to the attending physician before rounds, patient safety and financial performance both suffer.

India has 70,000 hospitals. Most have some form of digitisation. A significant portion still run on disconnected department software or, worse, on manual processes for critical functions. For a hospital treating 500 outpatients and managing 100 inpatient beds, a disconnected or manually operated HMS is not just inefficient. It is a liability.

This guide covers how to build a hospital management system, from the OPD registration workflow through IPD management, OT scheduling, pharmacy, lab, billing, and ABDM integration, with the architecture that keeps every department connected in real time.

EngineerBabu built healthcare platforms for Apollo Hospitals and Somnoware, which was acquired by ResMed. CMMI Level 5. Google AI Accelerator 2024 Top 20. Contact: mayank@engineerbabu.com

What a Hospital Management System Must Handle, The Complete Care and Revenue Lifecycle

An HMS is not a billing system with some clinical features added. It is the operational backbone that connects clinical care, what happens to the patient, with financial operations, how the hospital gets paid for it.

When these two are disconnected, revenue leaks in both directions: services provided but not billed, and services billed but disputed because the documentation does not support them.

Module 1 – Patient Registration and UHID Management

The patient journey in a hospital begins at registration. Every subsequent interaction, every consultation, every prescription, every test, every bill, links to the patient’s registration record. Get registration wrong and everything downstream is wrong.

The registration workflow:

A patient arriving at the hospital, for OPD, emergency, or planned admission, is registered at the front desk. The registration desk creates or retrieves the patient’s UHID (Unique Hospital ID). If the patient has visited before, their existing record is retrieved by searching on name, phone number, date of birth, or ABHA ID. If new, a new UHID is generated and the full profile is created.

Patient profile fields:

ABHA (ABDM) integration:

The Ayushman Bharat Digital Mission mandates a unique ABHA ID for every patient in India’s public health ecosystem.

For hospitals participating in ABDM, which is increasingly required for government scheme empanelment, the HMS must create or link the patient’s ABHA ID at registration, generate PHR records for every clinical interaction, and share these records with the ABDM health data fiduciary through the consent-based HIE-CM architecture.

The ABDM integration allows patients to access their health records from any ABDM-connected facility, a patient visiting a hospital in Chennai can share their records from a hospital in Delhi with a single consent action.

Module 2 – OPD Management

The outpatient department is the highest-volume, highest-visibility part of most hospitals. A well-managed OPD with short waiting times and smooth consultation flow is the primary driver of patient satisfaction, and the primary entry point for revenue.

• Doctor schedule management:

Each doctor in the OPD has a schedule, which days they see patients, in which OPD room, during which time slots, with how many appointments per slot. The HMS manages this schedule and opens appointment slots for booking, online (patient portal or app), through the call centre, or at the front desk.

• The OPD queue management:

As patients arrive, they are checked in against their appointment or registered as walk-ins. The queue management system displays on screens at waiting areas, showing the current call number and expected wait time. The doctor’s screen shows the queue for their OPD, and they advance the queue by calling the next patient.

• The consultation interface:

When the patient enters the consultation room, the doctor sees their complete history, previous visits, diagnoses, prescriptions, investigations, allergies, and chronic conditions. The doctor records the current consultation:

• E-prescription and drug interaction checking:

Every drug prescribed is checked against the patient’s documented allergies and their current medication list. Interactions above a defined severity level are flagged to the doctor before the prescription is finalised. The e-prescription is printed and/or sent to the patient’s registered mobile, and simultaneously pushed to the pharmacy for dispensing.

Module 3 – IPD Admission and Bed Management

When a patient is admitted, from OPD, from emergency, or as a planned admission, the IPD module takes over. Every inpatient encounter is more complex than an outpatient visit because it spans multiple days, involves multiple departments, accumulates charges continuously, and requires precise documentation for both clinical and billing purposes.

The admission workflow:

Real-time bed board:

The bed board shows every bed in the hospital, ward, ICU, isolation, maternity, with current status: occupied, available, under cleaning, under maintenance. Every bed shows the current patient’s name, admission date, treating doctor, and expected discharge date.

The ward manager uses this view to manage bed allocation, plan discharges, and identify beds that will be available for new admissions.

Module 4 – Pharmacy Management

The hospital pharmacy is one of the highest-risk and highest-revenue departments. Dispensing the wrong drug, the wrong dose, or a drug that interacts with the patient’s current medications is a patient safety event.

Letting pharmacy inventory run to stockout creates operational disruption and patient dissatisfaction.

The pharmacy dispensing workflow:

Pharmacy inventory management:

Module 5 – Laboratory Management

Lab investigations are the highest-volume investigation category in most hospitals. Managing sample collection, processing, result entry, and delivery, for hundreds of tests per day, requires a structured workflow that the HMS’s lab module provides.

The lab order-to-result workflow:

Analyser integration:

For hospitals with automated haematology, biochemistry, or microbiology analysers, the HMS integrates with the analyser through HL7 or proprietary middleware, the result flows directly from the analyser into the patient’s lab record without manual transcription.

This eliminates transcription errors, the most common source of critical lab value mistakes.

Module 6 – Hospital Billing

Hospital billing is complex because charges accumulate across multiple departments over multiple days, apply different rates to different patient types (cash, insurance, government scheme), and must be auditable for insurance claim processing.

The billing engine handles:

Insurance and TPA billing:

For insured patients, the billing module generates pre-authorisation requests to the TPA (Third Party Administrator) at admission, sends interim enhancement requests if the bill exceeds the initial approved amount, and generates the final claim package at discharge, itemised bill, discharge summary, investigation reports, and supporting documents, in the format required by the specific TPA.

Cost to Build a Hospital Management System

EngineerBabu built healthcare platforms for Apollo Hospitals and Somnoware (acquired by ResMed). CMMI Level 5. Google AI Accelerator 2024 Top 20. Contact: mayank@engineerbabu.com

FAQs about Build a Hospital Management System

• What is ABDM and why does it matter for a hospital building an HMS in India in 2026?

ABDM (Ayushman Bharat Digital Mission) is the Government of India’s national digital health infrastructure. It includes the ABHA (Ayushman Bharat Health Account), a unique 14-digit health ID for every citizen, and the Health Information Exchange and Consent Manager (HIE-CM) that allows patients to share their health records across facilities with a single consent action. For hospitals, ABDM integration means: every patient gets an ABHA ID at registration, every clinical interaction generates a linked health record, and the hospital’s HMS must be certified by the National Health Authority as an ABDM-compliant Health Information Provider. In 2026, ABDM integration is increasingly required for government scheme empanelment, hospitals not connected to ABDM cannot process Ayushman Bharat PM-JAY claims. Any HMS built for an Indian hospital in 2026 must have ABDM integration as a core requirement, not an optional add-on.

• What is the difference between an OPD and an IPD module in a hospital management system?

The OPD (Outpatient Department) module manages patients who come for a consultation and leave the same day, registration, appointment scheduling, consultation queue, e-prescription, investigation orders, billing, and follow-up booking. The IPD (Inpatient Department) module manages patients who are admitted and stay in the hospital, bed allocation, nursing documentation, medication administration records (MAR), daily progress notes, multi-doctor consultations, procedure records, and discharge summaries. The key architectural difference is duration and complexity: an OPD encounter lasts 15 to 30 minutes, an IPD encounter lasts days to weeks and generates dozens of clinical and billing events that must be tracked continuously. A hospital HMS must support both modules with real-time integration, a patient admitted from OPD must have their entire OPD encounter history immediately visible in the IPD module.

• How does the hospital billing module handle insurance and TPA patients?

For an insured patient, the billing workflow begins at admission rather than discharge. The billing module sends a pre-authorisation request to the TPA (Third Party Administrator) with the patient’s policy details, diagnosis, and estimated treatment plan. The TPA approves an initial credit limit. During the stay, if the actual cost approaches or exceeds the approved limit, the system automatically generates an enhancement request. At discharge, the system generates the complete claim package, itemised bill, discharge summary, investigation reports, and all required supporting documents, in the specific format required by that TPA. The module maintains a library of TPA-specific formats and claim requirements so that every claim goes out correctly the first time. Claims that are rejected are tracked in a denial management queue with the rejection reason and recommended correction.