ABDMLink

What ABDMLink does

THE NATIONAL HEALTH EXCHANGE IS NOT CONNECTED TO THIS PRODUCT, and connecting it is not a setting: it needs enrolment in the NDHM sandbox and production certification, a facility identifier issued by the Health Facility Registry, and a signed data-sharing undertaking with the National Health Authority. What is built is everything that comes before that. Care contexts — a visit, a prescription, a report, a document — are prepared from records that already exist and are checked against the patient they claim to belong to before anything is written. Consent artefacts sit on the same purpose-bound, versioned consent engine every other consent in this product uses, so revoking one withdraws the consent behind it in the same breath. The health-information-provider callbacks are declared and validated, and nothing listens on them, because an endpoint shaped like an ABDM callback with no gateway behind it is an unauthenticated door that answers plausibly. Every attempt to reach the network is written down and refused.

How you actually use it

1. 1Read the Not connected card firstThe first card says this deployment is not enrolled with the national health exchange and lists what connecting it needs — sandbox enrolment, a facility identifier, a signed undertaking — none of which is a setting on this screen.
2. 2Prepare a care contextOn the Care contexts tab, give the patient id, choose a visit, a prescription, a report or a document that already exists and enter its id; the record is checked against that patient before anything is written, and one belonging to somebody else is refused.
3. 3Record a consent the patient gaveOn the Consents tab, write who asked, the purpose code and the purpose in words the patient agreed to, what it covers and until when; it lands on the same consent engine every other consent uses, and Revoke asks why and withdraws that consent with it.
4. 4Read the gateway ledgerTry to link records the attempt and its refusal; the Gateway ledger tab lists every attempt with its operation, its outcome and what came back.
5. 5Look at the callbacksThe Callbacks tab lists what a gateway would ask this hospital and what it would answer; nothing listens on them, and the screen says they have never been checked against the sandbox.

What it does not do

It sends nothing to the national health exchange, and it cannot pretend otherwise: a care context may only claim to be linked if it names the gateway that linked it, an ABDM artefact number may only exist if a gateway issued it, and the gateway ledger’s one permitted outcome is the refusal this build produces. There is no ABHA verification here either — HealthWallet records the address a patient is known by after they link it themselves.

Questions clinics ask