Not an HMSThe revenue layer above the one you already run — orchestration for hospitals, health aggregation for employers.See the difference →

SOLUTIONS · POWERED BY NADI AI

One platform. Every gap covered.

Twenty-seven modules on one governed spine — clinical, operational and financial, from the first booking to the settled claim.

Talk to usExplore the platform
NADI · PLATFORM · SPINE
● Events today streaming
● Rationale attached
● Ledger single
✓ 27 modules, one spine
27 modules5 gates1 ledger

WHAT THIS IS, AND WHAT IT IS NOT

You already have an HMS. This is the layer above it.

Most hospitals we talk to have working software. It is mature, it is fine, and it is not the problem. The gap is narrow, specific and expensive — and it sits after the record is written.

  • Not an HMS
  • Not an EMR
  • Not a billing add-on
  • Not a marketplace
What your system does

Records that the claim was reduced, after it was reduced.

What Drapto does

Warns at admission that the room breaches the cap, while somebody can still move the patient.

Healthcare

Revenue orchestration

Claims governance, deduction defence and settlement reconciliation, scored by Nadi before a claim leaves the building. Thirty beds to three hundred.

Enterprise

Corporate health aggregation

One roster, one panel, one invoice. Caps tracked live; HR sees participation and utilisation, never a diagnosis.

And underneath both

The front office, free forever

Booking, queue, prescriptions and the patient record at zero cost for every clinic in India. The free half builds the network the paid half watches.

THE NUMBERS

Four points where a claim loses value.

The gates exist so the bars stay whole. Worked arithmetic, illustrative.

STAGE LOSSWhere the platform intervenes
Waterfall of an illustrative claim losing value at four stages.Waterfall from Billed to Settled.₹100,000Billed−₹6,800Front office−₹9,100Documentation−₹6,000Coding−₹7,400Settlement₹70,700Settled₹29,300 NEVER ARRIVES
  • Billed
  • Deducted
  • Settled

Four intervention points, four different modules. The platform is not one thing that catches everything; it is four things that each catch one.

Illustrative arithmetic. Your own figures will differ.

THE PLATFORM LOOP

Twenty-seven modules. One patient record.

Modules Nadi EVENT.SPINE RATIONALE.ATTACHED every module writes to one ledger
NADI · COVERAGE
● Modules 27
● Governance rules 24
✓ one spine under all

WHAT WE WILL NOT TELL YOU

What the platform will not do.

Not published

Settlement rates we have not measured.

Not published

Which payer to avoid.

Published instead

Mechanisms, gates, and arithmetic you can redo.

HOW IT LANDS

One record. Twenty-seven modules reading from it.

Modules are not products bolted together. They read and write the same patient record, which is why a room-cap breach at admission is visible to the claims desk before the claim exists, and why a settlement advice can be read against the bill that produced it.

Turn on what you need

A hospital already running an HMS starts with revenue integrity alone. The clinical half stays off until it is wanted, permanently if that is the answer.

Live in days, not quarters

Data in and roles set on day one; the desk runs on it inside a week; the first reconciliation cycle closes end to end inside a month.

Nothing is a rip-and-replace

Your record system keeps recording. This is the layer that acts on what it records.

Turn on only what you need. The front office is free.

Twenty-seven modules, one record. Start with the one that is costing you most.

Twenty-seven modules and an assistant.

Named after what the work is called, not after where it sits in an org chart.