Skip to content
Sign In Book a demo
Hospital management system

Hospital management software for the whole hospital, on one patient record.

RAKT HMS runs the outpatient desk, the wards, the lab, the pharmacy, radiology, emergency and the operating theatre off one patient record. When a doctor orders a test, the lab sees it. When a patient is discharged, the bill is already right. And everything that happened that day is written down, with who did it.

Book a demo See the product
Most hospitals start with two departments and add the rest later. Nothing needs re-entering when they do.
OPDIPDLaboratoryPharmacyRadiologyEmergencyOperating theatre
7
Departments on one shared patient record
235
REST API resources with a published OpenAPI schema
33
Countries in the locale registry, dial code, time zone, currency format
200+
Blood centres already run RAKT software every day
Who it is for

Who this is for

Most of the people who call us are one of these three. Here is what tends to change for each.

Hospital administrators

Your day is bed occupancy, an OPD queue that will not stay in order, pending reports and a billing counter that has to reconcile by evening. RAKT puts all of it on one record and one screen, so “where is this patient’s file?” stops being a question.
See RAKT HMS

Laboratory and pharmacy owners

Orders to signed reports with quality control an assessor will accept. Batch- and expiry-aware stock with a day close that actually ties out. Run standalone today; when you become part of a hospital, it is the same system with more departments switched on.
Lab and pharmacy modules

Multi-branch hospital groups

Every record belongs to one organisation and one branch. Roles are granted per department per branch, cross-branch links are explicit, and group-level reporting sits on top, without one branch ever seeing another’s patients by accident.
How branches work
Where hospitals usually start

Sized to the hospital you have

Clinics and nursing homes

OPD with pharmacy, sometimes the lab. Nothing you do not need yet.
OPDPharmacy

Multi-speciality hospitals

All seven departments on one record, switched on over a few months.
7 departments

Hospital groups

One organisation, departments per branch, records separate unless you link them.
Per-branch

Standalone labs and pharmacies

That one department on its own, growing into a hospital without a migration.
LabPharmacy
Departments

One hospital management system, seven departments

Each department is a module on the same underlying system. Turn one on and it comes with its own dashboard, worklists, billing, printouts, audit trail and reports, because those are built once and shared.

OPD (outpatient)

Queue and appointments, vitals, clinical notes, signed prescriptions checked against the allergy record, online booking paid before the slot is confirmed.

IPD (inpatient)

Wards, rooms and beds with an occupancy view; admission, transfer and consultants; medication administration at the bedside; bed-day accrual; discharge summary as PDF.

Laboratory (LIS)

Order to signed report with specimen rejection, verification and critical-value escalation. Levey–Jennings QC, EQA cycles, CAPA and incidents, outsourced tests.

Pharmacy

Batch- and expiry-aware stock, goods receipt and purchase orders, counts, transfers and returns. Dispense from OPD and IPD; cashier shifts and day close.

Radiology (RIS)

Study orders and appointments, versioned reports from templates, critical-finding escalation, unreported-study alerts and a turnaround-breach register.

Emergency

Registration, five-level triage with primary and secondary survey, observation and disposition; medico-legal case numbering; admit straight to IPD.

Operating theatre

Booking, cases and rooms; anaesthesia record; the WHO surgical safety checklist; consents, implants and consumables; sterile instrument sets and batches.

Shared by every module

One patient record and identifier engine One invoice, whoever is paying Audit trail on every change Roles and permissions per module Analytics, MIS and PDF output
A day on the record

An ordinary Tuesday, step by step

This is what a weekday looks like inside RAKT. Every step is a screen that exists today, not a plan for one.

08:30 · Front desk

A walk-in is registered

A patient ID on your numbering rules. Phone verified by one-time code. Consent captured once, properly, not on every form again.

09:10 · OPD

The doctor sees the queue in order

Vitals are already in from the nurse. The prescription is signed with an allergy check against the record, not against memory.

09:40 · Laboratory

The order is on the worklist

Nobody re-typed it. If the sample is rejected, the reason is recorded now instead of argued about at the counter later.

11:20 · Report

Signed, and on the patient’s phone

The pathologist signs. The PDF reaches the patient on WhatsApp before they have found their car, consent-gated, per patient.

12:00 · Ward

Admitted from OPD in two clicks

Bed allocated, bed-days accrue by themselves, and each medicine given is recorded at the bedside, not from memory at shift end.

17:30 · Billing

One invoice, whoever pays

Visit, tests and stay on one bill, split with the insurer. The discount that needed a signature has one, with a ticket to prove it.

19:00 · Day close

The counter ties out

Cashier shifts reconcile. The activity log has who did what, in which role, all day, for the auditor, and for you.

What patients notice

The part your patients will actually see

Most of RAKT is for staff. These four things reach the patient directly.

Reports on their phone

  • The signed lab or radiology report arrives on WhatsApp as a PDF
  • Sent only with consent recorded on their record, and they can withdraw it

Booking without a phone call

  • Book a slot online and pay before it is confirmed
  • A queue token on arrival, so the order is the order

Their own record, with a code

  • Sign in to the patient portal with a one-time code
  • No password to remember or to leak

One bill that adds up

  • Visit, tests, stay and medicines on one invoice
  • A statement of charges and payments whenever they ask
Billing

Hospital billing software that follows the patient

The invoice attaches to whatever created it: a visit, an admission, a lab order, a dispense. So payers, discounts and refunds are handled once, the same way, in every department.

Payers are first-class

Insurers, corporates and public schemes with the patient’s policy on file. Bill the patient, the payer, or split by co-pay on one invoice.

Pre-authorisation and claims

Requested, approved, denied or enhanced against the admission; then a claim from draft to settled with deductions recorded, so the ledger matches the remittance.

Discounts that need a signature

