Reprocess, cancel and shortfall
Claims are often not fully approved first time, for mundane reasons: missing documents, policy interpretation differences, package or pricing discrepancies.
One pair of calls carries every request a provider makes after a decision. Task.code and its reason say which one it is, and one endpoint, five requests lists the valid combinations.
APIs
| Call | Called by | Method and path | What it does |
|---|---|---|---|
| Provider: submit a reprocess or cancel task | Provider | POST /v1/task/submit | Provider sends a FHIR Task asking the payer to reprocess a rejected or short-paid claim or to cancel a preauth; Task.code and reasonCode set the intent. |
| Payer: send the task outcome | Payer | POST /v1/task/on_submit | Payer returns a Task bundle with Task.status completed whose Task.output references a ClaimResponse carrying the reprocess or cancellation outcome. |
The callback does not carry the decision as its leading resource. It carries a Task whose output points at the ClaimResponse, as the answer is nested sets out.
Callbacks you host
The exchange posts these to the endpoint_url you registered. Answer each with HTTP 202 first.
| Path | Hosted by |
|---|---|
/v1/task/submit | The payer |
/v1/task/on_submit | The provider |
Base URLs
| Environment | Base URL |
|---|---|
| Sandbox, NHCX exchange. | https://apisbx.abdm.gov.in/hcx |
| Production. | https://apisprod.nha.gov.in/hcx |
Guides that use these calls
The whole specification, with a request you can send from the page, is the Reprocess, cancel and shortfall API reference.