Not an HMSThe revenue layer above the one you already run — orchestration for hospitals, health aggregation for employers.See the difference →
Sign inGo to my accountStart freeGo to my account
Booking page For doctors For hospitals Corporate health Health packages Labs Pharmacy Nadi Compare Free tools Referrals Claim help
Home › Integration design

Connect what you need.
Keep control of what you don’t.

Healthcare data moves through many systems. Drapto starts with the information already made available to your organisation, then designs a controlled path into the workflow rather than collecting credentials or creating fragile dependencies.

NADI · DRAPTO
● Platform 27 modules
● Rules 24, rationale attached
● Figures worked arithmetic
✓ watched to the bank

The screen

Every settlement advice already reaches your inbox. Drapto reads it there. No TPA portal password is ever asked for or stored.

Integration planning

Design the boundary before you connect the system.

The boundary between Drapto and an existing hospital system
Two systems, one agreed boundary. Clinical records never cross it.

Every enterprise rollout needs an explicit answer to what flows in, who owns it, how it is mapped and which credentials never leave your control.

Source mappingIdentify the information already available and the business event it must support.
Controlled interface modesUse secure routes such as approved APIs, structured files or governed forwarding where appropriate.
Implementation by marketReview local payer, privacy and interoperability requirements during each rollout.
01The payer sends the advice

Email, portal download, or NHCX bundle. However they do it today, unchanged.

→
02It reaches one address

claims@yourhospital.drapto.in — set a forwarding rule once, or forward manually. Both work.

→
03Parsed, split, queued

Reconciled line by line, predictable separated from unexplained, on your worklist before anyone opens a portal.

Why not just log into the portals?

No open APIs existMedi Assist, Paramount, Vidal, FHPL, Raksha, MDIndia and the rest run credentialed web apps. There is no hospital-facing API to call.
Credentials are a liabilityAny vendor holding your portal logins is a breach waiting to be attributed to you. We would rather not hold them, and you should not want us to.
Automated access usually breaches their termsScraping a payer portal risks your access, not ours. A tool that gets your TPA login suspended has cost you more than it saved.
The inbox works with all of themEvery payer sends an advice somewhere. That is the one integration point common to all twenty, and it needs no permission from any of them.

Four ways an advice can reach us

Four ways an advice can reach us
RouteSetupWorks withEffort per claim
Auto-forward ruleOnce, in your mail clientAny payer that emailsNone
Manual forwardNoneAny payer that emailsOne click
Upload — PDF or imageNonePortal downloads, scans, paperDrag and drop
NHCX bundleYour NHA onboardingPayers live on NHCXNone

The first two cover the majority of Indian payers today. The fourth grows as NHCX adoption does — and needs no change at your end when it happens.

What we do with what arrives

  • Patient identifiers are stripped on ingestion, before anything is parsed or stored. Names, UHIDs and policy numbers do not enter the record.
  • Data stays in India. Indian data centres, no cross-border transfer, aligned to DPDP obligations.
  • We never hold a payer credential. Not for your portals, not for your mailbox — a forwarding rule sends us a copy, it does not give us access.
  • You can stop it in one step. Delete the forwarding rule and the flow ends. No integration to unwind.
Try it on 20 settled claims — free Paste one advice now →

Corporate contracts, without changing your system.

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

What arrives each monthBook a review