NHCX for Hospitals: How the National Health Claims Exchange Works in 2026

NHCX, the National Health Claims Exchange, is India's attempt to replace the dozens of insurer and TPA portals a hospital billing desk logs into every day with a single, standards-based pipe. Instead of typing the same pre-authorisation into five different websites, the hospital's software sends a structured FHIR message to the exchange, and the exchange routes it to the right payer.

It went live in June 2024 under the Ayushman Bharat Digital Mission (ABDM), run by the National Health Authority (NHA) with the insurance industry. Two years on, the picture is mixed: the plumbing works, insurers are connected, but hospital-side adoption is uneven. That gap is exactly where a well-prepared hospital can gain an advantage.

This guide explains what NHCX actually does in late 2026, what the message formats look like, how it fits with IRDAI's cashless timelines, and what you need to change in your hospital management system before you onboard. If you need the basics of the cashless process itself first, read our guide to TPA management in hospitals.

What NHCX is, and what it is not

NHCX is a message exchange, not a claims adjudication engine. It does not decide whether a claim is payable. It carries standard messages between "participants": hospitals (providers), insurers, TPAs and, in time, government schemes. Think of it as a switch, similar in spirit to how UPI routes payment messages between banks.

What it changes is the format and the channel:

• One integration instead of many. A hospital connects once and reaches every payer on the exchange, rather than maintaining logins and workflows for each insurer and TPA.
• Structured data instead of PDFs. Claims travel as FHIR R4 resources with coded diagnoses, procedures and amounts, with documents attached where needed.
• Asynchronous, trackable messages. Every request gets a correlation ID and a callback, so the status of a pre-auth or claim is visible in your own system instead of in someone's inbox.

What it does not change: your contracts with insurers, package rates, the medical scrutiny of a claim, or the clinical documentation a payer expects. Bad documentation sent faster is still bad documentation.

What is live in 2026

Public, official numbers on NHCX adoption are thin, so treat any vendor slide claiming "thousands of hospitals" with suspicion. Here is what can be stated with reasonable confidence:

• The exchange went online in June 2024 and the first claims flowed that month.
• Major insurers and TPAs have integrated, and industry commentary through 2025-26 describes the remaining public sector insurers being onboarded.
• A November 2025 Business Standard editorial described adoption as uneven across states and hospital networks, which matches what billing teams report on the ground.
• In March 2026 the NHA held an NHCX Innovation Meet at IIT Hyderabad, announced hackathon winners from 112 submissions, and announced an "NHCX-PMJAY Early Integrators" group, signalling that the government scheme side is being brought onto the same rails (PIB release).

For scale, the same Business Standard piece reported that general and health insurers settled ₹94,247 crore across 3.26 crore health insurance claims in 2024-25. Even a modest share of that volume moving to structured messages is a large change for hospital billing.

On mandates: as of late 2026 we have not seen a rule that compels a private hospital to join NHCX. The IRDAI health master circular of May 2024 asks insurers to work towards onboarding their network hospitals, and an IRDAI panel has recommended mandatory integration, but a recommendation is not a rule. Plan for NHCX becoming the default channel, not for a deadline that may or may not arrive.

How NHCX fits with IRDAI's 1-hour and 3-hour rules

The pressure on hospitals did not start with NHCX. It started with IRDAI's master circular on health insurance, which applied from 1 August 2024. Insurers must decide on a cashless authorisation request within one hour of receiving it, and grant final discharge authorisation within three hours of the hospital's request. If the discharge authorisation is delayed beyond three hours, any additional amount the hospital charges for that delay is borne by the insurer (Moneylife summary).

Those clocks only help you if your request is complete when it lands. A one-hour SLA on an incomplete pre-auth just produces a fast query. That is the real case for NHCX: a structured request with the right codes, amounts and attachments is far more likely to be decided in one pass than a scanned form.

The message formats: what the FHIR bundles contain

NHCX uses FHIR R4 profiles published in the ABDM FHIR Implementation Guide maintained by NRCeS (version 6.5.0 at the time of writing). The NHCX profiles in that guide define six bundles and a set of resource profiles:

