What is ABHA? India's digital health ID and its role in group health insurance

ABHA (Ayushman Bharat Health Account) is a government-issued 14-digit digital health ID under the Ayushman Bharat Digital Mission (ABDM). It lets individuals link, access, and share their medical records on a consent basis across ABDM-enabled providers. It does not store records itself and is separate from insurance, though employers and insurers can build workflows around it.

What is ABHA?

ABHA stands for Ayushman Bharat Health Account, and it is the official digital health identity for citizens within India's national digital health ecosystem. In everyday terminology, you may see it referred to as an "ABHA number," an "ABHA ID," or an "ABHA health ID" - all describing the same identifier used as a digital health ID.

Technically, an ABHA number is a 14-digit unique health ID that identifies a person, authenticates them, and threads their health records across multiple systems. It is a government initiative under the Ayushman Bharat Digital Mission (ABDM), operated by the National Health Authority (NHA), which runs the core registry and issuance mechanisms.

While users initiate the creation of an ABHA through official government platforms or ABDM-enabled partners, the identifier itself is generated and maintained by the NHA and ABDM systems - it is not self-chosen like a username. So the most accurate way to describe it for 2026 is: a government-issued, 14-digit digital health ID, identified by a unique ABHA number, that citizens create through official channels.

How ABHA works

ABHA is best understood as an identifier and account within a federated digital system, not a single database holding your clinical files. The ABHA number identifies a person and threads their health records - only with their informed consent - across multiple systems and stakeholders.

This is an important distinction. Your health records are stored in Participating Health Information Providers (HIPs) - hospitals, diagnostic labs, and digital health apps - not "inside" the ABHA number itself. ABHA acts as a key that lets these systems link a record to your unique digital identity and exchange that record through ABDM registries and consent managers when you approve it.

In other words, ABHA enables consent-based linking, access, and sharing of health records across ABDM-enabled systems, rather than storing those records on its own.

What records can be linked or shared

The kinds of health information that can be linked or shared through ABHA include:

• Hospital visit records - admission notes, treatment details, and discharge summaries.
• Diagnostic reports - pathology results, radiology images and reports, and lab tests.
• Prescriptions and medication history - outpatient and e-prescriptions.
• Insurance and claims-related health data - where insurers and TPAs integrate as participants under ABDM.

This means you can link and manage documents such as diagnostic test reports and prescriptions for future reference, and access records from admission through treatment and discharge through ABDM-enabled systems.

Current limitations

Records can be linked or shared only when two conditions are met: the facility or app is integrated with ABDM and acts as a Health Information Provider, and the user has an ABHA and provides informed digital consent for that sharing session. Non-ABDM providers cannot automatically push structured records into the system. You can still receive paper or local digital records from them, but those won't appear in your ABHA-linked records unless an ABDM-enabled intermediary uploads them. There is also variation in the depth and completeness of data across states and facilities, with some larger centres further along in integration than smaller clinics.

ABHA vs group health insurance

ABHA is not an insurance product, and it does not replace or alter your group health insurance coverage. It does not replace your doctor, hospital, or insurance policy. Instead, it supports smoother healthcare experiences by reducing paperwork and improving access to health information. ABDM is positioned as a digital health infrastructure, not a financing or benefit scheme.

There is no official policy stating that group health insurance must be linked to ABHA, nor that claims require an ABHA. The relationship between the two is indirect and operational rather than mandated. Insurers, TPAs, and hospitals may integrate with ABDM to:

• Pull clinical documents digitally, with consent, during pre-authorisation and claims.
• Reduce manual paperwork.
• Improve fraud control and continuity of care.

For employers, this means ABHA can support group health insurance workflows by making medical documentation and continuity of care smoother - but only where insurers and hospitals are ABDM-enabled. The connection is ecosystem-driven, not a formal regulatory linkage between ABHA and group policies. Platforms like Plum that combine group insurance, claims support, and benefits management can help HR teams navigate these workflows as the digital health ecosystem matures.

Why employers may encourage ABHA creation

There is no regulation preventing employers from informing or encouraging employees to create ABHA IDs. Because ABHA registration is completely voluntary - with no legal or regulatory requirement to create one, and full access to healthcare, insurance, and treatment available without it - employers can position it as a convenience rather than an obligation.

Within those boundaries, employers can:

• Educate employees about the benefits of ABHA and ABDM.
• Encourage them to create an ABHA through official channels.
• Suggest using ABHA to ease claims documentation where the insurer or hospital is ABDM-enabled.

Privacy, consent, and compliance considerations

Given ABHA's design and India's data-protection norms, employers should clearly articulate the following:

1. Voluntariness with no employment linkage. Participation must be optional. Employment, performance, or benefits should never be contingent on creating or sharing an ABHA.
2. Purpose limitation. If ABHA numbers are collected to assist with claims support, specify exactly why, and avoid any use unrelated to health-benefits administration.
3. Data minimisation and secure storage. Collect only the ABHA identifier needed for integration - never full medical records - and store it securely.
4. Explicit, informed consent. Obtain consent before collecting ABHA numbers, sharing them with insurers or TPAs, or initiating any health-data access. Employees should understand that consent for ABHA-based data sharing always remains with them through ABDM consent managers.
5. No direct access to clinical content. Health data should flow between employee, provider, and insurer or TPA. Employers should only see claims-relevant summaries they are legally entitled to, never full clinical histories.
6. Education about misuse. Employees should be reminded that an ABHA must be created only with their informed consent, that they should never share OTPs casually, and that they should review the permissions they grant.

