OperationsLive · in the productRegister

ABDMConnect

Scan-and-share check-in and records from other facilities over ABDM, switched on with your NHA credentials.

Installs with ABDMLink, whose screen it works on · Offered in: India only.

Get ABDMConnect Open the appAvailable nowHow pricing works →

What it is

The parts of the national health exchange that ABDMLink does not do, on the same gateway client and ledger. Scan and share (M1): a patient scans the counter QR in their ABHA app, the gateway posts their profile, and the hospital answers with a token number; the profile is sealed, the ABHA identifiers hashed, and ABHAKiosk checks the patient in from it. Records from elsewhere (M3, the Health Information User side): a doctor asks for a patient’s records held at another facility with their ABHA address, the patient decides in their own ABHA app, a granted consent is fetched, the records are requested with an encryption key made for that request alone, and the documents that arrive are decrypted, kept sealed and erased on the date the consent sets. The readiness register lists the National Health Authority’s steps — facility registration, bridge URL, the sandbox tests for M1, M2 and M3, the security audit, production credentials, the undertaking — and each is a fact a person records with its reference. Until the MedAppz owner switches ABDM on with the NHA’s client credentials, nothing reaches the network: a request is kept and marked not sent, and the screen says so first. The wire formats follow the published ABDM v3 specification and have not yet been exercised against the NHA sandbox.

Who uses it: Built for: Every specialty
Reads: ABHA-linked care contexts, the HIP registration
Writes: Scan-and-share tokens, consent requests, received documents (sealed), readiness steps
Never: It does not certify the hospital with the NHA, create an ABHA, or decide what a consent covers — the patient decides in their ABHA app, and certification is the NHA’s, after its own tests.
Access: Only people whose role includes it — the clinic owner decides who
Your data: Full PHI. Hosted in Boston, United States. On uninstall: Tokens, requests, readiness steps and the gateway ledger are kept; received documents are erased on their consent’s date.

In the product

Who uses it: Operations manager — the demo profile it is best tried as
Where it opens: Compliance › ABDM Connect /abdm-connect
Permission: abdmconnect.read

Every operations app in the handbook →

How it works

Record the NHA stepsEach with its reference, never a claim.
Owner switches it onThe NHA’s client id and secret.
Patients scan and shareA token number, checked in at the kiosk.
Ask for outside recordsThe patient decides; erased on the date set.

Rules it keeps

What it does not do, by design. A listing with only benefits is an advertisement.

It does not certify the hospital with the NHA, create an ABHA, or decide what a consent covers — the patient decides in their ABHA app, and certification is the NHA’s, after its own tests.

AI in ABDMConnect

AskQuestions about what is on screen — “What needs attention in ABDMConnect today?” — answered with the records it read.

DraftSummaries and notes for the team, marked as drafts until a person signs.

Every answer shows its sources. Nothing AI writes is saved until a person accepts it.

See it on screen

ABDMConnect — ABDM Connect — Check patients in by ABHA scan and ask other hospitals for their records — 01ABDM Connect — Check patients in by ABHA scan and ask other hospitals for their recordsCaptured from the running demo clinic

01ABDM Connect — Check patients in by ABHA scan and ask other hospitals for their recordsCaptured from the running demo clinic

1 of 1

Connected to

Read out of the code, not the brochure: each app below is here because one service queries the other’s tables. Install either side and the hand-over is already wired.

Reads from · 2

HealthWallet Patient Registry

See the whole clinic →

Questions clinics ask

What does ABDMConnect do?

Scan-and-share check-in and records from other facilities over ABDM, switched on with your NHA credentials. The parts of the national health exchange that ABDMLink does not do, on the same gateway client and ledger. Scan and share (M1): a patient scans the counter QR in their ABHA app, the gateway posts their profile, and the hospital answers with a token number; the profile is sealed, the ABHA identifiers hashed, and ABHAKiosk checks the patient in from it. Records from elsewhere (M3, the Health Information User side): a doctor asks for a patient’s records held at another facility with their ABHA address, the patient decides in their own ABHA app, a granted consent is fetched, the records are requested with an encryption key made for that request alone, and the documents that arrive are decrypted, kept sealed and erased on the date the consent sets. The readiness register lists the National Health Authority’s steps — facility registration, bridge URL, the sandbox tests for M1, M2 and M3, the security audit, production credentials, the undertaking — and each is a fact a person records with its reference. Until the MedAppz owner switches ABDM on with the NHA’s client credentials, nothing reaches the network: a request is kept and marked not sent, and the screen says so first. The wire formats follow the published ABDM v3 specification and have not yet been exercised against the NHA sandbox.

What data does ABDMConnect read and write?

ABDMConnect reads ABHA-linked care contexts, the HIP registration and writes scan-and-share tokens, consent requests, received documents (sealed), readiness steps. Its data class is Full PHI. Every app works on the same patient record — nothing is copied into a silo.

What does ABDMConnect deliberately not do?

It does not certify the hospital with the NHA, create an ABHA, or decide what a consent covers — the patient decides in their ABHA app, and certification is the NHA’s, after its own tests.

What happens to our data if we uninstall ABDMConnect?

Tokens, requests, readiness steps and the gateway ledger are kept; received documents are erased on their consent’s date.

Is ABDMConnect available today?

Yes — ABDMConnect is live in clinics today. Set up your practice on MedAppz and install it from your dashboard.

Where is ABDMConnect offered?

ABDMConnect is offered in India only: it is built on that market's own systems and rules.

Want to see ABDMConnect running on your own patients?

Tell us what you run and we will show you this app inside a practice shaped like yours — or answer the question the page above did not.

More in Operations

All 97 →