ABDM for Functional Consultants

February 2026 · 18 min

What Is ABDM?

The Ayushman Bharat Digital Mission (ABDM) is India's national initiative to create a unified digital health ecosystem. Launched in 2021, it aims to:

1. Give every citizen a unique ABHA (Ayushman Bharat Health Account) number
2. Build a Health Information Exchange & Consent Manager (HIE-CM) so patients control who sees their records
3. Create registries -- Health Facility Registry (HFR), Health Professional Registry (HPR) -- so every hospital and doctor is verified
4. Enable the Unified Health Interface (UHI) for discovering and booking health services digitally

As a functional consultant, you are the bridge between the hospital and ABDM compliance. You configure the integration, train staff on ABHA verification, and ensure health records flow correctly.

ABHA -- The Patient Identity Layer

ABHA (Ayushman Bharat Health Account) is a 14-digit unique health ID assigned to every citizen. It replaces the earlier "Health ID" terminology.

FC Configuration Tasks:

• Enable ABDM integration toggle in Bio Ecko Settings > Integrations
• Map the abha_number field to the patient registration form
• Configure the front desk SOP for ABHA verification at walk-in
• Train registration staff on Aadhaar OTP vs manual-entry flows

Health Facility Registry (HFR) & Health Professional Registry (HPR)

Every hospital using ABDM must register on the Health Facility Registry and every doctor on the Health Professional Registry.

HFR Registration:

1. Hospital admin registers on facility.abdm.gov.in with NIN (National Identification Number)
2. Facility details -- name, type, ownership, services, geo-coordinates -- are verified
3. A unique Facility ID is issued, stored in Bio Ecko organizations.hfr_id
4. This ID appears on all digital health records shared via ABDM

HPR Registration:

1. Each doctor registers with their NMC registration number
2. A unique HPR ID is issued
3. Bio Ecko stores this in profiles.hpr_id for each doctor
4. The HPR ID is embedded in prescriptions and discharge summaries shared digitally

FC Checklist:

• Verify hospital HFR registration is complete before go-live
• Collect HPR IDs for all doctors and map them in Bio Ecko profiles
• Ensure NMC registration numbers are current and match HPR records

Consent Framework -- How Patient Data Flows

ABDM uses a consent-based model. No health record leaves a hospital without the patient's explicit digital consent.

The Consent Flow:

1. Consent Request -- A requesting entity (e.g., a new hospital) asks for records through the HIE-CM
2. Patient Notification -- The patient receives a consent request on their PHR (Personal Health Record) app
3. Grant / Deny -- Patient reviews the request (what data, which period, for how long) and grants or denies
4. Data Transfer -- If granted, the source hospital's HIP (Health Information Provider) encrypts and sends the record
5. Expiry -- Consent auto-expires after the agreed period; data must be purged

Key FC Point: Bio Ecko acts as both HIP (sharing its own records) and HIU (requesting records from other facilities). You must configure both roles during setup.

FHIR R4 Profiles Used in ABDM

ABDM mandates health records be shared as FHIR R4 bundles using India-specific profiles.

What the FC Must Know:

• You do not write FHIR JSON -- Bio Ecko's ABDM Gateway auto-generates it
• You must ensure source data is complete and coded (e.g., ICD-10 on every diagnosis, LOINC on lab tests)
• Incomplete source data = failed FHIR validation = record not shared
• During UAT, always test ABDM sharing with the ABDM Sandbox environment

Configuring ABDM in Bio Ecko -- Step by Step

1. Obtain Sandbox Credentials -- Register at sandbox.abdm.gov.in to get client ID + secret for testing
2. Enter Credentials -- In Bio Ecko, go to Settings > Integrations > ABDM and enter the sandbox credentials
3. Map HFR ID -- Enter the hospital's HFR facility ID in Organization Settings
4. Map HPR IDs -- For each doctor profile, add their HPR ID
5. Enable ABHA at Registration -- Toggle on "ABHA Verification" in Patient Registration settings
6. Configure Record Sharing -- Select which record types to share (prescriptions, lab reports, discharge summaries)
7. Test in Sandbox -- Create a test patient with sandbox ABHA, generate records, verify they appear in the ABDM sandbox PHR app
8. Switch to Production -- After UAT sign-off, replace sandbox credentials with production credentials from hiecm.abdm.gov.in

Common Pitfall: Never test with production ABHA numbers in sandbox mode -- the records won't route correctly.

Unified Health Interface (UHI)

UHI is ABDM's service discovery and booking layer -- think of it as "UPI for healthcare."

• Patients search for services (e.g., "cardiologist near me") through UHI-enabled apps
• The request reaches participating hospitals via the UHI Gateway
• The hospital responds with available slots, pricing, and teleconsultation options
• Patient books and pays digitally

Current Bio Ecko Support:

• Bio Ecko exposes appointment availability via the UHI-compatible API
• Teleconsultation slots are included when the Telemedicine module is active
• The FC must configure: department-wise slot availability, service pricing, and teleconsult eligibility

Note: UHI adoption is still early-stage (2025-26). Not all hospitals will enable it at go-live, but the FC should configure it as "ready to activate."

ABDM Compliance Checklist for Go-Live

Before any hospital goes live with ABDM integration, the FC must verify:

• HFR registration is complete and facility ID is stored in Bio Ecko
• All active doctors have HPR IDs mapped in their profiles
• ABHA verification is enabled at the front desk registration screen
• At least 3 record types are configured for sharing (prescription, lab, discharge)
• ICD-10 coding is enforced on all OPD/IPD diagnoses (required for FHIR validation)
• LOINC codes are mapped for the top 50 lab tests (covers 90% of volume)
• Sandbox testing is complete with end-to-end consent flow verified
• Production credentials are obtained and securely stored
• Front desk staff have been trained on ABHA verification SOP
• A patient-facing poster/notice about ABHA is displayed at the registration counter
• Consent denial handling is documented -- what happens when a patient denies a consent request

Common ABDM Issues & Troubleshooting

Notes

Related topics