The Ayushman Bharat Digital Mission (ABDM) uses the ABHA Number (Ayushman Bharat Health Account Number) as the primary unique digital health identifier for an individual.

Enquery Now

Connect with our team for quick support & guidance.

The ABHA Number is a 14-digit unique number that connects an individual to the ABDM digital health ecosystem. It can be used to link digital health records generated by participating healthcare facilities and systems to the individual’s digital health identity.

However, there is an important distinction between the ABHA Number, ABHA Address, and Personal Health Record (PHR).

In simple terms:

ABHA Number → identifies the individual

ABHA Address → digital address used in ABDM health-information exchange workflows

PHR → allows the individual to access and manage available health records

Understanding this distinction is important for patients, hospitals, health-tech companies, and developers implementing ABDM integration.

What Is the Unique Identifier Used by ABDM?

The primary unique identifier is the ABHA Number.

ABHA stands for Ayushman Bharat Health Account.

The National Health Authority describes the ABHA Number as a 14-digit unique number for each citizen that connects the individual to the national digital health ecosystem.

This means that when a healthcare facility generates an ABDM-enabled digital health record, the record can be linked to the patient’s ABHA identity.

For example:

Patient → ABHA Number → Digital Health Records

A patient’s digital records may include:

  • Consultation records
  • Prescriptions
  • Laboratory reports
  • Diagnostic reports
  • Discharge summaries
  • Vaccination records
  • Other eligible digital health information

The ABDM architecture is designed to enable these records to be linked and exchanged through interoperable systems and appropriate consent mechanisms.

What Is an ABHA Number?

An ABHA Number is a 14-digit unique identifier associated with an individual’s ABHA.

It provides a digital identity within the ABDM ecosystem.

For example, a person’s ABHA Number may look conceptually like:

12-3456-7890-1234

The actual number is assigned by the ABDM ecosystem and should not be confused with other identification numbers such as:

  • Aadhaar number
  • PAN
  • Passport number
  • Hospital registration number
  • Insurance policy number

The ABHA Number has a specific purpose: digital health identity within the ABDM ecosystem.

The official ABDM material describes ABHA as a digital account that can be used to access health services and related digital health services.

How Does ABDM Use the ABHA Number to Link Health Records?

The basic concept can be represented as:

Individual

↓

ABHA Number

↓

ABDM-enabled Healthcare Facility

↓

Digital Health Record

↓

Record linked to patient’s ABHA identity

↓

Available through supported PHR workflows

For example, suppose a patient visits a hospital.

The hospital generates:

Consultation + Prescription + Diagnostic Information

The ABDM-enabled system can associate the resulting digital health record with the patient’s ABHA identity.

Later, the patient may be able to access the available record through a supported Personal Health Record (PHR) application.

The ABDM’s Digital Health Incentive Scheme documentation explicitly refers to digital health records being generated through ABDM-enabled software and linked to the person’s ABHA/ABHA Address.

Is ABHA Number the Same as ABHA Address?

No.

This is one of the most important distinctions when explaining ABDM.

ABHA Number

The ABHA Number is the 14-digit unique identifier associated with the individual’s ABHA.

ABHA Address

The ABHA Address is a digital address used within ABDM workflows for health-information exchange.

It may look similar to an email address, for example:

name@abdm

Therefore:

TermWhat it means
ABHA Number14-digit unique digital health identifier
ABHA AddressDigital address used in ABDM health-information exchange workflows
PHRPersonal Health Record that allows individuals to access/manage health information
ABDMLarger digital health ecosystem and infrastructure

This distinction prevents a common SEO and technical misconception: the ABHA Address should not be described as the patient’s unique 14-digit health ID.

Why Does ABDM Need a Unique Identifier?

Healthcare information is often fragmented.

A patient may visit multiple healthcare organizations:

Clinic → Diagnostic Lab → Hospital → Specialist → Pharmacy

Each organization may maintain its own patient records.

Without a common digital identity, connecting records across participating systems becomes difficult.

A unique health identifier can provide a consistent identity reference within the ABDM ecosystem.

For example:

