What ABHA-Ready Means
Your clinic can create or verify a patient's ABHA at the desk, record consent, and link the visit's documents so the patient can access them and, on consent, share them with other providers.
Step 1: Registries
- Register the clinic in the Health Facility Registry (HFR).
- Create each doctor's profile in the Healthcare Professionals Registry (HPR).
- Keep the login credentials and facility ID somewhere your software admin can reach.
Step 2: Software Capability
Confirm with your vendor that the software can:
- Create an ABHA using Aadhaar or mobile OTP, and verify an existing ABHA.
- Capture and store consent artefacts with timestamps.
- Link records (prescriptions, reports, discharge summaries) to the ABHA via the exchange.
- Handle a patient withdrawing consent.
If it cannot yet, get a committed timeline.
Step 3: Front-Desk Workflow
- Add an ABHA field to registration.
- Script the ask: explain what ABHA is, offer to create one, take consent.
- Decide the fallback when a patient declines or has no ID document.
Step 4: Clinical Workflow
- Ensure prescriptions and reports are generated in a linkable digital format.
- Set which document types are linked automatically after each visit.
Step 5: Consent and Privacy
- Store consent with purpose, scope and expiry.
- Train staff that fetching records needs a valid consent for that purpose.
- Log every record request and share.
Step 6: Pilot, Then Scale
Run ABHA capture for one week at one desk. Fix the script and the fallback. Then extend to all registration points and start linking records for every willing patient.