Compare Build, replace or connect
What ABDM integration really costs, and why a connector is the cheaper way
Every hospital in India that wants to be on ABDM has three ways to get there. They differ far more in what they cost over two years than in what they cost on day one, because ABDM does not stand still: NHA moved every API to v3, changed how requests are encrypted, renamed callback paths and added certification cases, and whoever built the integration has to keep up. This page sets the three routes side by side, with the figures the market actually advertises.
01 The three routes
What each route asks of you
The choice is rarely about the first invoice. It is about who carries the integration for the years after it, and whether a hospital has to change the software its staff already know.
Build it in-house
A team of two to four engineers works through ABHA (M1), HIP linking and sharing (M2), HIU consent and record fetching (M3), FHIR bundle composition, the registries, a callback bridge that is reachable from NHA’s gateway around the clock, and then agency testing and a security audit. Public write-ups put a custom build in lakhs and months, and every later NHA change lands back on the same team.
Replace the HMIS with an ABDM-ready one
Cloud hospital software with ABDM built in is advertised from about ₹999 a month for a small clinic to lakhs a month for a large hospital, with full deployments quoted at ₹3 lakh to ₹50 lakh. ABDM comes with it, but so does replacing billing, OPD, IPD, pharmacy and lab workflows, migrating records, and retraining every department. If that is the route you want, we build one: Swastik HMS.
Connect what you already run
A connector adds ABDM to the software a hospital already uses, called from it over a REST API and reporting back with webhooks. The hospital keeps its records and workflows; the connector keeps up with NHA. Swastik is priced per hospital per month, every milestone included, with a free sandbox to build against first.
02 Side by side
Cost, time and who carries the next change
Market figures are the ranges Indian hospital-software and integration vendors advertised publicly in 2026. Swastik’s figures are the prices on the pricing page, read from the same source the billing system uses. Prefer to have it done for you? See integration services.
| Build in-house | ABDM-ready HMIS | One-time integration fee | Swastik connector | |
|---|---|---|---|---|
| Up-front cost | Engineering time in lakhs; agency testing and security audit paid separately | Deployment quoted at ₹3–50 lakh for a full hospital; smaller cloud plans from ₹999 a month | Advertised from about ₹4,999 per hospital, one time | None. Sandbox is free and needs no card |
| Running cost | Hosting, monitoring and the team’s time on every NHA change | The HMIS subscription, for every module, whether or not you needed a new HMIS | Depends on the contract: a one-time fee rarely includes the next v3 change or re-certification | ₹2,999 (Growth) or ₹4,999 (Scale) per hospital per month; less on a yearly plan |
| Time to first ABHA | Weeks, once the sandbox credentials arrive | Weeks to months: the migration sets the pace, not ABDM | Days to weeks, per the vendor’s queue | Same day: sandbox keys are issued when you verify your email |
| Time to production | Months: build, then agency testing, then the security audit | Inherits the vendor’s certification; the migration is the long pole | Inherits the vendor’s certification, if it has one for v3 | Inherits the connector’s certification; your part is HFR registration and onboarding |
| Your existing HMIS, EMR or LIS | Stays; you integrate into it | Replaced | Stays | Stays. The connector is called from it |
| Who carries the next NHA change | You | The HMIS vendor | Usually you, after the engagement ends | Swastik, for every hospital on the connector at once |
| Milestones covered | Whatever you build | Varies by product; check M3 and the registries | Varies; often M1 and M2 only | M1, M2, M3 and the HFR/HPR registries on every paid plan |
| Several hospitals | One integration per product; multi-tenancy is extra design work | Per-hospital licences | A fee per hospital | Multi-tenant by design: one contract, one price per hospital, isolated credentials and audit trail each |
| Error handling when NHA answers HIS-500 | Yours to decode | Inside the vendor’s product | Inside the vendor’s product | Plain-language explanations, the ABDM request id for support, and pre-flight checks that refuse what NHA would |
Market figures are the ranges Indian hospital-software and integration vendors advertised publicly in 2026, read on 25 September 2026. No single vendor is quoted: prices change, and the point is the shape of each route, not one company’s list price.
03 What is different
Why the connector costs less and holds up longer
None of this is a discount. It is what falls out of building one integration for many hospitals instead of one per hospital.
One integration, shared by every hospital
When NHA changes an API, it is fixed once and every facility on the connector has it the same day. A hospital pays a subscription, not an engineer’s month.
Priced per hospital, nothing per patient
₹2,999 or ₹4,999 per hospital per month, with a call quota of 50,000 or 2,00,000 a month. No charge per ABHA, per record or per consent, so an OPD that gets busier does not get dearer.
All four milestones, on the first plan
ABHA, HIP, HIU, FHIR and the HFR and HPR registries are on Growth. Scale differs in capacity, not in features: unlimited facilities, more team members and four times the quota.
The current API, not last year’s
Everything speaks ABDM v3: sealed Aadhaar and OTP fields, v3 link tokens, v3 consent and data flow, and the registries’ current hosts. Nothing left on the retired v0.5 paths.
Errors you can act on
NHA’s registries answer wrong data with a generic failure that names nothing. The connector checks a record against NHA’s own field rules before sending it, and when NHA still refuses, says what to check and gives the request id support asks for.
Registration built in, not a PDF
Registering a hospital in HFR and a doctor in HPR is a guided flow in the portal, with NHA’s master lists loaded for every field, address proof and photos handled, and the bridge linkage done at the end, which is the step most integrations miss.
Audited security posture
Field-level encryption for Aadhaar, OTPs and tokens, signed consent artefacts verified on arrival, per-tenant isolation and an append-only audit trail. The security page is written for the auditor who has to sign it off.
No lock-in on the record
Your software keeps the patient record and the clinical data. The connector holds identifiers, consent artefacts and audit, and every one of them is yours to export through the API.
04 The incentive
What the Digital Health Incentive Scheme does to the arithmetic
NHA pays facilities per ABHA-linked transaction above a base level. Under the November 2025 corrigendum that is ₹20 for hospitals and ₹15 for laboratories, at most one transaction a day and five a month per ABHA, extended in stages and subject to funds. See the guide to the scheme.
eligible OPD transactions in a month at ₹20 each cover the Growth plan for that hospital
cover the Scale plan; a 100-bed hospital sees many times that in linked OPD visits
per patient or per record from Swastik, so every incentive rupee after the subscription is the hospital’s
The arithmetic assumes the rates in force on 25 September 2026 and eligible transactions; the scheme’s base levels, windows and caps are NHA’s to set.
FAQ Common questions
Frequently asked questions
How much does ABDM integration cost in India?
Why is a connector cheaper than building ABDM in-house?
Do I have to replace my HMIS to use it?
Does the Digital Health Incentive Scheme cover the cost?
What is included at every price?
Next Keep reading
Related reading
Priced per hospital, not per patient
One ABDM integration, billed per hospital per month. Free sandbox with no card. ABHA, HIP linking, HIU consent, FHIR and the HFR/HPR registries on every paid plan.
ABDM integration, milestone by milestone
What ABDM integration actually involves: M1 ABHA, M2 care-context linking and record sharing, M3 consent requests and retrieval, and the HFR and HPR registries. Sandbox credentials, Fidelius encryption, callbacks and the audit that gates production access.
How much does ABDM integration cost in India? A realistic breakdown for 2026
Engineering time, certification, security audit, hosting and the cost of keeping up with NHA: what ABDM integration costs a hospital or health software company in 2026, route by route, with the figures that are publicly advertised and the ones that are not.
ABDM for HMIS vendors, built once for every customer
For companies that sell hospital information systems: add ABHA, HIP record sharing, HIU consent and HFR onboarding to your HMIS once, then roll it out to every hospital you serve, with a facility per site and every record attributed to it.
Price it for your hospitals
Start in the sandbox for nothing, or tell us how many facilities you run and we will price the group on one contract.