Pre-authorisation
Pre-authorisation is the provider's formal request for the payer's approval to deliver a specific treatment to a covered beneficiary.
APIs
| Call | Called by | Method and path | What it does |
|---|---|---|---|
| Provider: submit a pre-authorisation | Provider | POST /v1/preauth/submit | Provider submits, resubmits, enhances or answers a query on a pre-authorisation Claim bundle (Claim.use preauthorization); NHCX routes it to the payer. Also sent as pre-authorisation enhancement. |
| Payer: send the pre-authorisation response | Payer | POST /v1/preauth/on_submit | Payer returns the ClaimResponseBundle for a pre-authorisation (approved, partially approved, queried or rejected) to the provider via NHCX. |
Callbacks you host
The exchange posts these to the endpoint_url you registered. Answer each with HTTP 202 first.
| Path | Hosted by |
|---|---|
/v1/preauth/submit | The payer |
/v1/preauth/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
- Building and sending a JWE
- Preauthorisation request
- Preauthorisation response
- Preauthorisation enhancement
- Preauthorisation query and answer
- Resubmission and cancellation of a pre-authorisation: resubmission on workflow
121, cancellation onPC01, answered onPC02 - Cancelling a pre-authorisation with a Task
- Reprocess, cancel and shortfall calls: a cancellation is sent on
/v1/task/submit, not on/v1/preauth/submit
The whole specification, with a request you can send from the page, is the Pre-authorisation API reference.