Without a common digital health identifier

Hospital A

→ Patient record A

Diagnostic Centre B

→ Patient record B

Specialist Clinic C

→ Patient record C

The records may exist independently.

With ABDM-enabled interoperability

Patient

↓

ABHA identity

↓

Hospital A record

Diagnostic Centre B record

Specialist Clinic C record

↓

Connected digital health ecosystem

The exact availability and exchange of records depends on whether the relevant healthcare providers and systems are participating and appropriately integrated.

How ABHA Helps Link Records Across Healthcare Facilities

One of the key citizen benefits described by the National Health Authority is the ability to link, store, and access health records created across different health facilities through PHR applications.

Consider a patient who visits three facilities.

Facility 1: General Physician

The patient receives:

  • Consultation
  • Prescription
  • Diagnosis

Facility 2: Diagnostic Laboratory

The patient receives:

  • Blood test
  • Imaging report

Facility 3: Specialist

The patient receives:

  • Specialist consultation
  • Treatment plan

If these systems are ABDM-enabled and the appropriate processes are followed, digital records can be associated with the patient’s ABHA identity and made available through supported health-information exchange workflows.

This can create a more connected longitudinal health record.

Does ABHA Automatically Collect All Medical Records?

No.

This is an important point that healthcare websites should explain accurately.

Creating an ABHA does not automatically digitize every medical record a person has ever created.

For a record to become available through ABDM-enabled workflows, several conditions may be involved:

  1. The record needs to exist in digital form or be digitized appropriately.
  2. The healthcare provider/system needs to participate in the relevant ABDM ecosystem.
  3. The record needs to be appropriately linked.
  4. The relevant ABDM workflows need to be implemented.
  5. Where applicable, the patient needs to provide the required consent for sharing/access.

Therefore, it would be inaccurate to tell patients:

“Create an ABHA and all your medical records will automatically appear.”

A better explanation is:

ABHA provides the digital health identity through which eligible digital health records can be linked and managed across participating ABDM-enabled systems.

Is Aadhaar the Unique Identifier Used by ABDM?

No.

This is another common misconception.

Aadhaar can be used as one of the mechanisms for identity verification or ABHA creation, but Aadhaar itself is not the ABDM digital health identifier.

The ABDM Health Data Management Policy describes mechanisms for creating a Health ID using Aadhaar or other permitted verification methods.

The resulting ABDM health identity is the ABHA Number.

Therefore:

Aadhaar → may support identity verification

ABHA Number → digital health identifier within ABDM

These should not be treated as the same identifier.

ABHA Number vs Aadhaar Number

FeatureABHA NumberAadhaar Number
PurposeDigital health identityGeneral identity
EcosystemABDMIndia’s broader identity system
Format14-digit ABHA Number12-digit Aadhaar number
Healthcare record linkingYes, within ABDM workflowsNot the primary ABDM health-record identifier
Healthcare-specificYesNo
Can be used for verification during ABHA creation—Yes, where supported

The distinction is especially important for healthcare organizations implementing ABDM.

Is the ABHA Number the Same as a Hospital Patient ID?

No.

A hospital may assign its own patient identifier.

For example:

Hospital Patient ID: HOSP-458921

This identifier belongs to the hospital’s internal system.

The patient’s ABHA Number belongs to the ABDM ecosystem.

A healthcare organization can therefore have:

Hospital Patient ID

ABHA Number

The hospital’s internal identifier can continue to be used for its own workflows, while the ABHA identity can support interoperability with the broader ABDM ecosystem.

This is an important concept for HMS, EMR and EHR integration.

ABHA Number and EMR/EHR Systems

For healthcare technology companies, one of the most important applications of the ABHA identifier is its relationship with Electronic Medical Record (EMR) and Electronic Health Record (EHR) systems.

A hospital may already have an internal patient database containing:

  • Patient demographics
  • Patient ID
  • Encounters
  • Diagnoses
  • Prescriptions
  • Laboratory results
  • Radiology reports
  • Discharge summaries

An ABDM-enabled system can introduce the ABHA identity into the relevant workflow.

