Hospital OS · Enterprise SaaS
A modular, cloud-native platform that unifies clinical, operational, financial and administrative workflows into a single connected ecosystem — reducing fragmentation for hospitals operating in the Indian healthcare market.
This is a self-initiated project grounded in real Indian healthcare-industry research, regulatory analysis and public competitor documentation. It is not presented as commissioned client work.
11
operational domains
from Patient Access through Administration & Compliance — the architectural pillars the platform is organised around.
42
departments
coordinated across 4 functional blocks: front-of-house, clinical core, ancillary/diagnostic, and back-office.
443
workflows mapped
each one specified down to its trigger, actors and system integrations before any interface was considered.
19
vendors researched
spanning enterprise EHR, India-focused HIS/EMR, and specialised point solutions (billing, patient engagement, RCM).
01 / Problem
Modern hospitals rely on separate software for appointments, records, billing, pharmacy, labs, inventory, HR and CRM. As hospitals grow, these specialised applications rarely operate as one cohesive system.
Staff spend significant time coordinating between systems instead of delivering care, duplicate data entry is routine, and leadership lacks a single view of operations across departments.
Core design question
How might we design a unified Hospital Operating System that simplifies healthcare operations while supporting the needs of every department through a single, scalable platform?
02 / Context
Before designing any screen, the research grounded the platform in how Indian hospitals actually operate as regulated, financially complex enterprises.
Government/public hospitals (AIIMS, district hospitals), corporate chains (Apollo, Max, Fortis), trust and not-for-profit hospitals, private standalone facilities, and single-specialty day-care clinics all operate under different economics and constraints.
Salaries and benefits account for roughly 43–56% of hospital revenue, which is why bed occupancy and staff utilisation — not just software features — drive whether a hospital survives.
A single hospital concurrently manages out-of-pocket cash patients, private insurance (TPA) claims with strict pre-authorization workflows, and government schemes like PM-JAY at standardised, discounted rates.
ABDM/ABHA interoperability mandates, the DPDP Act's consent and access-control requirements, NMC's biometric attendance rules, and IRDAI's 1-hour cashless pre-authorization timeline all shape what the platform must guarantee, not just offer.
03 / System model
Rather than starting from software features, the research mapped the hospital itself: every domain, department, workflow, actor and dependency — the foundation a modular platform has to be built on.
Select a domain to see its operations, actors and dependencies
11 operational domains, decomposed further
Each domain breaks down into departments (e.g. Patient Access → Registration, Scheduling, Admission Desk).
A hospital coordinates roughly 42 departments across these 11 domains — mapping them first is what makes a modular platform possible.
04 / Workflow depth
Every one of the 42 departments was decomposed into its actual workflows — each specified with its trigger, its actors and the systems it has to talk to. Four examples, spanning very different parts of the hospital:
Rapidly assesses an arriving patient's condition, assigns an evidence-based urgency category, and routes them to the right treatment area within minutes.
Actors
Triage Nurse, Emergency Physician, Trauma Team
Analyses clinical data in real time and delivers evidence-based, patient-specific guidance to clinicians — while keeping the clinician the final decision-maker.
Actors
Physician, Nurse, Pharmacist
Governs the safe transition out of inpatient care — clinical sign-off, medication handover, patient education and encounter closure — so no step gets skipped to save time.
Actors
Attending Physician, Discharge Nurse, Case Manager, Billing Team
Investigates, corrects and appeals insurance claims a payer has denied after adjudication — the workflow that decides whether the hospital actually gets paid for care already delivered.
Actors
Denial Management Specialist, Medical Coder, Appeals Coordinator
05 / Competitive research
19 hospital and healthcare software vendors were researched across three tiers — global enterprise EHR, India-focused HIS/EMR, and specialised point solutions — deliberately before evaluating any interface.
Enterprise EHR / HIS
India-focused HIS / EMR
Specialised point solutions
Questions asked of every vendor — deliberately not about UI
What modules does this vendor actually provide?
What real operational problems do they solve?
What do they explicitly ignore or leave to other vendors?
What integrations does adopting them require?
06 / Product scope & principles
Patient registration, EMR, appointments, consultation, admissions, discharge, nursing workflows.
Laboratory, radiology, report management.
Prescription management, drug inventory, dispensing.
Billing, insurance, CRM, sales pipeline, customer support.
HR, attendance, shift scheduling, asset management, procurement.
Mobile portal, appointment booking, digital consent, payments, notifications.
Design principles guiding every later phase
07 / Where this stands
I'd rather show exactly what's done and what's next than round the project up to a finished product.
Phase 1 — Discovery
Phases 2–18 · Ahead
Ahead of the process — an early prototype
The 18-phase process above is still in discovery, but I built Nadi — an authenticated, deployed OPD workspace — to pressure- test whether the Spine design system holds up once it’s wired to real routes and real auth, rather than waiting for Phase 15 to find out.
Sign in to Nadi ↗Continue exploring
