ABDM and NHCX: what a hospital actually has to do

Two acronyms get used interchangeably in Indian health-IT sales conversations and they are not the same thing.

ABDM is the Ayushman Bharat Digital Mission — the identity and records layer. ABHA numbers, consent-managed record sharing, FHIR R4 as the exchange format.

NHCX is the National Health Claims Exchange — a standardised pipe for claims between providers and payers, intended to replace the current arrangement where every TPA has its own portal, its own formats and its own quirks.

The distinction that matters commercially

Software can generate an ABHA linkage, produce FHIR R4 records, and build and validate an NHCX claim bundle. All three are engineering problems, and they are solved problems.

Software cannot complete your NHA onboarding. That is an institutional process involving your hospital's registration, credentials and approvals, and it belongs to you.

So when a vendor says "NHCX submission," ask which one they mean. If they generate and validate the payload, the honest phrase is NHCX-ready bundles. If they claim to transmit, ask to see a transmission that went through your onboarding — because it cannot have, if your onboarding is not done.

This is not pedantry. A hospital that buys on "we submit to NHCX" and discovers at go-live that onboarding was never started has lost months, and the vendor has lost the account.

The six things that usually block onboarding

• Facility registration in the Health Facility Registry, current and verified
• Practitioners registered in the Healthcare Professionals Registry
• A working ABHA linkage flow with consent capture that a patient can actually complete at your front desk
• Records emitted as valid FHIR R4, which most legacy HMIS exports are not
• Payer-side readiness — your insurers and TPAs must themselves be on NHCX for a given claim path to exist
• Internal process ownership, because the technical work finishes long before the paperwork does

A readiness check that names which of those six is blocking you is more useful than a claim of compliance. Compliance is not binary here, and the blocking item is usually organisational.

What is worth doing before NHCX matters to you

ABHA linking and FHIR R4 records are worth having regardless, because they are the substrate everything else sits on. A hospital with clean FHIR R4 records is a short step from NHCX when its payers arrive. A hospital with records locked in a proprietary schema has the same work ahead whenever it starts.

Drapto builds and validates NHCX claim bundles and reports which of the six onboarding blockers apply to you. We do not transmit — that runs through your NHA onboarding. See the ABDM layer →