Patient Onboarding (ABDM)
GovernmentSpin up an ABHA, verify the citizen and link records — consent-first.
Why this bundle exists
Onboarding a patient under the Ayushman Bharat Digital Mission is a consent problem before it is a data problem. The patient owns the record, the platform does not, and every record exchange has to be governed by an explicit consent artefact with a defined scope and duration. Implementing that incorrectly is a compliance failure, not a bug — which is why health platforms tend to move slowly here.
This bundle assembles the compliant path. An ABHA health ID is created or verified, establishing the patient's national health identity. Aadhaar e-KYC confirms who they are. DigiLocker pulls health and identity documents directly from their issuers rather than as uploads. Aadhaar eSign captures consent as a cryptographically verifiable artefact. The result is a patient onboarded with a verified ABHA, linked documents and a consent trail that stands up to inspection.
What it replaces
- Local patient record numbers that do not travel between providers
- Repeat diagnostics because prior history was unavailable at the point of care
- Photocopied identity and insurance documents at the registration desk
- Consent captured as a tick box with no verifiable artefact behind it
- Manual record linkage between systems that do not share an identity
What you need in place
- Your ABDM participant position, confirmed during scoping
- A health record model that can be linked against an ABHA
- A consent journey meeting ABDM presentation requirements
- Clinical data governance covering retention and access
Integrations in this bundle
Industries that run this flow
Patient Onboarding (ABDM) — FAQs
How long does this bundle take to go live?
Typically two to three weeks, with ABDM participation scoping usually the gating item rather than the integration work.
Does Aeologic store patient data?
No. Record exchange is brokered under the ABDM consent framework and flows between the participants involved; we do not retain clinical payloads.
Why is Aadhaar eSign part of a health onboarding flow?
Because consent under ABDM needs to be verifiable rather than asserted. eSign produces a cryptographic artefact tied to the patient's authenticated identity.
Can patients revoke consent later?
Yes — consent under ABDM is scoped, time-bound and revocable, and the flow handles revocation rather than assuming consent is permanent.
Stop rebuilding India's digital plumbing
Ship the integration in days — talk to us today
Every connector in this repository is pre-built, tested and compliance-ready. Tell us what you're building and our engineers wire it into your product end-to-end, while your team stays focused on what makes you different. Save the months — and the budget — a from-scratch build would cost.