National Health Authority

Command Palette

Search for a command to run...

PMJAY Integration Overview

Move PMJAY hospital claim work from TMS-only flow to an ABDM-enabled HMIS through NHCX.

PMJAY hospitals can run the PMJAY claim flow inside an ABDM-enabled HMIS. The HMIS sends claims to the payer through NHCX. This model removes duplicate entry across HMIS and TMS.

Source status

The source calls the sandbox journey tentative. Confirm the latest NHA milestone list before production use.

Why the flow changes

The current PMJAY flow depends on the TMS 2.0 Provider System. Hospitals still keep clinical and financial data in their own HMIS. This creates 2 records for the same PMJAY case.

Current issueEffect on a hospital
Duplicate entryStaff enter the same data in HMIS and TMS.
Weak data exchangeSystems cannot reuse beneficiary, clinical, and claim data.
Single-system dependencyPortal limits affect user access and claim work.
Low flexibilityHospitals cannot adapt PMJAY work to local processes.

Target model

The target model lets the hospital use one HMIS for the PMJAY case. The HMIS records clinical data, billing data, and claim data once. NHCX routes the claim transaction to the payer.

flowchart LR
Hospital[Hospital HMIS] --> NHCX[NHCX]
NHCX --> Payer[PMJAY payer system]
Payer --> NHCX
NHCX --> Hospital

Hospital benefits

BenefitResult
Embedded PMJAY flowStaff use the HMIS for registration, preauthorisation, claim, and payment.
Structured dataThe HMIS can auto-fill forms and reduce manual errors.
Better audit recordsClinical, bill, claim, and payment records stay in the hospital system.
Simpler user accessStaff train on one hospital system instead of 2 systems.
Higher scaleHigh-volume hospitals avoid portal limits and downtime.

Sandbox journey

Complete ABDM M1 readiness

Finish the ABDM M1 work before the PMJAY-specific integration.

Register for NHCX sandbox access

Send the NHCX team the participant ID, client ID, and registry ID.

Configure keys

Create a public key and a private key for JWE payload exchange.

Test the core APIs

Test InsurancePlan, CoverageEligibility, preauthorisation, claim, task, payment, and biometric flows.

Run the PMJAY demo

Show PMJAY interoperability, FHIR validation, structured data, and biometric authentication.

Complete the audits

Complete WASA and other security checks that the PMJAY team requires.

Submit the exit form

Fill the NHCX sandbox exit form after internal tests pass.

PMJAY-specific requirements

RequirementWhat the HMIS must do
InsurancePlan responseUse it as the source for packages, costs, STGs, documents, and claim rules.
Biometric authenticationPerform beneficiary authentication at registration, preauthorisation, and discharge.
Structured data exchangeSend supporting health records as ABDM Health Information Types.
Query flowDo not use the Communication API for PMJAY claim queries. Use the correct preauth or claim workflow ID.

Normal NHCX flow vs PMJAY flow

NHCX stepPMJAY HMIS note
Get InsurancePlanSame API. Use the provider-specific PMJAY plan.
Get policySame API. Confirm the beneficiary policy.
Coverage eligibility checkSame API. Use the correct purpose.
PreauthorisationPerform biometric authentication before submission.
Communication RequestDo not use it for PMJAY claim queries.
Claim submissionSame API. Include discharge details in the claim.
Payment NoticeSame API. Acknowledge the payment notice.
Status checkSame API pattern. Track the correlation ID.

Sources

  • pmjay-hmis-integration-overview.md (NHCX sandbox portal)