ABHA identity in Contacts
Open one Contact to view its masked ABHA status. Authorized administrators and care coordinators can complete a verified link workflow. Clinicians receive a read-only masked view.
WorkspaceAvailable
ABHA and ABDM workflows
ABHA and ABDM actions now live where staff already work. Identity is managed from a Contact, Scan and Share arrivals are reviewed from Clinic Appointments, and clinical exchange is available on the assigned clinician's appointment detail.
What you can do here
Scan and Share in Appointments
Operational staff review pending arrivals in Clinic Appointments and deliberately match each arrival to an exact Contact and optional appointment.
Clinical exchange in appointment details
The assigned clinician can manage care contexts, consent-bound exchange, and external records from the exact appointment and Encounter. GCC clinical records remain the source of truth.
Follow these steps
Continue an ABDM task
- Use Contacts to verify or review a patient's ABHA link.
- Use Clinic Appointments to review Scan and Share arrivals.
- Open an eligible appointment detail to work with care contexts, consents, transfers, and external records.
Helpful habits
- Never copy Aadhaar, OTP, full ABHA, consent artefacts, encryption keys, or clinical payloads into support tickets or screenshots.
- Treat requested consent as pending and a queued operation as incomplete until the verified callback or terminal state arrives.
- Use the original GCC clinical record for corrections. ABDM projections never replace clinical truth.
Tips
- ABDM remains voluntary and never blocks registration, booking, treatment, billing, or access to GCC records.
- The platform team manages facility registry identifiers and release readiness centrally.