Instead of integrating with each insurer’s proprietary portal, a hospital submits a claim once, in a standardized FHIR format, to NHCX. The exchange validates the message structure and routes it to the correct payer, then routes the response back. The same channel carries eligibility checks, pre-authorization, claim submission, adjudication, and payment notices.

Does NHCX store patient data?

No. NHCX is a router, not a repository. The clinical and financial details (the domain payload) are encrypted end-to-end; the gateway sees only routing headers such as sender, recipient, and message ID, and cannot read or store confidential patient data.

What data standard does NHCX use?

NHCX uses HL7 FHIR (Fast Healthcare Interoperability Resources), a globally recognized open healthcare data standard. This ensures information sent by a hospital is interpreted consistently by any insurer, and vice versa.

What is the difference between NHCX and ABDM?

ABDM (Ayushman Bharat Digital Mission) is the broader national digital health infrastructure. NHCX is one gateway within it, focused on insurance claims. A separate ABDM gateway, the HIE-CM, handles consent-based sharing of clinical health records. NHCX solves claims fragmentation; HIE-CM solves clinical-data fragmentation.

How does NHCX benefit hospitals and patients?

For hospitals, NHCX means fewer custom integrations, faster and more predictable settlements, fewer denials from formatting errors, and shorter accounts-receivable cycles. For patients, it enables faster cashless approvals and shorter waits at admission and discharge.

What Is NHCX? The National Health Claims Exchange Explained

Q: What is NHCX?

The National Health Claims Exchange (NHCX) is a standardized digital gateway that securely routes health-insurance claims information between healthcare providers (hospitals, clinics, labs) and payers (insurers, TPAs, government schemes) in India. It acts as an exchange, or router, not a central data store.

Q: Who built NHCX and when did it launch?

NHCX was developed by the National Health Authority (NHA) in consultation with the Insurance Regulatory and Development Authority of India (IRDAI), under the Ayushman Bharat Digital Mission (ABDM). It went live in June 2024, and IRDAI has formally urged insurers and providers to onboard.

A plain-language reference guide to India’s National Health Claims Exchange.

What is NHCX?

The National Health Claims Exchange (NHCX) is a standardized digital gateway that securely routes health-insurance claims information between healthcare providers (hospitals, clinics, diagnostic labs) and payers (insurance companies, third-party administrators, and government schemes) in India.

Its single most important characteristic: NHCX is a router, not a repository. It moves claims data between parties in a common format, but it does not store patients’ clinical or financial records. The confidential “domain payload” is encrypted end-to-end; the exchange reads only the routing headers it needs to deliver each message to the right place.

NHCX was developed by the National Health Authority (NHA) in consultation with the Insurance Regulatory and Development Authority of India (IRDAI), under the Ayushman Bharat Digital Mission (ABDM). It went live in June 2024, and IRDAI has since urged all insurers and providers to onboard.

Why does NHCX exist? The problem it solves

Before NHCX, every payer in India operated its own proprietary claims portal, with its own data format, submission process, and adjudication logic. A hospital working with twenty insurers effectively had to build and maintain twenty different integrations and workflows.

This fragmentation produced the symptoms Indian providers know well:

Long accounts-receivable cycles — claims taking weeks or months to settle.
High denial rates driven by formatting and data-entry mismatches rather than genuine clinical issues.
Heavy manual overhead — phone calls, faxes, portal re-keying, and document chasing for routine steps like eligibility verification.
Low transparency — providers often had little visibility into where a claim stood.

NHCX addresses the root cause: the absence of a common language (a shared data standard) and shared traffic control (a single routing gateway) for claims.

How does NHCX work?

At a high level, NHCX replaces many-to-many custom integrations with a single standardized hub:

Submit once. A hospital sends a claim, or an eligibility or pre-authorization request, to NHCX in a standardized FHIR format, rather than to each insurer’s bespoke portal.
Validate and route. NHCX checks the message structure and routes it to the correct payer using the routing headers, without reading the encrypted payload.
Respond on the same rail. The payer’s response, an eligibility result, an approval, an adjudication decision, or a payment notice, travels back to the provider through the same channel.

Because every participant speaks the same FHIR-based language, information sent by a hospital is interpreted consistently by any insurer, and vice versa.

The workflows NHCX standardizes

NHCX standardizes the core workflows across the claims lifecycle, including:

Provider and payer directory lookups
Coverage eligibility checks
Pre-authorization requests and responses
Predetermination requests
Claim submission and adjudication
Payment notice and reconciliation
Communication requests, status checks, and reprocessing

NHCX vs ABDM vs HIE-CM: clearing up the confusion

These terms are often conflated. They are related but distinct:

Term	What it is	What it solves
ABDM	Ayushman Bharat Digital Mission — India’s national digital health infrastructure	The umbrella program; provides health IDs, registries, and exchange gateways
NHCX	A gateway within ABDM for insurance claims	Claims fragmentation between providers and payers
HIE-CM	A gateway within ABDM for clinical records	Clinical-data fragmentation — letting records follow the patient, on consent

In short: NHCX moves claims; HIE-CM moves clinical records. Both sit inside the broader ABDM stack. (For the umbrella program, see What Is ABDM?; for the clinical-records side, see India’s Health Data Problem and The ABDM Stack.)

What does NHCX change for each stakeholder?

Hospitals and providers: fewer integrations to build and maintain, fewer denials from formatting errors, faster and more predictable settlements, and shorter A/R cycles.
Insurers and TPAs: structured, machine-readable claims that are easier to adjudicate; lower processing overhead; and a foundation for analytics and automation. (See Beyond Intermediation on how the TPA role is evolving.)
Patients: faster cashless approvals, shorter waits at admission and discharge, and a smoother experience overall.

Where NHCX stands today

NHCX went live in June 2024 and is in an active onboarding phase. Adoption depends on insurers and providers integrating their systems and adopting FHIR-compliant claim formats, work that is well underway but uneven across the ecosystem. The trajectory mirrors other Indian digital public infrastructure: a standardized rail laid first, followed by a multi-year ramp in participation and transaction volume.

Key terms

FHIR (Fast Healthcare Interoperability Resources): the open HL7 data standard NHCX uses so all parties exchange claims in a consistent structure.
Domain payload: the encrypted clinical and financial content of a message, which NHCX routes but cannot read.
Routing headers: the non-confidential addressing information (sender, recipient, message ID) NHCX uses to deliver messages.
TPA (Third-Party Administrator): an intermediary that processes claims on behalf of insurers.
Adjudication: the payer’s process of evaluating a claim and deciding what to pay.

Learn more

This page is the hub of our NHCX coverage. To go deeper:

Caladrius Health AI builds AI-native revenue cycle management for healthcare providers, with a focus on India’s NHCX and ABDM rails. Learn more about our platform.