ComplianceLive · in the productRegister

ABDMLink

Care contexts and ABDM consent artefacts, ready for a gateway this deployment does not have.

Offered in: India only.

Get ABDMLink Open the appAvailable nowHow pricing works →

What it is

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.

Who uses it: Built for: Every specialty
Reads: The patient record, visits, prescriptions, reports and documents, consents
Writes: Care contexts, consent artefacts, the gateway ledger
Never: 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.
Access: Only people whose role includes it — the clinic owner decides who
Your data: Full PHI. Hosted in Boston, United States. On uninstall: All clinical data stays in the record.

How it works

Read 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.
Prepare 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.
Record 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.
Read 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.
Look 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.

Rules it keeps

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

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.

AI in ABDMLink

AskQuestions about what is on screen — “What needs attention in ABDMLink 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

ABDMLink — ABDM Link — Prepare ABDM care contexts and consents — the network is not connected — 01ABDM Link — Prepare ABDM care contexts and consents — the network is not connectedCaptured from the running demo clinic

01ABDM Link — Prepare ABDM care contexts and consents — the network is not connectedCaptured 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 · 6

CaseNotes ConsentVault HealthWallet LabBridge Patient Registry RxCanvas

Hands to · 1

ConsentVault

See the whole clinic →

Questions clinics ask

What does ABDMLink do?

Care contexts and ABDM consent artefacts, ready for a gateway this deployment does not have. 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.

What data does ABDMLink read and write?

ABDMLink reads the patient record, visits, prescriptions, reports and documents, consents and writes care contexts, consent artefacts, the gateway ledger. Its data class is Full PHI. Every app works on the same patient record — nothing is copied into a silo.

What does ABDMLink deliberately not do?

What happens to our data if we uninstall ABDMLink?

All clinical data stays in the record.

Is ABDMLink available today?

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

Where is ABDMLink offered?

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

Want to see ABDMLink 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 Compliance

All 154 →