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 issue | Effect on a hospital |
|---|---|
| Duplicate entry | Staff enter the same data in HMIS and TMS. |
| Weak data exchange | Systems cannot reuse beneficiary, clinical, and claim data. |
| Single-system dependency | Portal limits affect user access and claim work. |
| Low flexibility | Hospitals 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
| Benefit | Result |
|---|---|
| Embedded PMJAY flow | Staff use the HMIS for registration, preauthorisation, claim, and payment. |
| Structured data | The HMIS can auto-fill forms and reduce manual errors. |
| Better audit records | Clinical, bill, claim, and payment records stay in the hospital system. |
| Simpler user access | Staff train on one hospital system instead of 2 systems. |
| Higher scale | High-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
| Requirement | What the HMIS must do |
|---|---|
| InsurancePlan response | Use it as the source for packages, costs, STGs, documents, and claim rules. |
| Biometric authentication | Perform beneficiary authentication at registration, preauthorisation, and discharge. |
| Structured data exchange | Send supporting health records as ABDM Health Information Types. |
| Query flow | Do not use the Communication API for PMJAY claim queries. Use the correct preauth or claim workflow ID. |
Normal NHCX flow vs PMJAY flow
| NHCX step | PMJAY HMIS note |
|---|---|
| Get InsurancePlan | Same API. Use the provider-specific PMJAY plan. |
| Get policy | Same API. Confirm the beneficiary policy. |
| Coverage eligibility check | Same API. Use the correct purpose. |
| Preauthorisation | Perform biometric authentication before submission. |
| Communication Request | Do not use it for PMJAY claim queries. |
| Claim submission | Same API. Include discharge details in the claim. |
| Payment Notice | Same API. Acknowledge the payment notice. |
| Status check | Same API pattern. Track the correlation ID. |
Build the HMIS flow, API calls, and PMJAY configuration.
Review roles, milestones, workflow codes, and core API sequences.
Use the InsurancePlan bundle to read benefits, limits, and documents.
Select the API for each hospital scenario.
Use the PMJAY HMIS sandbox exit test cases.
Sources
- pmjay-hmis-integration-overview.md (NHCX sandbox portal)
