For HMIS, EMR and LIS Product teams

Make your hospital management system ABDM compliant

You already have a hospital management system that works. ABDM compliance should be an addition to it, not a rewrite of it.

Start with the sandbox Discuss your product

01 The requirement

What ABDM compliance means for an HMIS

Four things your product has to be able to do. Everything else is protocol.

At intake: ABHA at registration

Create or verify an ABHA number at the OPD counter, from Aadhaar or a mobile OTP, and store the ABHA address against your patient record.
Outbound: Share what you produce

OP consultation notes, prescriptions, diagnostic reports, discharge summaries and immunisation records — published as care contexts the patient can see and consent to share.
Inbound: Fetch history with consent

Request records another provider holds, so a clinician sees a real history rather than whatever the patient remembers to mention.
Evidence: Prove it in an audit

Every ABDM call, callback and consent decision recorded with a correlation id you can trace end to end.

02 The division of labour

What you do not have to build

These five are where in-house ABDM projects lose their quarters, and where audits are failed.

Your product keeps Yours

The clinical record. Patients, encounters, orders, results — your schema, your database.
The workflow. How a clinician actually works at the counter and on the ward.
The identity of the product. Nothing here appears to your users.
The patient MRN. Your own reference stays authoritative; the connector maps it.

The connector absorbs Ours

FHIR R4 bundles. Send flat JSON; the NRCeS-profiled bundle is assembled and validated before it goes anywhere.
Fidelius encryption. Curve25519 key exchange and AES-256-GCM sealing, fresh per transfer.
The callback listener. A public endpoint that verifies ABDM’s signed tokens against their JWKS, deduplicates, correlates and retries.
Token lifecycle. Gateway session tokens, refresh, and the per-request headers ABDM expects.
Consent enforcement. Filtering releases by date range, HI type and revocation — the thing audits fail on.

03How it connects to your stack

REST over HTTPS with a bearer token, and signed webhooks back. There is no SDK you are forced to adopt and no agent to install — if your product can make an HTTPS request, it can integrate. That holds whether the product is a ten-year-old .NET desktop application or a three-month-old React front end.

04Multi-facility from the start

A hospital group with eight sites needs eight HFR identities, not one. The connector treats the facility as a first-class object: records are attributed to the facility that produced them, consent is scoped to it, and one API key can reach all of them.

That matters at audit time as much as at integration time. A record released under a consent artefact has to name the facility that holds it, and a group that registered one identity for eight buildings cannot produce that evidence afterwards.

05If you sell software to hospitals

Add ABDM once and give it to every hospital you sell to. The platform is multi-tenant by design: each customer keeps isolated credentials, facilities and audit trail, and no endpoint returns across tenants. Your customers get compliance as a feature of your product rather than a project of their own.

Get sandbox keys free Read the integration guide

Try it against your own data model

Sandbox credentials are issued on signup. Map one patient, link one care context, and see the webhook arrive.

Create an account Talk to us

FAQ Common questions

Frequently asked questions

How do I integrate a hospital management system with ABDM?

You connect your HMS to an ABDM connector over REST instead of building the gateway yourself. The connector handles ABHA creation, HFR identity, care-context linking, consent and the FHIR R4 bundles, and calls your system back over signed webhooks. Your HMS keeps its own patient record and data model.

Can I add ABHA to an existing HMS without replacing it?

Yes. Ayushman Bharat ABHA enrolment and verification are added beside your existing registration screen as API calls. Nothing is installed on the hospital network and no SDK is required — any language that can make an HTTPS request will do.

What is an ABDM connector?

An ABDM connector is middleware that sits between your hospital management system and the national ABDM gateway. It translates your data model into the FHIR R4 profiles ABDM expects, holds the ABDM credentials and callbacks, and gives your product one stable API instead of four milestones of protocol.

Does an HMS have to be ABDM certified?

The facility needs an HFR identity, and the software has to pass ABDM's milestone certification for the flows it uses. Production access additionally requires a Web Application Security Assessment from a CERT-In empanelled auditor.