The Enterprise plan

Everything in this kit,
switched on for your hospital.

The AI layer — all 34 capabilities across 10 departments, the 6 agents, the Guardian, the audit trail and the programme registers — is the Enterprise plan. Below is what that includes, roughly what it costs, how a rollout runs, and the questions we would ask a vendor if we were sitting on your side of the table.

What you get

The whole AI layer

Every capability, not a module list. New capabilities arrive in the plan rather than as an upsell.

Governance you can show a regulator

Guardian policy, hash-chained audit trail, evaluation suite, per-agent kill switch, and the compliance pack an accreditation visit asks for.

Interoperability

FHIR R4 and HL7 v2, scoped API tokens per connected system, and consent artefacts with ABDM identifiers.

Multi-site

One deployment, tenant-separated data, per-hospital AI settings — so a group can run one site live and another in observe mode.

Programme registers

TB, maternal and child, immunisation, chronic disease and prevention, with the returns produced from the record.

A named implementation path

Baseline, shadow, narrow go-live. Described on the business case page, and measured against figures you freeze before we start.

How it is priced

Two very different kinds of deal, priced on two different bases. A hospital, or a group of them, buys operational value out of its own revenue. A deployment covering a whole state or country — a health system or a chain spanning one — buys something else: it replaces the licensing, the reporting and the reconciliation of every site at once. A larger number, because it is a larger job.

Private hospitals and groups

Self-serve plans

Clinics and single hospitals
₹15k – ₹5L
per month · card payment
  • The hospital management system
  • Appointments, records, pharmacy, billing
  • No AI layer
Most common

Hospital Enterprise

One hospital, 100–250 beds
₹1.2 – 2.5 Cr
per year · invoiced
  • The entire AI layer
  • Typically modelled per bed per month
  • Implementation and AMC quoted separately
  • Governance and audit included, never an add-on

Large hospital

One hospital, 250–500 beds
₹2.5 – 5 Cr
per year · invoiced
  • The entire AI layer, as every tier above self-serve
  • Picks up where Hospital Enterprise stops, at 250 beds
  • Still one hospital, so still one tenant and one governance board
  • Implementation and AMC quoted separately

Network

One hospital over 500 beds, or groups of 5–10 facilities
₹5 – 25 Cr
per year · master agreement
  • Anything past 500 beds is a Network deal, whether that is one hospital or ten
  • Group pricing runs five to ten times the single-hospital band, less a discount
  • Every site on one deployment
  • Comparable registers across sites
  • Central governance, per-site settings

Government, state-wide and nationwide deployments

State programme or state-wide hospitals

A state health system, or a chain across one state
₹10 – 50 Cr
per month · invoiced
  • Every facility in the state on one platform, public or private
  • TB, maternal, immunisation and NCD registers produced from the record
  • Scheme claim integrity checked before payment
  • State-level surveillance across all reporting sites

National programme or nationwide hospitals

A national health system, or a chain across the country
₹50 – 100 Cr
per month · master agreement
  • Every state on one deployment, data separated per tenant
  • Fits a nationwide chain as readily as a national programme
  • One definition of every indicator, so states are comparable
  • National surveillance signal, not a per-state view
  • Consolidates per-facility licensing across the estate
Why the programme numbers are an order of magnitude larger. They are not the hospital price multiplied up. A deployment at this scale — a state health system or a chain spanning one — replaces per-facility licensing across thousands of sites, produces the programme returns those sites file by hand today, and checks scheme claims before they are paid rather than after. Those levers do not exist in a single hospital, which is why they are priced separately rather than as a volume discount. Work the figures yourself on the business case page — the programme scale is a tab on it.
Why there is no "buy now" button on any of these. A crore-scale charge does not go through a card checkout, and the price depends on beds, sites, integrations and how much data has to be migrated. Anyone who quotes you a number before asking those questions is guessing.

How a rollout runs

Freeze a baseline

Current length of stay by specialty, denial rate by payer, time from observation to escalation, 30-day readmissions. Before anything is switched on, so the comparison later is real.

Connect what you already run

Lab analysers and any existing systems over HL7 or FHIR, each with its own scoped token. Data migration scoped here, because it is usually the long pole.

Shadow on one ward and one clinic

Every agent capped at observe. It records what it would have flagged and nobody acts on it. You compare its calls against what actually happened, with the audit trail as the evidence.

Go live, narrow

Turn on the two capabilities that shadowed best. Your medical director sets the Guardian levels. Everything else stays in observe.

Widen on evidence

Each subsequent capability goes live because its shadow period justified it, not because it was in the contract.

Questions worth asking us

Including the ones with awkward answers. If a vendor cannot answer these, that is information.

What happens when the model is unreachable?The deterministic engines keep running — scoring, triage, interaction checks. Drafting and summarising stop. The product degrades; it does not fall over.
Can the AI be switched off after go-live?Per agent, per level, per hospital, immediately. The attempt is still recorded so the switch-off is itself auditable.
Who can see patient data?Permissions are per action and per tenant. Personal and clinical files are stored apart from public assets and served through signed, expiring URLs.
What are the known limitations?Written down in the Technical Architecture document in the kit. A vendor document with no limitations section is one to be suspicious of.
Do you have outcome data from other hospitals?No published study. We will not show you someone else's numbers as a prediction of yours — which is exactly why the rollout starts with a shadow period.
What happens to our data if we leave?Export of the record and the audit trail. Worth putting in the contract, with us or with anyone else.

Start with the awkward questions

Send the list your CISO and medical director would ask. We would rather answer those first than run a demo that avoids them.

Talk to us about Enterprise See all plans