A clear message works well: "We encourage ABHA for your convenience, but it is optional, and you remain in full control of what gets shared."

How ABHA fits into ABDM

ABDM stands for the Ayushman Bharat Digital Mission - earlier known as the National Digital Health Mission (NDHM). It is the national digital health infrastructure designed to connect patients, providers, payers, and health platforms through interoperable digital building blocks.

The core components of ABDM include:

• ABHA (Ayushman Bharat Health Account) - the unique digital health identifier for citizens.
• Health Facility Registry (HFR) - a registry of hospitals, clinics, and labs.
• Healthcare Professionals Registry (HPR) - a registry of doctors and licensed professionals.
• Health Information Provider (HIP) and Health Information User (HIU) framework - defining who can send versus request data.
• Consent managers and gateways - the technical layer enabling consent-based, standardised exchange of health information.
• Personal Health Records (PHR) applications - apps where citizens view and manage their linked records using their ABHA.

ABHA forms the backbone of this mission by providing the unique, interoperable identifier required for linking and exchanging data across all of these components.

Is ABHA usable everywhere in India?

Conceptually, ABHA is designed as a pan-India digital health ID for every citizen. In practical terms, however, it functions fully - for digital record-sharing - only where ABDM is implemented. Records can be linked and fetched only from ABDM-enabled facilities and digital systems. At non-ABDM providers, you can still present your ABHA card or number, but your records won't automatically sync into your ABHA-linked PHR unless that provider later becomes ABDM-compliant and uploads the data. The accurate framing: ABHA is built for use across India, but digital record-sharing works only at ABDM-enabled or participating providers.

How to create an ABHA ID

Creating an ABHA is free and open to all Indian citizens. There is no fee, and no documents beyond what is already captured in your Aadhaar or collected at a hospital registration desk are generally required.

The most common creation routes are using your Aadhaar, using your mobile number, or having an ABDM-enabled hospital or clinic create one for you at registration. Here is a typical online flow:

1. Visit an official ABDM or ABHA portal or app - for example, the NHA ABDM site (abdm.gov.in).
2. Select "Create ABHA number", which will generate your 14-digit identifier.
3. Choose your identification method - Aadhaar-based (most common) or mobile-based.
4. Enter your Aadhaar or mobile number along with basic demographic details where prompted.
5. Verify via OTP sent to your Aadhaar-linked or provided mobile number.
6. Confirm your demographic details, which are usually prefilled from Aadhaar.
7. Create an ABHA address (optional but encouraged) - a username-style handle, like an email ID, that makes sharing records easier.
8. Receive your ABHA number and QR code, and download your digital card.

At ABDM-integrated hospitals, staff typically follow a similar flow within their hospital information system.

Privacy and security

ABHA is built around consent, user control, and encryption. Data is shared only after your approval, providers can view records only for a defined period, the systems are encrypted against unauthorised access, and you can revoke access at any time. User consent is required every time a personal health record is accessed, and ABDM's consent manager issues time-bound, purpose-specific consent artefacts that providers must honour. Every data exchange is digitally signed and logged, creating an audit trail.

Because ABHA is not mandatory, users can also opt out and request to erase their data. Through PHR apps or help desks, you can deactivate or delete your ABHA, unlink providers or records, and revoke previously granted consents. One nuance worth noting: deactivating or deleting your ABHA prevents future consent-based exchange using that ID, but it does not necessarily force hospitals to delete clinical data they hold in their own systems under their own legal obligations - it mainly affects ABDM-mediated linkages and access.

For employers and employees alike, the practical takeaway is that ABHA puts the individual in control: you decide which providers and apps can access your records and for how long, you can revoke consents and unlink records, and you can deactivate the account entirely. Educating employees on never sharing OTPs casually and on reviewing consent prompts remains essential.

FAQs

What is ABHA, and how is it different from health insurance?

ABHA is a 14-digit digital health ID under the Ayushman Bharat Digital Mission that lets you link and share your medical records on a consent basis. It is not insurance - it does not pay for treatment or replace your policy. Instead, it helps manage your health information across ABDM-enabled systems, while group health insurance covers your medical costs.

Is ABHA mandatory for employees or for using group health insurance?

No. ABHA is completely voluntary. There is no legal or regulatory requirement to create one, and you can access healthcare services, insurance, and treatment without it. Group health insurance claims do not require an ABHA.

Can employers encourage employees to create an ABHA?

Yes. Employers may educate and encourage employees to create an ABHA for convenience, especially to simplify claims documentation. However, it must remain optional, with explicit consent, clear purpose limitation, and no link to employment decisions.

How does ABHA work with ABDM and digital health records?

ABHA is the unique identifier at the core of ABDM, India's national digital health infrastructure. It threads your health records across ABDM-enabled hospitals, labs, and apps, allowing consent-based linking and sharing through registries and consent managers - without storing the records itself.

How can someone create an ABHA number?

Visit an official ABDM or ABHA portal or app, select "Create ABHA number," choose Aadhaar or mobile verification, enter your details, and verify via OTP. Confirm your demographic details, optionally create an ABHA address, and download your digital card. The process is free for all Indian citizens.

Talk To Sales