• CoverageEligibilityRequestBundle and ResponseBundle: check whether a policy is active and what it covers.
• ClaimBundle: one bundle type used for pre-authorisation, predetermination or a final claim, depending on the Claim resource's "use" value.
• ClaimResponseBundle: the payer's adjudication or error.
• InsurancePlanBundle: a description of the insurance product and its benefits.
• TaskBundle: payment information, claim status checks, reprocessing and requests for supporting documents.
• Resource profiles for Communication, CommunicationRequest, Coverage, PaymentNotice and PaymentReconciliation round out the flow.

The guide states that the initial version focuses on the cashless claims process. Reimbursement claims and richer flows are on the roadmap, so design your integration to be version-aware rather than hard-coding today's profiles.

If your team is new to FHIR, start with our HL7 FHIR integration guide. NHCX is a good first real-world FHIR project because the scope is bounded and the profiles are published.

What your hospital software must change

Most HMIS products in India were built around printing forms for TPA desks. NHCX needs the data behind those forms to be structured, coded and available at the moment of request. The typical gaps:

1. Payer master data. Every insurer and TPA needs its NHCX participant code mapped in your system, alongside your existing empanelment and tariff details.
2. Coded clinical data. Diagnoses and procedures must be captured as codes, not only free text, at admission and discharge.
3. Itemised, mappable billing. The final claim needs line items that map cleanly to the payer's expectations. A single "package charges" line hides the detail a payer queries.
4. Document handling. Discharge summaries, investigation reports and consent forms must be attachable as structured references, with sensible file sizes.
5. Status tracking. Pre-auth and claim status must live inside the HMIS, with the correlation IDs NHCX returns, so the billing desk stops checking portals.
6. Callbacks. NHCX is asynchronous. The payer's response arrives as a callback to an endpoint you expose. That endpoint has to be reachable, secure and reliable.

That last point catches on-premise hospitals. If your HMIS sits inside the hospital network with no public address, you need a small, hardened relay or gateway in the cloud that receives callbacks and passes them inward over an outbound connection. Each callback can also come in two shapes, a processed response or a protocol error, and both need handling.

Onboarding: from sandbox to production

The onboarding path is published by NHA and is broadly:

1. Get your registry footing right. Your facility should be on the Health Facility Registry, and your software should already be live on ABDM Milestone 1 (ABHA creation and verification). Vendors who have been through onboarding report that NHA expects M1 to be in place first. Our ABDM integration guide explains the milestones.
2. Apply as a participant through the NHCX sandbox, where the specifications and FHIR profiles live.
3. Build and test each use case against the sandbox: eligibility, pre-auth, claim, communication, payment.
4. Validate your bundles. Profile validation errors are the most common reason for delay. Run the official FHIR validator in your CI pipeline, not only at certification time.
5. Certify and move to production, then switch on one or two payers before going wide.

Timelines vary with how clean your data is. A hospital with structured billing and coded diagnoses can move through in a few months. One with free-text discharge summaries and package-only bills will spend most of that time fixing data, not code.

A practical rollout plan for a 100-200 bed hospital

Measure three things before and after: time from pre-auth request to decision, number of queries per claim, and days from discharge to payment. If NHCX is working for you, all three should improve.

Mistakes we see hospitals make

• Treating NHCX as an IT project. It changes how the billing desk, ward doctors and the discharge team work. Train them before go-live.
• Building a one-off integration. Profiles will evolve. Keep the FHIR mapping in a separate layer so a version change does not ripple through the billing module.
• Ignoring PM-JAY. If you serve scheme patients, watch the NHCX-PMJAY integration track. One pipeline for private and scheme claims is the eventual goal.
• Skipping reconciliation. PaymentReconciliation messages only help if you match them against receivables automatically.

At Algon we build these integration layers as part of our healthcare integration work, usually alongside the billing and TPA modules of a hospital management system, because the data quality problem and the integration problem are the same problem.

Conclusion

NHCX is not a future idea any more. The exchange is running, insurers are on it, and the NHA is pulling government schemes onto the same rails. What is missing is hospital-side readiness, and that is mostly about data: coded diagnoses, itemised bills, clean payer masters and a reliable callback endpoint.

Hospitals that fix those foundations now will see faster pre-auths under IRDAI's one-hour rule, fewer queries and cleaner reconciliation, whether or not a mandate ever arrives. If you want to see how your current billing data would fare, talk to us and we will walk through a sample of your claims.