Line or total discounts go through an approval queue, so a waiver is a decision someone made and can be found later.

Shifts, day close, statements

Cashier shifts and day-close reconciliation; expenses and referral payouts tracked; a patient statement of charges and balance on demand.
Open by design

Everything the screens do, your systems can do too

The browser is just one client of the API. Your accounting software, your SMS gateway or an AI assistant can be another, and each one gets the permissions of the person whose key it is using, no more.

REST API

235 resources with an OpenAPI schema, Swagger and Redoc. Organisation-scoped keys, bound to a user, read-only until you flip them.

AI assistants, with your permissions

An MCP server exposes department surfaces to Claude, Cursor and other MCP clients. Every call goes back through the API under the caller’s own key, so audit is identical to a browser session.

Webhooks and an app store

Install apps with scoped grants. Deliveries are signed, retried and logged, for the events you subscribe to.

Reports where the phone is

Lab and radiology reports as WhatsApp template messages with the PDF attached, consent-gated per patient; scheduled summaries by email.
Roles and security

Permissions the server enforces

Every request is checked against a permission code on the server. Hiding a button is never the control. A receptionist cannot sign a lab report, whatever the screen shows.

A permission catalogue per department

Each module ships its own catalogue and named default roles. Organisation masters short-circuit; everyone else holds explicit grants per department instance.

An append-only activity log

Actor, their role at that moment, and a structured before-and-after on every change, readable per organisation and per department.

Locked down by default

Government ID fields encrypted at rest. Five failed sign-ins lock the account for a cooling-off period. Every edit to a record goes through a change request.

Branches stay separate

Every record belongs to one organisation and one branch. Cross-branch links are explicit, never implied.
Country editions

Compliance follows your country setting

Tax, statutory registers, payer conventions and phone formats differ by country. RAKT HMS carries one flag per organisation and the country-specific screens read it, nothing foreign shows up in your menus. Dial codes, time zones and money formatting already resolve for 33 countries.

Editions today

1 shipped
IndiaGST and GSTR-1, e-Invoice, insurer and TPA claims, consent law, statutory registersShipped
Everywhere elseGlobal configuration, locale, currency format and dial code from your country; tax and registers not yet modelledGlobal
Further editions as they shipRoadmap
Straight answers

What isn’t finished yet

Every demo looks finished. Here is what isn’t, so you find out from us and not after signing.

Standalone Labs and Pharmacy products are still comingRoadmap

Today they ship as departments inside RAKT HMS. For a standalone lab that is usually still the right starting point, and we will say plainly if it is not.

The interface is EnglishTranslation framework in place

Strings are catalogued for translation and patient-facing documents can carry your own bilingual text. Full interface translations are not done yet.

Only one country edition has shippedIndia

Outside India your organisation runs the global configuration: locale and currency are right, but your country’s tax and statutory registers are not modelled yet. Tell us what your inspectors ask for.

Hosted in India todayOther regions on request

One tenant per organisation, backups to encrypted storage. If your policy needs another region or an on-premise install, raise it before you sign, not after.

How it goes

How it usually goes

There is no twelve-month implementation. This is the shape of it for most hospitals.

1

A walkthrough on your numbers

Send us your tariff sheet and how many beds you run, and we show you RAKT set up that way rather than a sample hospital.

2

Your data, imported

Patients, doctors, tariffs and your drug list come in from the workbooks you already have.

3

One department goes live

Usually OPD with pharmacy, or OPD with the lab. The rest can wait until the team is comfortable; adding them later does not mean re-entering anything.

4

Support on WhatsApp and email

You reach people who know the product. Inside the screens there are 130 help articles, each written for whoever sits at that particular desk.

FAQ

Questions we get asked before a demo

What is a hospital management system, and what does RAKT HMS cover?

A hospital management system runs the operational and clinical record of a hospital: registration, appointments, consultations, orders, admissions, billing and discharge. RAKT HMS covers seven departments. OPD, IPD, laboratory, pharmacy, radiology, emergency and operating theatre, on one patient record, with one invoice and one activity log across all of them.

Can we start with one department and add the rest later?

Yes, and most hospitals do. Departments are enabled per organisation and per branch. Because the patient record, billing and activity log are shared from day one, switching on IPD or radiology later moves nothing and re-enters nothing.

How is RAKT HMS priced?

Per organisation, by the departments you switch on. Hospitals outside India are billed in US dollars; Indian hospitals in rupees with a GST invoice. A single price list would be wrong for most hospitals, so we quote against your bed count and departments.

Who owns our data, and can we export it?

You do. Each organisation is its own tenant. A full export is available at any time over the API or on request, and everything the screens show is available through 235 documented REST resources.

Is it cloud-hosted or on our own servers?

Cloud, operated by RAKT, one tenant per organisation. Today that infrastructure is in India; if your policy needs another region or an on-premise install, raise it before signing so we can answer honestly.

Does it work outside India?

The platform is country-aware: dial codes, time zones and locale resolve from your organisation's country for 33 countries, and money formats accordingly. Country-specific tax and statutory registers are shipped for India today; every other organisation runs the global configuration.

Who we are

Who is behind this

RAKT started with blood bank software, which is about the most inspected thing you can build for a hospital. More than 200 blood centres still run it every day. RAKT HMS came after, and it shows: each screen names the register, rule or record it exists for. We are based in Delhi, and the people who answer support@rakt.in are the people who built it.

Get in touch

Demos, quotes and awkward questions all land in the same inbox, and it is read by people.
+91 70427 21037
support@rakt.in
Delhi, India · hosting in Bengaluru

Want to see it with your own numbers?

Send us the departments you run and how many beds you have. We will walk you through RAKT on a call, set up your way instead of as a demo hospital.

Book a demoExplore RAKT HMS