Front officeLive · in the productPatient-facing

ABHAKiosk

A check-in tablet: scan your ABHA or type your phone, and today's appointment checks you in.

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

Get ABHAKiosk Open the appAvailable nowHow pricing works →

What it is

A tablet at the entrance that a front-desk login opens in kiosk mode. A patient with an ABHA scans the counter’s QR in their ABHA app; ABDM’s scan and share sends their profile to the hospital (through ABDMConnect), the app shows a token number, and the patient taps it on the kiosk: if the profile matches exactly one patient here with an appointment today, they are checked in — the same check-in the desk does, opening the visit and issuing the queue token. The kiosk then asks whether today’s visit may be linked to their ABHA; a yes prepares the visit in ABDMLink, once it has started, for the gateway to link; a no is kept as a no. A patient without an ABHA types their phone number and year of birth instead, and is checked in only when exactly one patient with an appointment today matches. The kiosk faces the waiting room, so it shows initials, a time and a doctor’s calendar — never a full name or a phone number — and a search that finds nothing writes nothing. Scanning works once the MedAppz owner connects ABDM with the NHA’s credentials; the phone way works from the first day.

Who uses it: Built for: Every specialty
Reads: ABHA scan-and-share profiles, today’s appointments
Writes: Kiosk check-ins, the patient’s answer on linking, ABDMLink care contexts (on a yes)
Never: It does not create or pull an ABHA record, and it never links a visit without the patient’s yes on the kiosk — a walk-in with no ABHA still checks in by phone, and anyone it cannot match is sent to the desk.
Access: Only people whose role includes it — the clinic owner decides who
Your data: PHI-lite. Hosted in Boston, United States. On uninstall: Counters and kiosk check-ins are kept; the visits it opened are ordinary visits.

In the product

Who uses it: Front desk — the demo profile it is best tried as
Where it opens: Operations › ABHA kiosk /abha-kiosk
Permission: abhakiosk.read

Every front office app in the handbook →

How it works

Scan or typeThe ABHA app’s QR, or phone and birth year.
One match, todayAnything else goes to the desk.
Checked inThe desk’s own check-in and queue token.
Link if they say yesOnce ABDM is connected by the owner.

Rules it keeps

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

It does not create or pull an ABHA record, and it never links a visit without the patient’s yes on the kiosk — a walk-in with no ABHA still checks in by phone, and anyone it cannot match is sent to the desk.

AI in ABHAKiosk

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

ABHAKiosk — ABHA kiosk — Let patients check themselves in at the entrance by ABHA scan or phone — 01ABHA kiosk — Let patients check themselves in at the entrance by ABHA scan or phoneCaptured from the running demo clinic

01ABHA kiosk — Let patients check themselves in at the entrance by ABHA scan or phoneCaptured 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 · 3

CaseNotes Patient Registry SlotGrid

See the whole clinic →

Questions clinics ask

What does ABHAKiosk do?

A check-in tablet: scan your ABHA or type your phone, and today's appointment checks you in. A tablet at the entrance that a front-desk login opens in kiosk mode. A patient with an ABHA scans the counter’s QR in their ABHA app; ABDM’s scan and share sends their profile to the hospital (through ABDMConnect), the app shows a token number, and the patient taps it on the kiosk: if the profile matches exactly one patient here with an appointment today, they are checked in — the same check-in the desk does, opening the visit and issuing the queue token. The kiosk then asks whether today’s visit may be linked to their ABHA; a yes prepares the visit in ABDMLink, once it has started, for the gateway to link; a no is kept as a no. A patient without an ABHA types their phone number and year of birth instead, and is checked in only when exactly one patient with an appointment today matches. The kiosk faces the waiting room, so it shows initials, a time and a doctor’s calendar — never a full name or a phone number — and a search that finds nothing writes nothing. Scanning works once the MedAppz owner connects ABDM with the NHA’s credentials; the phone way works from the first day.

What data does ABHAKiosk read and write?

ABHAKiosk reads ABHA scan-and-share profiles, today’s appointments and writes kiosk check-ins, the patient’s answer on linking, ABDMLink care contexts (on a yes). Its data class is PHI-lite. Every app works on the same patient record — nothing is copied into a silo.

What does ABHAKiosk deliberately not do?

What happens to our data if we uninstall ABHAKiosk?

Counters and kiosk check-ins are kept; the visits it opened are ordinary visits.

Is ABHAKiosk available today?

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

Where is ABHAKiosk offered?

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

Want to see ABHAKiosk 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 Front office

All 17 →