Connect the identity
Create or connect an ABHA through an authorised flow and confirm the person and care context involved.
ABHA + ABDM workflows
ABHA-connected records,
with consent in view.
Support ABHA-linked record journeys with clear consent states, visible context and standards-aware exchange across participating systems.
The workflow
A connected health journey should still feel controlled by the individual.
The Ayushman Bharat Digital Mission is India’s standards-based digital health ecosystem. An Ayushman Bharat Health Account, or ABHA, is a unique 14-digit identifier that can help an individual link and share eligible records through ABDM-enabled personal health record workflows.
Doxyte is designed to bring identity, record discovery and consent states into the care workflow without treating an ABHA link as blanket permission. A participating provider can receive records only through a supported, authorised exchange after the individual reviews the request.
What this helps you do
01
Connect ABHA identity to supported registration and record journeys
02
Discover and link eligible records from participating facilities
03
Keep the purpose, record scope and duration of consent visible
04
Carry approved context into the next participating care interaction
How it works
A visible path from input to responsible action.
Each step keeps the source, the reviewer and the next decision clear.
Find eligible records
Discover records made available by participating health facilities and choose which care contexts to link.
Review the request
Show why information is requested, which record types are included and how long the consent remains valid.
Share with control
Complete the supported exchange only after consent, while keeping later consent-management actions visible.
Important context
Consent is specific, not assumed.
Available record types, provider participation and connection status vary by implementation. An ABHA-connected workflow does not automatically expose every linked record, and consent should remain reviewable and manageable by the individual.
Official ABDM resources
ABDM overviewOfficial overview of ABDM, ABHA and personal health record functions.Open official source ↗ABDM frequently asked questionsOfficial guidance on ABHA, record linking and consent management.Open official source ↗ABDM resources for citizensOfficial citizen information about ABHA and connected health records.Open official source ↗
Questions, answered
What to know before using this workflow.
What is the difference between ABHA and ABDM?
ABDM is the broader digital health ecosystem. ABHA is a unique identifier used within supported ABDM journeys to identify an individual and link eligible health records with informed consent.
Can a provider see every record linked to an ABHA?
No. ABDM describes consent-led sharing in which an individual can review the purpose, records and duration involved. The exact controls available depend on the participating PHR application and connected systems.
Can consent be withdrawn?
Official ABDM guidance states that previously granted consent can be managed and revoked through a supported personal health record application. Revocation does not undo information that was already lawfully shared during an earlier valid exchange.