The whole hospital, on one screen.
OPD queue, IPD beds, lab orders, pharmacy stock and the day’s MIS — updated as your team works. Seven departments on one patient record and one bill, from the team that runs blood bank software at 200+ centres.
Where the day stands
Just now
Departments: OPD, IPD, Lab, Pharmacy, Radiology, Emergency, OT
Documented REST endpoints, OpenAPI schema published
Automated tests, plus a seven-day hospital simulator in CI
In-app help articles written for the staff who use it
Seven departments that share one patient, one bill and one activity log
Not modules bolted together. A lab order raised in OPD lands in the lab worklist, a discharge prescription lands in pharmacy, and every step is written to the same audit trail with the role that made it.
OPD
Queue tokens, doctor schedules, vitals, SOAP notes, consult templates and signed prescriptions with an allergy check against the patient’s record. Public self-booking with online payment.
IPD
Wards, rooms and beds; admission, transfer and consultants; progress notes, medication orders and administration (eMAR), intake/output, deposits, discount approval and pre-authorisation.
Laboratory
Orders to signed reports with specimen rejection, verification, amendments and critical-value escalation. QC with Levey–Jennings, EQA cycles, CAPA, incidents and outsourced tests.
Pharmacy
FEFO batch picking, GRNs, purchase orders, stock counts, transfers, returns and supplier debit notes. Cashier shifts and day close for the counter.
Radiology
Study orders, appointments, versioned reports from templates, critical-finding escalation, stale-order and unreported-study alerts, turnaround-breach register.
Emergency
Registration, triage, vitals and disposal; medico-legal case numbering; admit straight to IPD; the ER register and death certificate as PDFs.
Operation theatre
Booking, cases and rooms; anaesthesia record with drugs and vitals; WHO surgical safety checklist; consents, implants, consumables; CSSD instrument sets and sterilisation batches.
Shared by all seven
Configurable UHID, IPID, invoice and report numbering. Daily summaries by WhatsApp, tickets for every change request, staff and permissions per branch, registers and MIS reports.
The same journey your front desk, wards and lab already run
Each step below is a real screen, and each writes to the record the next step reads from.
Register
UHID issued on your numbering rules; phone verified by OTP; consent captured.
Appointment
Walk-in, phone, referral or self-booked online. Queue token on arrival.
Consult
Vitals, notes, investigations and a signed prescription with an allergy check.
Orders
Lab and radiology worklists, pharmacy dispense — from the same visit.
Admit
Bed allocated or reserved, bed-days accrued, medication administered on the ward.
Bill
One invoice whoever pays: patient, insurer, TPA or corporate, with split co-pay.
Discharge
Signed summary from a template, balance cleared, discharge prescription to pharmacy.
One bill, whoever is paying
The invoice attaches to whatever generated it — a visit, an admission, a lab order, a dispense — and payers, discounts and refunds are handled once, the same way in every department.
Payers and split billing
Insurance, TPA, corporate and government-scheme payers with patient policies. Bill the patient, the payer, or split by co-pay percentage.
Pre-authorisation and claims
Requested, approved, denied or enhanced; then a claim from draft to settled, recording TDS and disallowances.
Discounts that need a signature
Line or total discounts, with an approval queue in IPD so a waiver is a decision someone made, not a keystroke.
Day close and statements
Cashier shifts, day-close sessions and reconciliation. A patient statement PDF of charges, payments and balance on demand.
The compliance a hospital in India is actually inspected on
Where the country has a form, a register or a statute, RAKT HMS has the screen — and it is switched on by the organisation’s country, not by a plugin.
- GST on every line with HSN/SAC, CGST/SGST/IGST split by state, per-branch tax profiles
- GSTR-1 filing export as a four-sheet workbook: B2B, B2CL, B2CS and HSN
- NIC e-invoice JSON generated per invoice; IRN, acknowledgement and QR stored against it
- Insurance and TPA pre-authorisation and claims, with TDS and disallowance
- DPDP Act 2023: purpose-scoped consent, erasure requests with a cooling-off window, public privacy notice
- Schedule H, H1 and X on every drug, with the H1/X dispensing register as an export
- IDSP notifiable-disease register with the reporting authority and statutory time limit
- UPI and cards through Razorpay; reports and daily summaries delivered on WhatsApp with consent
Connects to how your hospital already runs
The channels patients answer on, the way money arrives, and an API for everything else.
WhatsApp Cloud API
Lab reports, daily summaries and late-arrival notices as template messages with the document attached. Consent-gated, per-patient.
SMS with DLT templates
MSG91 or Textlocal, with registered template IDs, for OTPs and reminders.
Razorpay
Online payment for self-booked appointments, server-verified before the slot is confirmed.
REST API
Over 1,100 documented endpoints with an OpenAPI schema; organisation API keys for users and services; rate limits and CORS per origin.
Webhooks and App Center
Install apps with scoped grants; deliveries are HMAC-signed, retried and logged.
Biometric attendance
Enrol staff on attendance devices and bring their punches into the roster.
Who did what, with which role, and what changed
A hospital record is only as good as the trail behind it. These are in the product, not in a policy document.
Roles per department, per branch
Each department ships its own permission catalogue and named default roles — receptionist, nurse, billing, pharmacist and more. The server decides; screens follow.
An event on every change
Actor, role at the time, what changed and the diff, on every department’s activity log, with retention you set.
Locked down by default
Government ID fields encrypted at rest, twelve-character password floor, lockout after five failed attempts, one-day reset links.
Branches that stay separate
Every record belongs to one organisation and one branch. Cross-branch links are explicit, never implied.
Questions hospital administrators ask first
Can we start with two departments and add the rest later?
Yes. Departments are enabled per organisation and per branch. Most hospitals begin with OPD and pharmacy or OPD and lab, and switch on IPD, radiology, emergency and OT as the team is ready. The patient record and billing are shared from day one, so nothing has to be migrated when a department is added.
Is RAKT HMS cloud-hosted?
Yes. Each organisation runs as its own tenant with its own branches, timezone and locale, on infrastructure RAKT operates. Your data can be exported in full at any time, and DPDP erasure requests are processed on a schedule you set.
Does it include the blood bank?
The blood bank is a separate RAKT product, running at 200+ centres across India, and lives at rakt.in. Hospitals that run both get the same team and the same standards of record-keeping; the two systems are licensed separately.
What about ABHA and ABDM?
A patient’s ABHA number can be recorded on their record today. Linking through ABDM — verifying the account and pulling demographics — is on the roadmap and not yet shipped; we would rather say so than print an integration you cannot use.
Can our other systems talk to it?
Yes. Everything the screens do is available over a documented REST API with an OpenAPI schema, authenticated by organisation-scoped keys. Outbound, the App Center delivers signed webhooks for the events you subscribe to.
See RAKT HMS on your own workflow
Tell us how many beds, which departments and what your registers look like. Demos are run by people who have set the product up in a hospital, not from a script.