ABDM & NHCX readiness

Interoperability readiness for India's digital health ecosystem

AIpath HealthTech by AIpath DigiNext Private Limited. Our ABDM (M1–M3) and NHCX integrations are fully developed. Our application to the National Health Authority (NHA) for certification is in progress.

Contact our technical team

Status

Integration and certification status

Last updated: October 2026

Developed · Certification in progress

ABDM Milestone M1

ABHA creation and verification, ABHA linking, and Scan & Share registration

Developed · Certification in progress

ABDM Milestone M2

Health Information Provider (HIP): care-context linking and consent-based sharing of health records

Developed · Certification in progress

ABDM Milestone M3

Health Information User (HIU): consent requests and retrieval of health records from other facilities

Developed · Onboarding in progress

NHCX integration

Coverage eligibility, pre-authorisation, claims, communication requests and payment notices

We will update this page as each milestone is cleared by the National Health Authority. Certification milestones are not a government endorsement of any product.

Ayushman Bharat Digital Mission (ABDM)

Consent-based health record exchange

Built as both a Health Information Provider (HIP) and a Health Information User (HIU), integrated with the ABDM gateway, ABHA, the Health Facility Registry (HFR) and the Healthcare Professionals Registry (HPR).

ABDM consent-based health record exchange

Requesting facilityHIU · AIpath HealthTech

ABDM gatewayConsent manager

PatientABHA / PHR app

Record-holding facilityHIP · AIpath HealthTech

1Consent request
Requesting facility → ABDM gateway: Doctor requests the patient’s records for a stated purpose and date range.
2Approval prompt
ABDM gateway → Patient: Patient reviews the purpose, record types, date range and expiry in their ABHA app.
3Consent granted
Patient → ABDM gateway: Patient approves (or denies). Consent can be revoked at any time.
4Consent artefact
ABDM gateway → Record-holding facility: The record-holding facility receives the signed consent artefact.
5Encrypted FHIR records
Record-holding facility → Requesting facility: Only the consented records are sent, encrypted end to end, until consent expires.

AIpath HealthTech supports both roles: sharing records as a HIP and requesting them as a HIU.

ABDM capabilities

ABHA creation, verification and linking where enabled
QR-based Scan & Share registration
HFR and HPR integration capabilities
Health Information Provider (HIP) workflows
Health Information User (HIU) workflows
Consent-based health record exchange
FHIR-based health record mapping
Integration status and error monitoring

Patient rights we uphold

Consent first

Records are shared only after the patient approves a specific purpose, date range and expiry in their ABHA app.

Revoke any time

Patients can withdraw consent at any time; access ends when consent is revoked or expires.

Transparency

Every access to a patient record is logged with who, when and why.

Data minimisation

Only the records covered by the consent are shared, encrypted end to end.

Grievance redressal

A designated Grievance Officer handles privacy and data-protection concerns.

National Health Claims Exchange (NHCX)

Standardised digital claims between providers and payers

NHCX is India’s National Health Claims Exchange, designed to standardise digital health-claim information exchange among participating providers, payers, beneficiaries and TPAs. NHCX participation has its own onboarding and integration requirements.

NHCX digital claims exchange

HospitalProvider · AIpath HealthTech

NHCXNational Health Claims Exchange

Insurer / TPAPayer

1Coverage eligibility
Hospital → Insurer / TPA: Verify the patient’s policy and coverage at admission.
2Pre-authorisation
Hospital → Insurer / TPA: Request approval with clinical documents attached as a FHIR bundle.
3Communication request
Insurer / TPA → Hospital: Payer raises queries or asks for additional documents.
4Claim submission
Hospital → Insurer / TPA: Structured claim prepared from the patient’s bill and records.
5Payment notice
Insurer / TPA → Hospital: Settlement details returned and reconciled against the bill.

All messages pass through NHCX using the HCX protocol, subject to supported workflows and participant onboarding.

Insurance eligibility and policy details
Pre-authorisation workflow support
Claim preparation and submission
Document and query management
Claim status and response tracking
Reconciliation and settlement visibility
NHCX integration capabilities, subject to supported workflows and onboarding

Standards

Health data standards used

Standard	How it is used
FHIR R4	Health records structured to the NRCeS FHIR Implementation Guide for ABDM
SNOMED CT	Clinical terminology for diagnoses, findings and procedures
LOINC	Identification of laboratory tests and observations
ICD-10	Diagnosis classification for records and insurance claims
HCX protocol	Health Claims Exchange specification used by NHCX
ABDM APIs	ABDM gateway, ABHA, HFR, HPR and consent manager integration

Architecture

How the platform fits together

Channels

WebMobile appTabletWhatsAppAI assistant

Workspaces

DoctorNursingPatientFront deskVisitor & caregiverPharmacy, lab, billing & admin teams

Platform core

HMISEMR / EHRLIS & RISPharmacyFinanceERPCommand centre AI copilot · automation · intelligence · clinical assistance

Integrations

ABDM & ABHANHCXFHIR APIsLab analysersPACS / DICOMWebhooks

Secure cloud

AWS or Azure, India regionsEncryption & key vaultRBAC & MFAAudit & monitoringBackup & DR

One patient record, one user directory and one data layer across every layer.

Data protection

Health data protected by design

Health data is hosted in Indian cloud regions on AWS or Microsoft Azure, encrypted in transit and at rest, and accessible only through role-based, MFA-protected and fully audited access.