Hospital - multi-tenant HMS
Run the whole hospital
on one platform.
From the front desk to the final bill, Hospital carries one patient record through OPD, wards, theatre, diagnostics, imaging and billing - with medical imaging built in.
My clinic - Dr. Osei
- OPD queue - 6 waiting
- R. Mehta - ward round due
- CT chest - ready to read

The whole hospital
One platform, department by department.
Every role opens the same platform to its own view. These are the real workbenches - one short line each, no jargon.
Front desk
Patient Registry
One patient record, created once, that every department shares.
Front desk
Appointments & OPD
Book against real doctor availability and issue queue tokens at the desk.
Clinical
Clinical Care
Notes, vitals and e-prescriptions on the same chart the whole team sees.
Ward
Nursing
Shift rosters and medication rounds charted in place, so handover carries forward.
Ward
Ward & Beds
Rooms, beds and occupancy on one live status board.
Theatre
Surgery / OT
Theatre scheduling with anaesthesia records, staff, implants and intra-op events.
Diagnostics
Diagnostics & Lab
Order tests, capture results by parameter, and return them to the chart.
Imaging
Radiology
Open scans in a built-in viewer, right beside the patient record.
Pharmacy
Pharmacy
Prescriptions and medication administration, tied to each patient.
Finance
Billing
OPD bills, patient bills, bill items and room charges on the same record.
Admin
Admin
Set up departments, staff, rooms and services for your hospital.
Platform
Superadmin
Provision new hospitals, tenant admins and subscription plans.
The whole hospital loop
One record, front desk to final bill.
Every step writes to the same tenant-scoped record, so each role picks up exactly where the last left off - no re-keying between systems.
01
Registration
Patient created once
02
OPD & queue
Token, consult
03
Admission
Bed assigned
04
Surgery / OT
Theatre + anaesthesia
05
Diagnostics
Lab + radiology
06
Discharge
Summary + clearance
07
Billing
Bills settle
One record
One record follows the patient, front desk to final bill.
WardBuilt-in imaging
Medical imaging, built in.
- View CT, MR, X-ray and ultrasound studies in-product
- No separate PACS to license or log into
- The scan sits beside the patient chart
RadiologyMulti-tenant SaaS
One platform. Many hospitals.
Hospital runs as multi-tenant SaaS. Every record lives inside its hospital's tenant, isolated by design, and access is decided by role. One system serves many hospitals without their data ever touching.
- Each hospital's data is sealed inside its own tenant - no request crosses the boundary.
- Role-based access for admin, doctor, nurse, staff and patient.
- One deployment serves many hospitals - nothing shared to untangle.
Subscription plans - seeded per tenant (INR / month)
Single-site clinic - core OPD and records
₹2,500 / mo
IPD, theatre, diagnostics and imaging
₹5,000 / mo
Multi-site chain - full operations
₹15,000 / mo
Plans are defined and seeded in the platform. Hospital is pre-1.0 and pre-revenue - these are the tiers, not a customer count.
Where it fits
Where Hospital fits.
Hospital is a modern, integrated, multi-tenant hospital operations platform for the India and emerging-market private-hospital and clinic-chain segment. The neighbours keep their real strengths - it trades scale and certification for a lighter, cloud-native platform with imaging built in.
Enterprise EHRs keep certified suites, revenue-cycle depth and proven scale; India-market HIS keep broad, price-competitive local coverage. Hospital trades that for a lighter, cloud-native, tenant-per-hospital platform with imaging built in.
Under the hood
Governed by role, sealed by tenant.
The story above is the plain version. For evaluators, here is how it actually holds together - the frontend is React, the backend Spring Boot on Java 17 and PostgreSQL.
Multi-tenant isolation
Every entity carries a non-null tenant_id and a TenantContext is resolved once per request, so every read is scoped to one hospital. No context means no rows - the boundary fails closed.
Flexible, dual-mode auth
A hospital can run Hospital on its own login, or federate it into the Splenta identity fabric through ICE. Either way, access is scoped per tenant and decided by role.
mode A - standalone (default)
Built-in login with legacy JWT - short-lived access token plus refresh. Nothing external required.
mode B - federated
Resource-server mode validates ICE-minted tokens - aud = hms-api, scopes hms:* - for single sign-on across the family.
- superadmin
- admin
- doctor
- nurse
- staff
- patient
Built-in medical imaging
Hospital proxies its radiology API to an Orthanc PACS over DICOMweb and launches a vendored OHIF viewer inside the product - windowing, MPR, 3D and measurements next to the chart. Schematic facade below, no real study.
Studies - MRN 40118
- CT chest w/o contrastCT
80 img
- MRI brainMR
144 img
- Chest X-ray PAXR
2 img
- US abdomenUS
36 img
A boundary that fails closed
Hospital owns the clinical and operational record - not the warehouse, purchasing ledger or finance books. Those flows return "unavailable" until a real adapter is wired in. A blank you can trust beats a number you can't.
- unavailablePharmacy stockWMS adapter - roadmap
Drug catalog, stock levels and pharmacy billing need a warehouse system of record.
- unavailableProcurementSCM adapter - roadmap
Purchase orders and supplier flows belong to a procurement system of record.
- unavailableAccounting & financeFMS adapter - roadmap
Ledger and financial truth belong to a finance system - billing-support only here.
Private - early access
Bring your whole hospital onto one platform.
Hospital is pre-1.0 and private - no public download, no self-serve sign-up. We are taking on a small number of hospitals and clinic chains early. Tell us how you run your wards and we will map it to a tenant of your own.