MedAppz has built the ABDM pieces: ABHA scan-and-share check-in, linking visits to a patient’s ABHA, and consented record exchange. It is not connected to the live ABDM gateway yet; that needs the National Health Authority’s onboarding.
Prepares care contexts (a visit, a prescription, a report, a document) from records that already exist, checked against the patient first.
Keeps ABDM consent artefacts on the same consent engine as every other consent, so revoking one withdraws it at once.
Built for scan and share: a patient scans your counter QR in their ABHA app, and ABHA Check-in Kiosk checks them in from the profile.
Built to fetch records from other facilities with a key made for that one request, kept sealed and erased on the date the consent sets.
Switching it on
What it takes
1Step 1MedAppz completes the NHA’s sandbox and production tests for the deployment.
2Step 2Your facility gets its Health Facility Registry identifier.
3Step 3Enter your HIP id in ABDM Consents.
4Step 4The readiness register in ABDM Records Exchange shows each step still open.
What it does not do yet
Nothing is sent to the national network today, no ABHA is verified, and no care context claims a link the gateway did not make. The connection is written to the published ABDM v3 specification and has not yet been run on the NHA sandbox.
It is built, and MedAppz switches it on for your deployment. MedAppz has built the ABDM pieces: ABHA scan-and-share check-in, linking visits to a patient’s ABHA, and consented record exchange. It is not connected to the live ABDM gateway yet; that needs the National Health Authority’s onboarding.
How do I switch on ABDM and ABHA?
MedAppz completes the NHA’s sandbox and production tests for the deployment. Your facility gets its Health Facility Registry identifier. Enter your HIP id in ABDM Consents. The readiness register in ABDM Records Exchange shows each step still open.
What does the ABDM and ABHA connection not do yet?
Nothing is sent to the national network today, no ABHA is verified, and no care context claims a link the gateway did not make. The connection is written to the published ABDM v3 specification and has not yet been run on the NHA sandbox.