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

India today · conversations open elsewhere

Built to travel. Sold in one market first, on purpose.

Drapto is engineered the way any serious international health platform is — FHIR R4, audit trails, standards-based claim bundles. It is sold exclusively in India right now because the thing that makes it work is depth in one payer system, not breadth across several.

NADI · DRAPTO
● Platform 27 modules
● Rules 24, rationale attached
● Figures worked arithmetic
✓ watched to the bank
Corporate contracts, brought inWithout changing the system you already run
Runs beside your HISA layer on top, not a migration
Paid on outcomesThe commercial reason to bring us with you
Your account, your clientWe stay the plumbing
Why one marketRoom-rent proportionate deduction, scheme package viability and Indian clinical shorthand are not features you localise. They are the product. Building them properly for one country beats approximating them for ten.
What is already portableFHIR R4 records, standards-based claim bundles, deterministic coding, audit trails and role model. The engine does not assume India; the rules layer does.
What a second market needsIts own payer mechanics, its own coding vocabulary, and someone on the ground who knows both. That is a partnership, not a translation.

Where the same problem exists

A panel of member clinics
Where the same problem exists, and who solves it together.

The mechanism Drapto was built for — a payer reducing a claim in ways the provider cannot see until settlement — is not unique to India. It recurs anywhere private insurance meets provider billing without a shared source of truth.

Where the same problem exists
MarketWhy the problem rhymesStatus
IndiaRoom caps, scheme packages, TPA fragmentationAvailable now
Gulf — UAE, Saudi, Qatar, OmanMandatory cover, dense private provision, large Indian clinical diasporaPartner conversations
Southeast Asia — Malaysia, Indonesia, PhilippinesMixed public scheme and private insurance, similar package mechanicsPartner conversations
Africa — Kenya, Nigeria, South AfricaGrowing private insurance against thin provider-side toolingExploratory
Bangladesh, Sri Lanka, NepalShared clinical vocabulary and comparable payer structuresExploratory

Status means what it says. “Partner conversations’’ is not a launch date, and we are not going to invent one.

Company and legal details, including the registered entity and where to write about anything contractual, are on the PartnershipsCompareCareersabout page.

Three ways to work with us

ImplementationIn India

Consultants and healthcare IT firms already inside Indian hospitals, implementing and supporting Drapto alongside their existing work.

  • Margin on licence and implementation
  • Training and certification provided
  • You own the client relationship
DistributionNew markets

For firms with real provider relationships in a market we do not serve. You bring the payer knowledge; we bring the engine.

  • Rules layer built for your payer system
  • Exclusivity discussed by market
  • Longer runway, deeper partnership
IntegrationPayer and platform

TPAs, insurers and health platforms wanting a standards-based provider-side integration rather than another portal.

  • FHIR R4 claim bundles
  • NHCX-ready in India
  • Fewer queries on both sides

What we will tell you on the first call

  • How many customers we have. Precisely, not as a range. You will hear the real number.
  • What is built and what is not. We do not transmit to NHCX. We publish no recovery percentages, because no customer has been running long enough to produce one.
  • What a second market would actually take. Months of payer-rule work, not a language file. If someone tells you otherwise they have not done it.

Corporate contracts, without changing your system.

We find the companies and run the outreach. Your existing software stays where it is.