Conceptually:

Hospital EMR

↓

Patient identification

↓

ABHA association

↓

Digital health record generation

↓

ABDM-enabled exchange

This allows the healthcare organization’s internal patient identity and the ABDM digital health identity to coexist.

How Does ABHA-Based Record Linking Work?

A simplified workflow can look like this:

Step 1: Patient has an ABHA

The patient has an ABHA Number.

Step 2: Patient visits an ABDM-enabled facility

The healthcare provider has an ABDM-enabled digital health system.

Step 3: Patient identity is established

The facility associates the patient with the appropriate ABDM identity.

Step 4: Healthcare service is provided

The patient receives consultation, diagnostic testing, treatment or another healthcare service.

Step 5: Digital record is generated

The provider’s system generates the relevant digital health record.

Step 6: Record is linked

The digital record can be linked to the patient’s ABHA/ABHA Address through supported ABDM workflows.

Step 7: Patient can access the record

The record can become available through supported PHR and health-information exchange workflows.

Step 8: Patient controls sharing

Where consent is required, the patient can authorize sharing with an appropriate healthcare provider.

This creates a more interoperable digital health journey.

Does ABHA Mean Every Doctor Can See the Patient’s Records?

No.

Having an ABHA Number does not mean that every doctor can automatically access all of the patient’s medical records.

ABDM is built around consent-based health information exchange.

The official ABDM citizen material specifically describes consent-based sharing of records with verified healthcare providers for a defined period.

Therefore, the relationship is better understood as:

ABHA identity

Digital health record

Participating systems

Appropriate consent

↓

Health information exchange

This is fundamentally different from creating a single centralized database where every doctor automatically sees every patient’s medical history.

What Role Does the ABHA Address Play?

The ABHA Address provides another important layer in the ABDM ecosystem.

It can be used as a digital address for health-information exchange and PHR-related workflows.

For example:

rahul@abdm

can function as a patient’s ABDM address.

The ABHA Number, meanwhile, remains the 14-digit unique identifier.

A useful analogy is:

ABHA Number = unique identity

ABHA Address = digital address

The two work together within ABDM workflows but should not be described as identical.

What Is PHR’s Relationship With the ABHA Number?

PHR stands for Personal Health Record.

A PHR is not an identifier.

It is the mechanism/application through which a person can manage and access their health information.

The ABDM citizen brochure describes PHR applications as enabling individuals to link, store and access health records created across different health facilities.

Therefore:

ABHA Number → identifies

ABHA Address → facilitates addressing/exchange

PHR → manages/accesses health records

This is a useful framework for understanding ABDM.

ABHA Number vs ABHA Address vs PHR

ComponentPrimary Purpose
ABHA NumberUnique digital health identifier
ABHA AddressDigital address for ABDM health-information exchange
PHRAccess and management of personal health records
HFRRegistry of health facilities
HPRRegistry of healthcare professionals
UHIInteroperable digital health service network
ABDMOverall digital health ecosystem

Why Is ABHA Important for Healthcare Interoperability?

Healthcare interoperability means that different healthcare systems can exchange and use information appropriately.

Imagine:

Hospital A uses EMR System A

Lab B uses LIS System B

Hospital C uses HIS System C

Patient uses PHR App D

If these systems operate completely independently, exchanging patient information is difficult.

ABDM provides common digital infrastructure and standards intended to enable interoperability.

The ABHA identity provides an important patient-level identity layer within this ecosystem.

Conceptually:

Patient

↓

ABHA

↓

Multiple participating healthcare systems

↓

Interoperable health information

This can support a more connected healthcare journey.

What Does “ABHA-Linked Health Record” Mean?

An ABHA-linked health record is a digital health record associated with the patient’s ABDM health identity through the applicable ABDM workflow.

The ABDM Digital Health Incentive Scheme documentation specifically describes transactions involving the generation of a digital health record through ABDM-enabled software and its linking to the person’s ABHA/ABHA Address.

This is important because simply creating an ABHA does not itself constitute the creation of a health record.

There are two different events:

ABHA creation

and

