Create or link the patient's ABHA at registration, share records with their consent through the national health exchange, and receive records from other providers. Coming in Release 2.
The Ayushman Bharat Digital Mission asks every provider to create ABHA IDs, keep records shareable and honour patient consent. The rules are detailed and the sandbox is slow.
A separate portal, a separate login, and the number copied into the file. It is done for some patients and forgotten for most.
Sharing a record without a valid consent artefact is not allowed. Doing it right needs the whole consent flow, not a checkbox.
A patient treated in another hospital brings a bag of paper. The exchange could bring the records, if the hospital were connected.
ABHA at the desk, consent requests the patient approves on their phone, records shared as FHIR bundles from the signed notes Vaidyah already holds.
Create a new ABHA with Aadhaar or mobile, or link an existing one, from the same registration screen. The patient can also scan a QR at the desk to share their profile.
Consent requests go to the patient's ABHA app; approved consents are stored as artefacts; sharing stops when they expire or are revoked.
Signed notes, prescriptions and reports are shared as standard bundles. Records from other providers appear in the patient's timeline.
Release 2. The parts of the OPD it depends on, signed notes and consent at registration, are already in place.
The ABHA field on the registration screen creates or verifies the number in seconds. The QR at the desk lets the patient share their ABHA profile and skip the form.
The doctor asks for records; the patient approves on their phone; the records arrive in the timeline. The hospital's own records are shared the same way.
External records sit in the same timeline as the hospital's own, marked with their source, and count towards the doctor's view of the patient.
The hospital and its doctors are registered once and the IDs flow into every record shared.
Every share is backed by a consent artefact, kept with the record, as the mission's audits require.
Because the notes are structured and signed, the bundles are produced without extra typing.
Certified in the ABDM sandbox before any real record is shared.
ABHA created or linked in the registration screen, nothing separate to remember.
A patient's history from other providers, with consent, before the consultation.
Their ABHA, their consent, their records, on their phone.
Compliance with the mission's milestones without a separate project.
Release 2, after the OPD, scribe and billing are running in the first hospitals. Registration already has the ABHA field; the exchange connection follows.
No. ABHA is optional at registration. Patients without one are registered by mobile number as usual.
No. Records leave the hospital only against a consent artefact approved by the patient, and only to the provider named in it.
We will show you what the OPD already does today and what the exchange adds in Release 2.
Request a demo