NHCX hackathon names winners under digital health mission
The health-claims exchange that standardises insurance claims, built under the Ayushman Bharat Digital Mission.
What happened
- The National Health Authority (NHA) announced the winners of the NHCX Hackathon, run under the Ayushman Bharat Digital Mission (ABDM) to spur innovation around the National Health Claims Exchange (NHCX).
- The hackathon ran 22–28 February 2026; the Grand Finale and NHCX Innovation Meet followed at IIT Hyderabad on 6–7 March 2026, where winning teams demonstrated their solutions.
- 112 submissions were received across five problem statements and judged by an independent jury.
- Two tracks ran in parallel: a Build track for open-source data-conversion utilities and an Ideathon track for misuse/abuse detection and claims-processing optimisation.
- NHA also unveiled NHCX Champions and ABDM Ambassadors, and recognised NHCX–PMJAY Early Integrators — providers and insurers bringing PM-JAY claims onto the standardised exchange.
- NHA CEO Dr. Sunil Kumar Barnwal compared the long-term vision of NHCX to digital public infrastructure such as UPI; the IRDAI Chairman delivered the valedictory address.
Background & context
The NHCX does not stand alone. It is a building block of the Ayushman Bharat Digital Mission (ABDM), the Union government's programme to create a national digital health ecosystem — a set of interoperable registries and identifiers that let health records, providers and now insurance claims talk to one another. ABDM is implemented by the National Health Authority (NHA), the same attached office of the Ministry of Health and Family Welfare that administers the flagship insurance scheme Ayushman Bharat PM-JAY. This shared parentage matters: the NHA runs both the assurance scheme that pays for hospitalisation of the poor and the digital plumbing that the claims under that scheme flow through, which is why the news event specifically singles out NHCX–PMJAY integration.
ABDM grew out of the National Digital Health Mission, launched as a pilot in the Union Territories on 15 August 2020 and rolled out nationally as a full mission in 2021. Its foundational layers are the Ayushman Bharat Health Account (ABHA) — a unique health ID for every citizen — together with the Healthcare Professionals Registry (HPR) and the Health Facility Registry (HFR), the verified directories of doctors and hospitals. On top of these identity layers ABDM is now adding transaction layers, and the claims gateway is the most consequential of them. The release describes the NHCX as one of three gateways under ABDM — the exchange layer that connects the registries and accounts to the actual movement of insurance-claim information.
Before NHCX, a hospital that treated an insured patient typically dealt with each insurer or third-party administrator (TPA) through a different portal, a different file format and a different set of forms. The result was duplicated paperwork, slow pre-authorisation, manual data re-entry and a high rate of claim queries and rejections. The exchange is the government's answer to that fragmentation: a single, standards-based switchboard rather than dozens of bilateral integrations. The hackathon announced here is one rung in building out that switchboard — crowdsourcing the unglamorous but essential tooling (format converters, fraud detectors) that the ecosystem needs before it can scale.
For Prelims
- Full name: National Health Claims Exchange (NHCX) — a unified digital gateway for exchanging health-insurance claims data among hospitals, insurers/TPAs and patients.
- Operated by: the National Health Authority (NHA), an attached office under the Ministry of Health and Family Welfare; built under the Ayushman Bharat Digital Mission (ABDM).
- Place in ABDM: described as one of the three gateways under ABDM; it sits above ABDM's foundational registries — ABHA (health ID), HPR (professionals registry) and HFR (facility registry).
- Data standard: NHCX is built on FHIR (Fast Healthcare Interoperability Resources) — the international standard for exchanging electronic health information — so claims data is structured and machine-readable rather than free-form PDFs.
- The hackathon: 22–28 Feb 2026; 112 submissions across five problem statements; Grand Finale and Innovation Meet at IIT Hyderabad, 6–7 Mar 2026.
- Build track outputs: open-source utilities — Legacy Systems → NHCX-aligned FHIR Converter, Clinical Documents → FHIR Structured Data Converter, and PDF → NHCX-aligned Insurance Plan FHIR Bundle.
- Ideathon track: misuse/abuse (fraud) detection and claims-processing optimisation.
- Ecosystem partners: IRDAI, IIT Hyderabad, National Resource Centre for EHR Standards (NRCeS), General Insurance Council (GIC), Insurance Information Bureau (IIB), Google, NABH, India Insurtech Association (IIA) and NATHealth.
- New launches at the event: NHCX Champions, ABDM Ambassadors, and recognition of NHCX–PMJAY Early Integrators.
- Regulatory anchor on the insurance side: IRDAI (the Insurance Regulatory and Development Authority of India) is the partner that has pushed insurers and TPAs onto the exchange; its Chairman delivered the valedictory address.
What it is NOT. NHCX is not an insurance scheme and it does not itself pay any claim — it is the data-exchange rail, not the money. It is not PM-JAY: PM-JAY is the assurance scheme that funds secondary and tertiary hospitalisation, while NHCX is the standardised pipe through which PM-JAY (and private-insurance) claims can travel. It is not ABHA: ABHA is the citizen's unique health ID, whereas NHCX is the claims-settlement gateway. It is not a regulator — that role belongs to IRDAI on the insurance side; the NHA only builds and operates the exchange. And it is not the same as the National Health Mission (NHM), the centrally-sponsored public-health programme — the names rhyme but the things differ.
The set it belongs to (so "how many / match the pairs" survive). Under the Ayushman Bharat umbrella, distinguish: (i) Ayushman Bharat PM-JAY — the insurance/assurance pillar run by the NHA; (ii) Ayushman Arogya Mandirs (the rebranded Health and Wellness Centres) — the primary-care pillar; and (iii) the Ayushman Bharat Digital Mission (ABDM) — the digital pillar, which contains ABHA, HPR, HFR and the NHCX gateway. The NHA is the common thread administering the insurance pillar and the digital mission. On the technology side, NHCX is the health-sector analogue of digital public infrastructure such as UPI in payments — a shared, standards-based, interoperable rail that many private players plug into.
Why it matters
India's out-of-pocket spending on health remains among the highest in the world, and a major reason private insurance fails to relieve that burden is friction at the point of claim: slow cashless pre-authorisation, manual paperwork, inconsistent data formats and disputes that push families back into out-of-pocket payment even when they are insured. NHCX attacks that friction directly. By forcing every participant — hospital, insurer, TPA — onto a common FHIR-based format and a single exchange, it cuts duplicate data entry, speeds settlement, and makes claims auditable, which in turn makes fraud and abuse easier to detect. The Ideathon track on misuse detection is a recognition that interoperability and integrity must be built together: a faster pipe is only useful if it is also a trustworthy one.
The deliberate comparison to UPI is the key to why this is examinable rather than routine. UPI worked because it was a thin, open, standards-based public rail on which thousands of private apps could compete — the state built the protocol, not the product. NHCX is an attempt to repeat that template in health insurance: a public exchange that any insurer or hospital software can integrate with, lowering the cost of entry and ending the lock-in of bespoke insurer portals. If it succeeds, it converts insurance-claims processing from a private, opaque, bilateral mess into shared digital public infrastructure. The hackathon's open-source converters matter precisely because they lower the on-ramp cost for smaller hospitals and legacy systems that cannot afford custom integration — the difference between a network that only large chains can join and one that reaches the long tail of providers.