Digital health record generation and linking

They should not be treated as the same thing.

Example: Linking a Lab Report With ABHA

Suppose a patient visits an ABDM-enabled diagnostic centre.

Patient

Has an ABHA Number.

Diagnostic centre

Generates a digital blood test report.

ABDM-enabled software

Associates the record with the patient’s appropriate ABDM identity.

Patient

Can access the available record through a supported PHR workflow.

Future consultation

The patient may be able to share the relevant report with a healthcare provider through an appropriate consent-based mechanism.

This is the practical value of having a common digital health identity.

Why Is This Important for Hospitals and Health-Tech Companies?

For healthcare technology companies, the ABHA identifier is more than a patient-facing concept.

It has architectural implications.

An EMR, EHR, HIS, LIS or other healthcare application participating in ABDM may need to support workflows around:

  • Patient identity
  • ABHA association
  • Health record generation
  • Health record linking
  • Consent
  • Health-information exchange
  • Record discovery
  • Record retrieval
  • Data security
  • Interoperability standards

A healthcare organization therefore needs to think beyond simply adding an “ABHA field” to its patient database.

A successful ABDM integration requires appropriate workflows, APIs, data standards, identity handling, consent mechanisms and security controls.

What Unique Identifier Does ABDM Use? Simple Answer

If you need the answer in one sentence:

ABDM uses the 14-digit ABHA Number (Ayushman Bharat Health Account Number) as the individual’s unique digital health identifier, while ABHA Address is used as a digital address in relevant health-information exchange workflows.

This distinction is essential.

Remember:

ABHA Number = unique identifier

ABHA Address = digital address

PHR = personal health record

ABDM = digital health ecosystem

Conclusion

The ABHA Number is the key unique digital health identifier used within ABDM.

Its purpose is to provide an identity layer through which an individual’s digital health records and services can be connected within the ABDM ecosystem.

But ABHA should not be viewed in isolation.

A more accurate model is:

ABHA Number

→ identifies the individual

ABHA Address

→ provides a digital address for relevant ABDM exchange workflows

Digital Health Records

→ contain the individual’s healthcare information

PHR

→ enables access and management of available records

Consent

→ supports controlled sharing of health information

ABDM

→ provides the broader digital health ecosystem and interoperability infrastructure

For patients, this can mean a more connected digital healthcare experience. For hospitals and health-tech companies, it means that patient identity, health records, interoperability, consent and security need to work together.

That is the real significance of the ABHA identifier in India’s digital health ecosystem.

Frequently Asked Questions

What identifier is used in ABDM to link health records?

The primary identifier is the 14-digit ABHA Number, which connects an individual to the ABDM digital health ecosystem. ABDM documentation also refers to linking digital health records to an individual’s ABHA/ABHA Address.

Is ABHA Number the same as Health ID?

The terminology evolved from Health ID to ABHA Number under ABDM. Current ABDM materials use the term ABHA Number.

Is ABHA Number the same as Aadhaar?

No. Aadhaar can be used for identity verification in supported ABHA creation processes, but the ABHA Number is the digital health identifier within ABDM.

Is ABHA Address the unique identifier?

The ABHA Number is the 14-digit unique number. The ABHA Address is a digital address used in ABDM health-information exchange workflows.

Can ABHA link health records from different hospitals?

ABDM is designed to support linking and accessing digital health records generated across participating healthcare facilities through PHR and interoperability workflows.

Does creating ABHA automatically link all old medical records?

No. Existing records need to be available through participating systems and appropriately linked. Creating an ABHA alone does not automatically digitize or import every historical medical record.

Can doctors access all records using ABHA?

No. ABHA does not provide unrestricted automatic access to all patient records. ABDM supports consent-based sharing of health information with appropriate healthcare providers.

What is the difference between ABHA and PHR?

ABHA provides the individual’s digital health identity, while a PHR application enables the individual to access and manage available personal health records.

Why is a unique identifier important in healthcare interoperability?

A consistent digital health identity helps participating systems associate health information with the correct individual, making interoperable record exchange more practical while supporting patient-centric digital health workflows.