What is ABHA?
ABHA stands for Ayushman Bharat Health Account. It's a 14-digit health ID (displayed as a format like 14-1234-5678-9012) that every citizen can create, usually linked to their Aadhaar or mobile number. Once created, a patient's ABHA ID becomes the anchor that connects every health record they generate, across every ABDM-registered facility they visit, for life.
How Do Patients Get an ABHA ID?
- Self-registering through the official ABHA mobile app or web portal using Aadhaar or mobile OTP verification.
- Creating one on the spot at a hospital or clinic's registration desk, where staff assist using ABDM-integrated software.
- Through a Personal Health Record (PHR) app that supports ABDM.
Why Should Hospitals Integrate ABHA Verification?
Verifying and linking a patient's ABHA at the point of registration is the single most common entry point into the ABDM ecosystem. It unlocks:
- Faster registration — existing demographic details can be pulled instead of re-typed.
- Continuity of care — previous visit history becomes accessible (with consent) even across different hospitals.
- Eligibility workflows for government health scheme integrations that require an ABHA-linked record.
- Reduced duplicate testing when lab reports are already linked to the patient's ABHA-linked record.
How ABHA Verification Works via API
In practice, integrating ABHA verification into your registration workflow involves a few consistent steps, all of which an ABDM connector automates:
- Patient provides their ABHA number or ABHA address (e.g.
name@abdm) at the front desk or via a self-check-in kiosk. - Your system calls the verification endpoint (see our API documentation for a sample request).
- The patient confirms via OTP, completing consent for that facility to link the visit.
- Your system receives verified demographic data and a confirmation the patient is now linked as a HIP-generated record for that visit.
Common ABHA Integration Mistakes to Avoid
- Skipping consent handling: Every data pull needs a matching, logged consent artefact — not just a one-time OTP.
- Hardcoding sandbox credentials: Sandbox and production ABHA environments use separate credentials; mixing them causes silent failures.
- Ignoring failed verifications gracefully: Patients without an ABHA ID yet should be offered on-the-spot creation, not blocked from registration.
Key Takeaways
- ABHA is the patient-level digital health ID underpinning all of ABDM.
- Hospitals integrate ABHA verification primarily during patient registration.
- A connector automates verification, consent logging and error handling so your team doesn't build this from scratch.
- Proper ABHA integration is usually the first milestone (M1) on the path to full ABDM compliance — see our ABDM integration process.