Get started
ABDM & ABHA · India

Ready for the national network. Honest that it is not plugged in.

Everything that comes before the Ayushman Bharat Digital Mission gateway is built: care contexts prepared from real records, consents on the same engine every other consent uses, and a ledger that refuses to pretend. The connection that carries them — scan-and-share check-in and records from other facilities — is built to ABDM’s published specification and waits for the NHA’s credentials and certification.

Today

MedAppz is not connected to the ABDM gateway today. Nothing is sent to the national network, no ABHA is verified, and a care context never claims a link that no gateway made. The connection is built to the published ABDM v3 specification and has not yet been tested on the NHA sandbox; switching it on needs the NHA’s client credentials, its certification tests, and a Health Facility Registry identifier. This is for clinics in India only.

  • 6● live in clinics
How it works

What works today, and what does not yet

The listing behind each tile says what it does and, just as plainly, what it does not.

  1. Care contexts, preparedA visit, a prescription, a report or a document, prepared from the record and checked against the patient it claims to belong to.
    ● live in clinicsABDMLink →
  2. Consent on one engineABDM consent artefacts sit on the same versioned consent engine as every other consent, so revoking one withdraws the consent behind it.
    ● live in clinicsConsentVault →
  3. The gateway connectionScan-and-share check-in and records asked for from other facilities, built to ABDM’s published specification and switched on with the NHA’s credentials.
    ● live in clinicsABDMConnect →
  4. ABHA at the front deskA check-in tablet: scan your ABHA once the hospital is connected, or type your phone today, and your appointment checks you in.
    ● live in clinicsABHAKiosk →
AI in every app

It drafts and suggests. A person decides.

Meet medappz AI
Shows its sourcesClinical and financial answers are grounded in your own records, and name the ones they read.
Drafts, never filesA named person accepts or discards every draft. The model never signs.
You can turn it offOne setting per organisation: off, redacted or full. Off keeps the manual path.
Redacted before it leavesBy default the patient’s name, number and contact details are taken out of what the model sees.
The contract

What ABDMLink promises

Every app in the store states what it reads, what it writes and what it will never do. This is its listing, word for word.

● live in clinicsABDMLink →
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. There is no ABHA verification here either — HealthWallet records the address a patient is known by after they link it themselves.
Your data
Full PHI. All clinical data stays in the record.
The apps

The apps behind it

Every badge is read from the listing it links to.

Live today

ABDMLinkCare contexts and ABDM consent artefacts, ready for a gateway this deployment does not have.ConsentVaultDPDP consent, proven at the point of use.HealthWalletThe records this clinic holds, shared by the patient — a travelling record for a worker who moves for work, and an emergency card showing only what the patient chose.FHIRBridgeFHIR R4 in and out, mapped in the open and every exchange logged.ABDMConnectScan-and-share check-in and records from other facilities over ABDM, switched on with your NHA credentials.ABHAKioskA check-in tablet: scan your ABHA or type your phone, and today's appointment checks you in.

Offered in some markets only: ABDMLink (India) · ABDMConnect (India) · ABHAKiosk (India).

Hear when the gateway is live

Leave a name and number. We will call when the certified connection opens, starting with the clinics already on MedAppz.

We use your name, phone number and clinic name for one thing: to answer this enquiry about MedAppz. It is stored on our own server, in the single region our trust centre names, and it is not sold or passed to anyone else.

Email us

You can withdraw either at any time: write to hello@medappz.com, or tell whoever calls you, and we will delete what you gave us.

Questions, answered

What works today, and what does not yet?
MedAppz is not connected to the ABDM gateway today. Nothing is sent to the national network, no ABHA is verified, and a care context never claims a link that no gateway made. The connection is built to the published ABDM v3 specification and has not yet been tested on the NHA sandbox; switching it on needs the NHA’s client credentials, its certification tests, and a Health Facility Registry identifier. This is for clinics in India only.
Which apps are behind it?
Live in clinics: ABDMLink, ConsentVault, HealthWallet, FHIRBridge, ABDMConnect, ABHAKiosk. Each listing says what the app does and what it does not.
How do I get it?
It cannot be bought or installed yet. Leave a name and number. We will call when the certified connection opens, starting with the clinics already on MedAppz.
Does the AI decide anything?
No. It drafts and suggests from the records on your screen; a named person accepts or discards every draft, and one setting per organisation — off, redacted or full — decides what reaches the model.

See the live half working

Everything marked live runs in the demo practice right now, with invented patients in it. Or set up your own practice in about a minute.