01What ABDM itself costs
Nothing. Registering on the sandbox, calling the APIs, applying for production credentials and being listed as a certified integrator are all free of charge from the National Health Authority. Two steps on the way to production are paid, but not to NHA: functional testing is done by an agency NHA has empanelled, which charges for its time, and the security audit that produces the Safe-to-Host certificate is done by a CERT-In or STQC empanelled auditor, who also charges.
So when a quotation for “ABDM integration” runs into lakhs, none of it is going to the government. It is paying for the work of building the integration, proving it, and then keeping it working as NHA changes things, which it does often.
02The five things you actually pay for
- Engineering. M1 is a few synchronous APIs with strict encryption rules. M2 and M3 are asynchronous: every request is answered later by a callback to a bridge you host, and the flows have to survive callbacks arriving early, late, twice or never. FHIR bundles have to be composed from your own clinical data. This is where months go.
- Certification. The empanelled agency runs NHA’s test-case sheets against your deployment. Cases you fail are re-tested; every round is time and a fee.
- Security audit. A web application security audit with findings closed and a Safe-to-Host certificate issued, then renewed on the auditor’s cycle.
- Hosting and operations. The bridge must be reachable from NHA’s gateway around the clock, with the callback token verified, the audit trail kept, and someone watching for the consent that never arrived.
- Keeping up. NHA replaced its v0.5 APIs with v3, changed the encryption used for Aadhaar and OTP fields, moved the registries to new hosts and revised the certification sheets. Each change is a small project, and there is one every few months.
The fifth item is the one that decides which route is cheaper. A build that costs little on day one and then sits still is out of date within a year, and out of certification soon after.
03Route 1: building in-house
Published guides for Indian hospitals put a custom ABDM integration at anywhere from a few lakh to ten lakh rupees, taking months, with the figure driven by how many milestones are in scope and how clean the clinical data is. Those figures line up with what the work involves: a small team for a quarter or two, then testing and audit.
The in-house route makes sense for a software company whose product is the HMIS itself, with enough hospitals to amortise the work and a team that will stay on it. It rarely makes sense for a single hospital, which ends up employing a team for something that is not its business.
Budget for it honestly: the build, the two paid certifications, hosting, and at least a few engineer-weeks a year for NHA’s changes.
04Route 2: an ABDM-ready HMIS
Cloud hospital software with ABDM built in is advertised in 2026 from about ₹999 a month for a small clinic, through ₹15,000 to ₹2.5 lakh a month for larger systems, with full hospital deployments quoted between ₹3 lakh and ₹50 lakh. The ABDM part is included, and the vendor carries certification.
The cost that does not appear on the price list is the change. Billing, OPD, IPD, pharmacy, laboratory and stores all move; historical records are migrated; every department is retrained; and reports the finance team relies on are rebuilt. For a hospital that is unhappy with its software anyway, this is the moment to move. For one whose software works, ABDM is a poor reason to replace it.
05Route 3: a connector
A connector is ABDM as a service: certified once, hosted once, and called from the software the hospital already runs. The HMIS sends a patient to the connector to create an ABHA, tells it when a visit is ready to link, and receives a webhook when a consent is granted or records arrive. The connector holds the bridge, the encryption, the callback handling and the registry flows, and updates them when NHA does.
The pricing model matters as much as the price. Some integrators advertise a one-time fee per hospital, from about ₹4,999. That covers the first integration; ask what covers the next v3 change, and who re-certifies. Swastik prices per hospital per month, ₹2,999 on Growth and ₹4,999 on Scale, and the subscription is what pays for the keeping-up. Every milestone is on every paid plan; the plans differ in how many facilities, applications and team members they carry and in the monthly call quota. The comparison page sets the routes side by side.
06Two-year arithmetic
Take one hospital and look two years out, because that is roughly one NHA version cycle.
- In-house: the build, two paid certifications, hosting for 24 months, and the engineering to follow NHA. Even at the low end of published figures this is several lakh before the first patient.
- New HMIS: 24 months of the new subscription plus the migration and retraining, against a system you may not have needed to replace.
- Connector: 24 months at ₹2,999 is ₹71,976 on Growth, or ₹59,980 on the yearly plan, with certification, hosting and every NHA change inside the price. On Scale it is ₹99,980 yearly.
For a group of hospitals the gap widens, because a connector is multi-tenant: the second hospital is another subscription, not another integration.
07What the incentive scheme pays back
NHA’s Digital Health Incentive Scheme pays facilities for ABHA-linked transactions above a base level. Under the November 2025 corrigendum the rate is ₹20 per eligible transaction for hospitals and ₹15 for laboratories, capped at one a day and five a month per ABHA, with the scheme extended in stages and subject to funds. At those rates, 150 eligible OPD transactions in a month pay for the Growth plan and 250 pay for Scale. A hospital that links visits as a matter of routine can find ABDM paying for itself. The guide to the scheme covers eligibility and claiming.
08Questions to ask any vendor
- Which ABDM API version does it speak today? If the answer is not v3, ask when.
- Which milestones are certified, by which agency, and when was the last functional test?
- Who pays for the next NHA change, and how long after NHA announces it does it reach me?
- Is anything charged per ABHA, per record, per consent or per API call beyond a quota?
- Does my HMIS keep the patient record, and can I export everything the vendor holds?
- Can I try it against the sandbox before paying, and how quickly?
- Does it register my facility in HFR and my doctors in HPR, or is that left to me?
- When NHA answers with its generic failure, what does the vendor show me?
The answers to the third and fourth questions are where most of the two-year difference lives.