PMJAY error codes
Every error code a PMJAY integration can meet, in one table. NHCX- codes come from the exchange, PAYR- codes from the PMJAY payer, and ERR-PYR- codes have been seen only in live traffic. Search by code, by a phrase from the message, or by the path you called. Filter by the part of the claim the code belongs to.
Eighteen codes from PAYR-1001 to PAYR-1020 mean different things on the standard payer sheet and on the PMJAY payer's, so read a code with the message beside it. Reading error codes explains the code spaces and what to do about each collision.
310 of 310 codes
| Code | What it means | Message as sent | Area | Arrives on |
|---|---|---|---|---|
| ERR-PYR-CLM-007 | No preauthorisation or claim exists for the claim's case numberThe PMJAY payer refused your claim because it found no preauthorisation or claim under the case number you sent. | Observed live | /v1/claim/on_submit/v1/claim/submit | |
| NHCX-401 | The exchange does not accept your authorisation for this callThe NHCX refused your call because it does not accept you as authorised to make it. The message text is User Unauthorized. | Gateway | /v1/error/v3/sessions | |
| NHCX-1001 | The recipient's system is not reachableThe NHCX accepted your message but could not deliver it. The recipient's registered endpoint did not answer. | Gateway | /v1/error | |
| NHCX-1002 | The sender is not a registered participantThe NHCX does not recognise the sender of your message. Your organisation is not registered as a participant, or the sender code on the message is wrong. | Gateway | /v1/error | |
| NHCX-1003 | The recipient is not a registered participantThe NHCX does not recognise the recipient your message is addressed to. The recipient code is wrong, or that organisation is not registered. | Gateway | /v1/error/v2/participant/get/policies | |
| NHCX-1004 | No recipient is registered for the scheme you asked forThe NHCX found no recipient registered for the scheme on your message. The recipient details do not fit the scheme that the policy belongs to. | Gateway | /v1/error/v2/participant/get/policies | |
| NHCX-1005 | A request header is missing or not validThe NHCX refused your call because a header is missing or holds a value it cannot accept. | Gateway | /v1/error | |
| NHCX-1006 | The correlation id has already been usedThe NHCX already has a request with the correlation id on your message. Each request cycle needs its own correlation id. | Gateway | /v1/error | |
| NHCX-1007 | The exchange could not process the request's structure or valuesThe NHCX failed while processing your message. The message text points at the structure or the values of your request. | Gateway | /v1/error | |
| NHCX-1008 | The exchange had a temporary failureThe NHCX failed while processing your message. The message text asks you to try again after some time. | Gateway | /v1/error | |
| NHCX-1009 | The exchange failed and recorded the cause in its own logsThe NHCX failed while processing your message. The detail is in the exchange's own logs, which you cannot see. | Gateway | /v1/error | |
| NHCX-1010 | No request matches the correlation id on your answerYou sent an answer on an on_ path, and the NHCX holds no request with its correlation id. | Gateway | /v1/error/v1/status | |
| NHCX-1011 | The x-hcx-status value is not validThe NHCX refused your message because x-hcx-status in the protected header holds a value it does not accept. | Gateway | /v1/error | |
| NHCX-1012 | No message matches the api_call_id you gaveThe NHCX found no message with the API call id you referred to. | Gateway | /v1/error/v1/on_status/v1/status | |
| NHCX-1013 | The request body is empty or not validThe NHCX received a call with an empty body, or a body it cannot read as a request. | Gateway | /v1/error | |
| NHCX-1014 | The exchange could not deliver the response to its senderThe NHCX could not deliver a response to the participant it was meant for. That participant's registered endpoint did not take it. | Gateway | /v1/error | |
| NHCX-1015 | The client is not allowed to change this participant's registry detailsThe participant registry refused a change to a participant's record because the client id behind your token is not the one that created the participant. Only the creator's credentials can change the endpoint URL or the encryption certificate through the API. Anyone else changes them on the NHCX portal or through NHCX support. | You are not authorized to update/modify details | Gateway | /v2/participant/update/v2/update/cert |
| NHCX-1016 | The call does not fit the exchange open on this correlation idThe NHCX refused your call because its action does not fit the exchange open under this correlation id. | Gateway | /v1/error | |
| NHCX-1017 | The recipient answered a delivery in a form the exchange does not acceptThe NHCX delivered a message, and the recipient's system answered in a form the exchange does not accept. The exchange treats that answer as a failed delivery. | Invalid response received from receiver | Gateway | /v1/error |
| NHCX-1018 | The ABHA number is not in the XX-XXXX-XXXX-XXXX formThe NHCX refused your message because the ABHA number is not in the form it accepts. | Gateway | /v1/error | |
| PAYR-1001 | The recipient could not decrypt your requestThe recipient could not open the sealed JWE you sent. Its private key does not match the certificate you sealed with, or the sealed content is malformed. | Standard payer sheetBundle structure | /v1/claim/on_submit/v1/coverageeligibility/on_check/v1/preauth/on_submit | |
| PAYR-1002 | The payer could not encrypt its answer to youThe payer received and processed your request, but could not seal its answer to you. It seals answers with the public certificate your organisation registered in NHCX. | Standard payer sheetBundle structure | /v1/claim/on_submit/v1/coverageeligibility/on_check/v1/preauth/on_submit/v2/update/cert | |
| PAYR-1003 | The payer's system could not reach the exchange and will resend, or the workflow requested is not validPAYR-1003 has two meanings, depending on which payer sent it: | Standard payer sheetBundle structureClaim | /v1/claim/on_submit/v1/claim/submit/v1/preauth/on_submit/v1/preauth/submit | |
| PAYR-1004 | Your facility is not registered with the payer for the policy, or the FHIR bundle is malformedPAYR-1004 has two meanings, depending on which payer sent it: | Standard payer sheetBundle structure | /v1/claim/on_submit/v1/claim/submit/v1/coverageeligibility/check/v1/coverageeligibility/on_check/v1/preauth/on_submit/v1/preauth/submit | |
| PAYR-1005 | The beneficiary is not a covered member of the policy, or the request is more than 24 hours oldPAYR-1005 has two meanings, depending on which payer sent it: | Standard payer sheetBundle structureCoverage eligibilityPreauthorisationClaim | /v1/claim/on_submit/v1/claim/submit/v1/coverageeligibility/check/v1/coverageeligibility/on_check/v1/preauth/on_submit/v1/preauth/submit | |
| PAYR-1006 | The policy does not exist, or a name in the request is not validPAYR-1006 has two meanings, depending on which payer sent it: | Standard payer sheetBundle structure | /v1/claim/on_submit/v1/claim/submit/v1/coverageeligibility/check/v1/coverageeligibility/on_check/v1/preauth/on_submit/v1/preauth/submit | |
| PAYR-1007 | The policy has expired, or the gender in the request is not validPAYR-1007 has two meanings, depending on which payer sent it: | Standard payer sheetBundle structure | /v1/claim/on_submit/v1/claim/submit/v1/coverageeligibility/check/v1/coverageeligibility/on_check/v1/preauth/on_submit/v1/preauth/submit | |
| PAYR-1008 | The beneficiary's remaining cover is not enough for the request, or the FHIR bundle is not valid or cannot be parsedPAYR-1008 has two meanings, depending on which payer sent it, and the PMJAY payer also uses it for fifteen messages the error sheet prints without a code. | Standard payer sheetBundle structure | /v1/claim/on_submit/v1/claim/submit/v1/preauth/on_submit/v1/preauth/submit | |
| PAYR-1009 | The requested items are not valid or not covered, or the Patient resource has no identifierPAYR-1009 has two meanings, depending on which payer sent it: | Standard payer sheetBundle structure | /v1/claim/on_submit/v1/claim/submit/v1/preauth/on_submit/v1/preauth/submit | |
| PAYR-1010 | A preauthorisation was required but not obtained, or the Patient identifier has no typePAYR-1010 has two meanings, depending on which payer sent it: | Standard payer sheetBundle structure | /v1/claim/on_submit/v1/claim/submit/v1/preauth/on_submit/v1/preauth/submit | |
| PAYR-1011 | The approved package does not support enhancement, or the Claim resource has no identifierPAYR-1011 has two meanings, depending on which payer sent it: | Standard payer sheetBundle structure | /v1/preauth/on_submit/v1/preauth/submit | |
| PAYR-1012 | The claim amount is more than the approved preauthorisation amount, or the Claim identifier has no typePAYR-1012 has two meanings, depending on which payer sent it: | Standard payer sheetBundle structure | /v1/claim/on_submit/v1/claim/submit | |
| PAYR-1013 | The procedures or packages have no prior approval, or the provider Organization resource has no identifierPAYR-1013 has two meanings, depending on which payer sent it: | Standard payer sheetBundle structure | /v1/claim/on_submit/v1/claim/submit/v1/preauth/on_submit/v1/preauth/submit | |
| PAYR-1014 | The date of birth is after the date of service, or the provider Organization identifier has no typePAYR-1014 has two meanings, depending on which payer sent it: | Standard payer sheetBundle structure | /v1/claim/on_submit/v1/claim/submit/v1/coverageeligibility/check/v1/coverageeligibility/on_check/v1/preauth/on_submit/v1/preauth/submit | |
| PAYR-1015 | The date of service is after the date of death, or the payer Organization resource has no identifierPAYR-1015 has two meanings, depending on which payer sent it: | Standard payer sheetBundle structure | /v1/claim/on_submit/v1/claim/submit | |
| PAYR-1016 | The claim duplicates one already submitted for the same services and dates, or the payer Organization identifier has no typePAYR-1016 has two meanings, depending on which payer sent it: | Standard payer sheetBundle structure | /v1/claim/on_submit/v1/claim/submit | |
| PAYR-1017 | The amount calculations are not correct, or the Task resource has no task codePAYR-1017 has two meanings, depending on which payer sent it: | Standard payer sheetBundle structure | /v1/claim/on_submit/v1/claim/submit/v1/preauth/on_submit/v1/preauth/submit/v1/task/on_submit/v1/task/submit | |
| PAYR-1018 | The time limit for submission has expired, or the Task resource has no reason codePAYR-1018 has two meanings, depending on which payer sent it: | Standard payer sheetBundle structure | /v1/claim/on_submit/v1/claim/submit/v1/preauth/on_submit/v1/preauth/submit/v1/task/on_submit/v1/task/submit | |
| PAYR-1019 | The additional information the payer asked for did not arrive in time, or a supporting info sequence is not validPAYR-1019 has two meanings, depending on which payer sent it: | Standard payer sheetBundle structure | /v1/claim/on_submit/v1/claim/submit/v1/preauth/on_submit/v1/preauth/submit | |
| PAYR-1020 | The payer holds no valid bank details for your facility, or a supporting info category is not validPAYR-1020 has two meanings, depending on which payer sent it: | Standard payer sheetBundle structure | /v1/claim/on_submit/v1/claim/submit/v1/paymentnotice/request | |
| PAYR-1021 | A supporting info entry has an invalid codeYour FHIR bundle lists supporting information, such as dates, discharge details and documents. Each entry has a category and a code. The payer rejected the request because one entry's code is not valid for it. | Invalid code received in supporting info element for sequence %s. Hence request will not be processed further. | Bundle structure | /v1/claim/on_submit/v1/claim/submit/v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1023 | A procedure has an invalid categoryYour FHIR bundle describes each procedure in a Procedure resource. The payer rejected the request because a procedure's category is missing or not one it accepts. | Invalid procedure category received for procedure component. Hence request will not be processed further. | Bundle structure | /v1/claim/on_submit/v1/claim/submit/v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1024 | A procedure has an invalid statusYour FHIR bundle describes each procedure in a Procedure resource, with a status. The payer rejected the request because a procedure's status is missing or not valid. | Invalid procedure status received for procedure component. Hence request will not be processed further. | Bundle structure | /v1/claim/on_submit/v1/claim/submit/v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1025 | A procedure has an invalid sequenceA claim in a FHIR bundle lists its procedures with sequence numbers. Items point at procedures by that number. The payer rejected the request because a procedure's sequence is missing or not valid. | Invalid procedure sequence received for procedure component. Hence request will not be processed further. | Bundle structure | /v1/claim/on_submit/v1/claim/submit/v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1026 | The claim references a procedure that is not in the bundleThe Claim resource in your FHIR bundle points at each procedure through a reference. The payer rejected the request because one of those references finds no Procedure resource in the bundle. | No procedure component found for reference in claim component. Hence request will not be processed further. | Bundle structure | /v1/claim/on_submit/v1/claim/submit/v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1027 | A claim item has an invalid idEach billed item in the Claim resource of your FHIR bundle carries an id. The payer rejected the request because an item's id is missing or not valid. | Invalid item id found for item in claim component. Hence request will not be processed further. | Bundle structure | /v1/claim/on_submit/v1/claim/submit/v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1028 | A claim item has an invalid sequenceEach billed item in the Claim resource of your FHIR bundle carries a sequence number. The payer rejected the request because an item's sequence is missing or not valid. | Invalid item sequence received for item in claim component. Hence request will not be processed further. | Bundle structure | /v1/claim/on_submit/v1/claim/submit/v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1029 | The bundle id is invalidEvery request carries one FHIR bundle, and the bundle has an id. The payer rejected the request because the bundle's id is missing or not valid. | Invalid bundle id received for FHIR bundle. Hence request will not be processed further. | Bundle structure | /v1/claim/on_submit/v1/claim/submit/v1/coverageeligibility/check/v1/coverageeligibility/on_check/v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1030 | A questionnaire id in the bundle is invalidSome policies ask the provider to answer questionnaires. The answers travel as QuestionnaireResponse resources in the FHIR bundle. The payer rejected the request because a questionnaire id in the bundle is not valid. | Invalid questionnaire id received in FHIR bundle for questionnaire component. Hence request will not be processed further. | Bundle structure | /v1/claim/on_submit/v1/claim/submit/v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1031 | A bundle entry has an invalid URLEvery resource in a FHIR bundle sits in an entry with a full URL. References between resources use that URL. The payer rejected the request because an entry's URL is missing or not valid. | Invalid url received for bundle entry in FHIR bundle. Hence request will not be processed further. Please reach out to technical team. | Bundle structure | /v1/claim/on_submit/v1/claim/submit/v1/coverageeligibility/check/v1/coverageeligibility/on_check/v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1032 | The eligibility check has an invalid purposeA coverage eligibility check states what the provider wants to know, in its purpose. The payer rejected the check because the purpose in your FHIR bundle is missing or not one it supports. | Invalid purpose received for coverage eligibility request. Hence request will not be processed further. Please try again with valid purpose details. | Bundle structure | /v1/coverageeligibility/check/v1/coverageeligibility/on_check |
| PAYR-1033 | The eligibility check has no items for its purposeSome eligibility questions are about a specific package or treatment. The FHIR bundle names it in an item. The payer rejected the check because the purpose needs items and the check carries none. | No items received for coverage eligibility purpose. Since items are mandatory for the requested purpose, hence request will not be processed further. Please try again with valid item details. | Bundle structure | /v1/coverageeligibility/check/v1/coverageeligibility/on_check |
| PAYR-1034 | A procedure code is invalidEach procedure and billed item in your FHIR bundle names a package by its code. The payer rejected the request because a procedure code is not valid. | Invalid procedure code received. Please try again with valid procedure details. | Bundle structure | /v1/claim/on_submit/v1/claim/submit/v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1035 | The policy code is invalidEvery request names the insurance policy it is made under. The payer rejected the request because the policy code in your FHIR bundle is not valid. | Invalid policy code received. Please try again with valid policy details. | Bundle structure | /v1/claim/on_submit/v1/claim/submit/v1/coverageeligibility/check/v1/coverageeligibility/on_check/v1/insuranceplan/on_request/v1/insuranceplan/request/v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1036 | A supporting info entry lacks a valid attachmentSome supporting information entries in your FHIR bundle carry a document, such as a clinical note or a report. The payer rejected the request because an entry that must carry a document has no valid attachment. | Invalid attachment received in supporting info with sequence number %s. Please try again with valid attachment details as attachment value is expected. If issue is not resolved, please reach out to technical team. | Bundle structure | /v1/claim/on_submit/v1/claim/submit/v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1037 | The communication has no identifierWhen a payer sends a communication request, you answer with a FHIR bundle that carries a Communication resource. The payer rejected your answer because the Communication resource has no identifier. | No identifier found for communication component. Hence request will not be processed further. | Bundle structure | /v1/communication/on_request/v1/communication/request |
| PAYR-1038 | The communication identifier has no typeWhen a payer sends a communication request, you answer with a FHIR bundle that carries a Communication resource. The payer rejected your answer because the Communication resource's identifier has no type. | No type found for communication component identifier. Hence request will not be processed further. | Bundle structure | /v1/communication/on_request/v1/communication/request |
| PAYR-1039 | The communication has no payloadWhen a payer sends a communication request, you answer with a FHIR bundle that carries a Communication resource. The payer rejected your answer because the Communication resource has no payload. | No payload found for communication component. Hence request will not be processed further. | Bundle structure | /v1/communication/on_request/v1/communication/request |
| PAYR-1040 | A reference points at a resource that is not in the bundleResources in a FHIR bundle point at each other through references. The payer rejected the request because a reference points at a resource that is not in the bundle. | No component found for given reference. Hence request will not be processed further. | Bundle structure | /v1/claim/on_submit/v1/claim/submit/v1/coverageeligibility/check/v1/coverageeligibility/on_check/v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1041 | A procedure has no identifierEach Procedure resource in your FHIR bundle carries an identifier, its serial number. The payer rejected the request because a Procedure resource has no identifier. | No identifier found for procedure component. Hence request will not be processed further. | Bundle structure | /v1/claim/on_submit/v1/claim/submit/v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1042 | A procedure identifier has no typeEach Procedure resource in your FHIR bundle carries an identifier with a type. The payer rejected the request because a procedure identifier has no type. | No type found for procedure component identifier. Hence request will not be processed further. | Bundle structure | /v1/claim/on_submit/v1/claim/submit/v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1043 | A date is in the wrong formatDates in a FHIR bundle follow the date format of the NRCeS profiles. The payer rejected the request because a date does not. | Date received in the request does not adhere to the NRCES date datatype format. Hence request will not be processed further. Please refere to the date format in NRCES portal. | Bundle structure | /v1/claim/on_submit/v1/claim/submit/v1/coverageeligibility/check/v1/coverageeligibility/on_check/v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1044 | A date and time is in the wrong formatDates with times in a FHIR bundle follow the date and time format of the NRCeS profiles. The payer rejected the request because one does not. | Date and time received in the request does not adhere to the NRCES date datatype format. Hence request will not be processed further. Please refere to the date time format in NRCES portal. | Bundle structure | /v1/claim/on_submit/v1/claim/submit/v1/coverageeligibility/check/v1/coverageeligibility/on_check/v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1045 | A claim item has an invalid quantityEach billed item in the Claim resource of your FHIR bundle states how many units it bills. The payer rejected the request because an item's quantity is missing or not valid. | Invalid quantity received for item. Hence request will not be processed further. | Bundle structure | /v1/claim/on_submit/v1/claim/submit/v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1046 | A supporting info entry has no value or dateEvery supporting information entry in your FHIR bundle carries its content, either a value or a date. The payer rejected the request because one entry carries neither. | No value or timing details received for supporting info for sequence %s. Hence request will not be processed further. Please reach out to technical team. | Bundle structure | /v1/claim/on_submit/v1/claim/submit/v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1047 | A supporting info entry has an invalid referenceA supporting information entry can point at another resource in your FHIR bundle, such as a clinical record. The payer rejected the request because an entry's reference is not valid. | Invalid reference received in supporting info with sequence number %s. Please try again with valid resource as reference value. | Bundle structure | /v1/claim/on_submit/v1/claim/submit/v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1048 | A supporting info entry references a resource that is not in the bundleA supporting information entry can point at another resource in your FHIR bundle. The payer rejected the request because the resource the entry points at is not in the bundle. | No reference resource received for supporting info with sequence number %s. Please try again with valid resource for reference value. | Bundle structure | /v1/claim/on_submit/v1/claim/submit/v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1049 | The payer cannot accept the bundleThe payer could not accept your FHIR bundle as a whole. The message names no element. | Invalid FHIR bundle received. Hence request will not be processed further. please reach out to technical team. | Bundle structure | /v1/claim/on_submit/v1/claim/submit/v1/coverageeligibility/check/v1/coverageeligibility/on_check/v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1050 | A practitioner identifier has no typePractitioners in your FHIR bundle carry identifiers, such as their HPR id. The payer rejected the request because a practitioner's identifier has no type. | No type found for practitioner component identifier. Hence request will not be processed further. | Bundle structure | /v1/claim/on_submit/v1/claim/submit/v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1051 | A clinical record has no sectionClinical records attached to a preauthorisation or claim travel as Composition resources in the FHIR bundle. A Composition groups its content into sections. The payer rejected the request because a Composition has no section. | No section found for composition component. Hence request will not be processed further. | Bundle structure | /v1/claim/on_submit/v1/claim/submit/v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1052 | A clinical record section has no referencesClinical records in your FHIR bundle are Composition resources. Each section lists its content as references. The payer rejected the request because a section has no references. | No references found in composition section. Hence request will not be processed further. | Bundle structure | /v1/claim/on_submit/v1/claim/submit/v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1053 | A nested clinical record section has an invalid referenceA Composition section in your FHIR bundle can hold child sections, each with references. The payer rejected the request because a reference in a child section is not valid. | Invalid reference found in child sections of composition section. Hence request will not be processed further. | Bundle structure | /v1/claim/on_submit/v1/claim/submit/v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1054 | A clinical record section is emptyClinical records in your FHIR bundle are Composition resources made of sections. The payer rejected the request because a section carries no content. | No section content found for composition component. Hence request will not be processed further. | Bundle structure | /v1/claim/on_submit/v1/claim/submit/v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1055 | A clinical record has no subject or its subject is not a patientEach clinical record in your FHIR bundle is a Composition that names the patient it is about, in its subject. The payer rejected the request because a Composition has no subject, or its subject is not a Patient. | No subject found for composition component. Hence request will not be processed further. | Bundle structure | /v1/claim/on_submit/v1/claim/submit/v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1056 | The patient's contact organization is not an OrganizationThe payer checks the Patient that each clinical record in your FHIR bundle is about. It rejected the request because that patient's contact organization is not an Organization. | Invalid contact organization found for subject in composition component. This should be of type Organization. Hence request will not be processed further. Please try again with valid data. | Bundle structure | /v1/claim/on_submit/v1/claim/submit/v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1057 | The patient's general practitioner has the wrong typeThe payer checks the Patient that each clinical record in your FHIR bundle is about. It rejected the request because that patient's general practitioner is the wrong type of resource. | Invalid general practioner type found for subject in composition component. This should be of type Organization/Practitioner/PractitionerRole. Hence request will not be processed further. Please refer to https://www.nrces.in/ndhm/fhir/r4/StructureDefinition-Patient.html | Bundle structure | /v1/claim/on_submit/v1/claim/submit/v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1058 | The patient's managing organization is not an OrganizationThe payer checks the Patient that each clinical record in your FHIR bundle is about. It rejected the request because that patient's managing organization is not an Organization. | Invalid managing organization type found for subject in composition component. This should be of type Organization. Hence request will not be processed further. Please refer to https://www.nrces.in/ndhm/fhir/r4/StructureDefinition-Patient.html | Bundle structure | /v1/claim/on_submit/v1/claim/submit/v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1059 | A clinical record points at something other than an encounterClinical records and observations in your FHIR bundle point at the visit they belong to, an Encounter. The payer rejected the request because a Composition or Observation points at something other than an Encounter. | Invalid encounter type found for composition/observation component. This should be of type Encounter. Hence request will not be processed further. Please refer to https://www.nrces.in/ndhm/fhir/r4/StructureDefinition-DiagnosticReportRecord.html | Bundle structure | /v1/claim/on_submit/v1/claim/submit/v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1060 | A clinical record has no encounter or its encounter has no subjectClinical records and observations in your FHIR bundle point at the visit they belong to, an Encounter. That Encounter names the patient. The payer rejected the request because one of these links is missing. | No encounter found for composition/observation component. Hence request will not be processed further. | Bundle structure | /v1/claim/on_submit/v1/claim/submit/v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1061 | An encounter's subject has the wrong resource typeYour bundle carries clinical records as Composition and Observation resources. Each can point at an Encounter, the visit the record belongs to. One of those Encounters names a subject of a type the payer does not accept, so the payer stopped processing your request. | Invalid subject type found for encounter in composition/observation component. Hence request will not be processed further. Please refer to https://www.nrces.in/ndhm/fhir/r4/StructureDefinition-Encounter.html | Bundle structure | /v1/claim/on_submit/v1/claim/submit/v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1062 | An encounter has no episode of care the payer can findYour bundle carries clinical records as Composition and Observation resources. Each can point at an Encounter, the visit the record belongs to. The payer could not find an episode of care for one of those Encounters, so it stopped processing your request. | No episode of care found for encounter in composition/observation component. Hence request will not be processed further. Please refer to https://www.nrces.in/ndhm/fhir/r4/StructureDefinition-Encounter.html | Bundle structure | /v1/claim/on_submit/v1/claim/submit/v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1063 | An encounter's episode of care has the wrong resource typeYour bundle carries clinical records as Composition and Observation resources. Each can point at an Encounter, the visit the record belongs to. One of those Encounters has an episode of care reference that points at the wrong kind of resource, so the payer stopped processing your request. | Invalid episode of care type found for encounter in composition/observation component. Hence request will not be processed further. Please refer to https://www.nrces.in/ndhm/fhir/r4/StructureDefinition-Encounter.html | Bundle structure | /v1/claim/on_submit/v1/claim/submit/v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1064 | An encounter has no based-on reference the payer can findYour bundle carries clinical records as Composition and Observation resources. Each can point at an Encounter, the visit the record belongs to. The payer could not find the based-on reference for one of those Encounters, so it stopped processing your request. | No based on found for encounter in composition/observation component. Hence request will not be processed further. Please refer to https://www.nrces.in/ndhm/fhir/r4/StructureDefinition-Encounter.html | Bundle structure | /v1/claim/on_submit/v1/claim/submit/v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1065 | An encounter's based-on reference has the wrong resource typeYour bundle carries clinical records as Composition and Observation resources. Each can point at an Encounter, the visit the record belongs to. One of those Encounters has a based-on reference that points at the wrong kind of resource, so the payer stopped processing your request. | Invalid based on type found for encounter in composition/observation component. Hence request will not be processed further. Please refer to https://www.nrces.in/ndhm/fhir/r4/StructureDefinition-Encounter.html | Bundle structure | /v1/claim/on_submit/v1/claim/submit/v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1066 | An encounter has no appointment the payer can findYour bundle carries clinical records as Composition and Observation resources. Each can point at an Encounter, the visit the record belongs to. The payer could not find an appointment for one of those Encounters, so it stopped processing your request. | No appointment found for encounter in composition/observation component. Hence request will not be processed further. Please refer to https://www.nrces.in/ndhm/fhir/r4/StructureDefinition-Encounter.html | Bundle structure | /v1/claim/on_submit/v1/claim/submit/v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1067 | An encounter's appointment has the wrong resource typeYour bundle carries clinical records as Composition and Observation resources. Each can point at an Encounter, the visit the record belongs to. One of those Encounters has an appointment reference that points at the wrong kind of resource, so the payer stopped processing your request. | Invalid appointment type found for encounter in composition/observation component. Hence request will not be processed further. Please refer to https://www.nrces.in/ndhm/fhir/r4/StructureDefinition-Encounter.html | Bundle structure | /v1/claim/on_submit/v1/claim/submit/v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1068 | An encounter has no reason reference the payer can findYour bundle carries clinical records as Composition and Observation resources. Each can point at an Encounter, the visit the record belongs to. The payer could not find the reason reference for one of those Encounters, so it stopped processing your request. | No reason reference found for encounter in composition/observation component. Hence request will not be processed further. Please refer to https://www.nrces.in/ndhm/fhir/r4/StructureDefinition-Encounter.html | Bundle structure | /v1/claim/on_submit/v1/claim/submit/v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1069 | An encounter's reason reference has the wrong resource typeYour bundle carries clinical records as Composition and Observation resources. Each can point at an Encounter, the visit the record belongs to. One of those Encounters has a reason reference that points at the wrong kind of resource, so the payer stopped processing your request. | Invalid reason reference type found for encounter in composition/observation component. Hence request will not be processed further. Please refer to https://www.nrces.in/ndhm/fhir/r4/StructureDefinition-Encounter.html | Bundle structure | /v1/claim/on_submit/v1/claim/submit/v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1070 | A composition has no authorYour bundle carries clinical documents as Composition resources. One of them does not say who wrote it, so the payer stopped processing your request. | No author found for composition component. Hence request will not be processed further. | Bundle structure | /v1/claim/on_submit/v1/claim/submit/v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1071 | A composition's author has the wrong resource typeYour bundle carries clinical documents as Composition resources. One of them names an author of a type the payer does not accept, so the payer stopped processing your request. | Invalid author type found for composition component. This should be of type Practitioner / PractitionerRole / Organization / Patient / Device / RelatedPerson. Hence request will not be processed further. Please try again with valid author type for the composition. | Bundle structure | /v1/claim/on_submit/v1/claim/submit/v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1072 | A claim procedure has no procedure referenceThe Claim resource in your bundle lists procedures in procedure. One entry does not say which Procedure resource it means, so the payer stopped processing your request. | No procedure reference received for procedure element in claim resource. Hence request will not be processed further. | Bundle structure | /v1/claim/on_submit/v1/claim/submit/v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1073 | An observation has no based-on referenceYour bundle carries test results and other findings as Observation resources. The payer could not find the based-on reference for one of them, so it stopped processing your request. | No based on found for observation component. Hence request will not be processed further. Please refer to https://www.nrces.in/ndhm/fhir/r4/StructureDefinition-Observation.html | Bundle structure | /v1/claim/on_submit/v1/claim/submit/v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1074 | An observation's based-on reference has the wrong resource typeYour bundle carries test results and other findings as Observation resources. One of them has a based-on reference that points at the wrong kind of resource, so the payer stopped processing your request. | Invalid based on type found for observation component. Hence request will not be processed further. Please refer to https://www.nrces.in/ndhm/fhir/r4/StructureDefinition-Observation.html | Bundle structure | /v1/claim/on_submit/v1/claim/submit/v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1075 | An observation has no part-of referenceYour bundle carries test results and other findings as Observation resources. The payer could not find the part-of reference for one of them, so it stopped processing your request. | No part of found for observation component. Hence request will not be processed further. Please refer to https://www.nrces.in/ndhm/fhir/r4/StructureDefinition-Observation.html | Bundle structure | /v1/claim/on_submit/v1/claim/submit/v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1076 | An observation's part-of reference has the wrong resource typeYour bundle carries test results and other findings as Observation resources. One of them has a part-of reference that points at the wrong kind of resource, so the payer stopped processing your request. | Invalid part of type found for observation component. Hence request will not be processed further. Please refer to https://www.nrces.in/ndhm/fhir/r4/StructureDefinition-Observation.html | Bundle structure | /v1/claim/on_submit/v1/claim/submit/v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1077 | An observation has no subjectYour bundle carries test results and other findings as Observation resources. One of them does not say which patient it is about, so the payer stopped processing your request. | No subject found for observation component. Hence request will not be processed further. | Bundle structure | /v1/claim/on_submit/v1/claim/submit/v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1078 | An observation's subject is not a PatientYour bundle carries test results and other findings as Observation resources. One of them names a subject that is not a Patient, so the payer stopped processing your request. | Invalid subject type found for observation component. This should be of type Patient. Hence request will not be processed further. Please try again with valid subject type for the observation. | Bundle structure | /v1/claim/on_submit/v1/claim/submit/v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1079 | The claim has no care teamThe Claim resource in your bundle must name the practitioners treating the patient in careTeam. It has none, so the payer stopped processing your request. | No care team details received. Hence request will not be processed further. Please add the care team details and try again. | Bundle structure | /v1/claim/on_submit/v1/claim/submit/v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1080 | A practitioner's HPR id is not validEach Practitioner in your bundle carries the practitioner's HPR id. The payer did not accept the id on one of them, so it stopped processing your request. | Invalid HPR details received for practioner resource with url %s. Hence request will not be processed further. Please try again with valid HPR id. | Bundle structure | /v1/claim/on_submit/v1/claim/submit/v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1081 | An item's service date is not validEach item in the Claim resource carries the date or period of service. The payer did not accept the date on one item, so it stopped processing your request. | Invalid service date received for item with sequence %s in claim resource. Hence request will not be processed further. Please try again with valid item service date. | Bundle structure | /v1/claim/on_submit/v1/claim/submit/v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1082 | A composition linked from supporting info has an invalid titleSupporting information on the Claim can point at a Composition, such as a lab report. The payer did not accept the title of one of those Compositions, so it stopped processing your request. | Invalid title received for composition for supporting info with sequence %s in claim resource. Hence request will not be processed further. Please try again with valid composition title. | Bundle structure | /v1/claim/on_submit/v1/claim/submit/v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1083 | A practitioner has no HPR idEach Practitioner in your bundle must carry the practitioner's HPR id. One of them has none, so the payer stopped processing your request. | No HPR details found for the practitioner for resource %s. Hence request will not be processed further. Please send the details in the identifier for Practitioner resource with category code as HPIN. | Bundle structure | /v1/claim/on_submit/v1/claim/submit/v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1084 | A reference points at a questionnaire response that is not in the bundleSupporting information can point at a QuestionnaireResponse, for example the answers to a policy or treatment questionnaire. One reference points at a url with no QuestionnaireResponse behind it, so the payer stopped processing your request. | No questionnaire response resource found for url %s. Hence request will not be processed further. Please add the resources for all the references given in the FHIR bundle and try again. | Bundle structure | /v1/claim/on_submit/v1/claim/submit/v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1085 | A questionnaire response reference points at the wrong resource typeSupporting information can point at a QuestionnaireResponse. One such reference points at an entry of another resource type, so the payer stopped processing your request. | Invalid questionnaire response resource type found in the FHIR bundle for url %s. Hence request will not be processed further. | Bundle structure | /v1/claim/on_submit/v1/claim/submit/v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1086 | A reference points at a procedure that is not in the bundleEach Claim.procedure entry points at a Procedure resource in the bundle. One reference points at a url with no Procedure behind it, so the payer stopped processing your request. | No procedure resource found for url %s. Hence request will not be processed further. Please add the resources for all the references given in the FHIR bundle and try again. | Bundle structure | /v1/claim/on_submit/v1/claim/submit/v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1087 | A procedure reference points at the wrong resource typeEach Claim.procedure entry points at a Procedure resource in the bundle. One reference points at an entry of another resource type, so the payer stopped processing your request. | Invalid procedure resource type found in the FHIR bundle for url %s. Hence request will not be processed further. Procedure resource type is expected. | Bundle structure | /v1/claim/on_submit/v1/claim/submit/v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1088 | A composition failed the payer's checksYour bundle carries clinical documents as Composition resources. One of them failed the payer's checks, and the message does not name the element. The payer stopped processing your request. | Invalid composition details. | Bundle structure | /v1/claim/on_submit/v1/claim/submit/v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1089 | The claim has no billing itemsThe Claim resource lists what you are billing for in item. It has no items, so the payer stopped processing your request. | No billing items found. Hence request will not be processed further. Please try again with valid billing items. | Bundle structure | /v1/claim/on_submit/v1/claim/submit/v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1090 | The coverage has no identifierEvery eligibility, preauthorisation and claim bundle carries a Coverage resource for the beneficiary's policy. Yours has no identifier, so the payer could not tell which policy you mean. | No identifier found for coverage component. Hence request will not be processed further. | Bundle structure | /v1/claim/on_submit/v1/claim/submit/v1/coverageeligibility/check/v1/coverageeligibility/on_check/v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1091 | The coverage identifier has no typeEvery eligibility, preauthorisation and claim bundle carries a Coverage resource for the beneficiary's policy. Its identifier has no type, so the payer stopped processing your request. | No type found for coverage component identifier. Hence request will not be processed further. | Bundle structure | /v1/claim/on_submit/v1/claim/submit/v1/coverageeligibility/check/v1/coverageeligibility/on_check/v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1092 | The payer failed while processing your requestThe payer hit a failure while processing your request. The message names no element in your bundle. It asks you to start a new request. | Something went wrong while processing request, kindly intiate new request | Bundle structure | /v1/claim/on_submit/v1/claim/submit/v1/coverageeligibility/check/v1/coverageeligibility/on_check/v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1093 | An encounter linked from a composition has no subjectYour bundle carries clinical records as Composition and Observation resources. Each can point at an Encounter, the visit the record belongs to. The Encounter behind one Composition does not say which patient it is about, so the payer stopped processing your request. | No subject found for encounter in composition component. Hence request will not be processed further. Please refer to https://www.nrces.in/ndhm/fhir/r4/StructureDefinition-Encounter.html | Bundle structure | /v1/claim/on_submit/v1/claim/submit/v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1094 | An encounter's subject has the wrong resource typeYour bundle carries clinical records as Composition and Observation resources. Each can point at an Encounter, the visit the record belongs to. One of those Encounters names a subject of a type the payer does not accept, so the payer stopped processing your request. | Invalid subject type found for encounter in composition/observation component. Hence request will not be processed further. Please refer to https://www.nrces.in/ndhm/fhir/r4/StructureDefinition-Encounter.html | Bundle structure | /v1/claim/on_submit/v1/claim/submit/v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1095 | The claim carries no valid discharge informationA claim must say how the patient was discharged. Yours carries no valid discharge information, so the payer stopped processing it. | Invalid discharge information received for claim request. Hence request will not be processed further. Please send the discharge information in supporting info in claim resource, with category as DIS (refer - https://www.nrces.in/ndhm/fhir/r4/ValueSet-ndhm-supportinginfo-category.html), and codes in LAMA/DAMA/DTH/DTM (refer - https://www.nrces.in/ndhm/fhir/r4/ValueSet-ndhm-supportinginfo-code.html). | Bundle structure | /v1/claim/on_submit/v1/claim/submit |
| PAYR-1096 | A death discharge carries no valid death dateWhen the discharge type is death, the claim must carry the date of death. Yours carries no valid death date, so the payer stopped processing it. | Invalid death date received for claim request. Hence request will not be processed further. Please send the death date information in supporting info in claim resource, with category as ONS (refer - https://www.nrces.in/ndhm/fhir/r4/ValueSet-ndhm-supportinginfo-category.html), and code as DTM (refer - https://www.nrces.in/ndhm/fhir/r4/ValueSet-ndhm-supportinginfo-code.html). | Bundle structure | /v1/claim/on_submit/v1/claim/submit |
| PAYR-1097 | The request arrived with no encrypted payloadEvery request carries your FHIR bundle, encrypted, in the payload property of the request body. The payer opened your request and found no encrypted payload. | No payload found in the request. Please ensure that the request that is being sent, contains encrypted payload within the mandatory payload properties. | Bundle structure | /v1/claim/on_submit/v1/claim/submit/v1/coverageeligibility/check/v1/coverageeligibility/on_check/v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1098 | The registration date has the wrong value typeThe Claim resource carries the patient's registration date as a supporting info entry with category OTH and code EDT. That entry's value has a type the payer does not accept. | Value type received as %s for category - OTH and code - EDT for item with sequence %s in supporting info in claim resource. In supporting info list, item with category - OTH and code - EDT combination is used to get the registration date. So the registration date should be sent as timing (date or period) or as a string value, adhering to the NRCES standards, with the category - OTH and code - EDT. | Bundle structure | /v1/claim/on_submit/v1/claim/submit/v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1099 | The discharge date has the wrong value typeThe claim carries the discharge date as a supporting info entry with category ONS and code DSDE. That entry's value has a type the payer does not accept. | Value type received as %s for category - ONS and code - DSDE for item with sequence %s in supporting info in claim resource. In supporting info list, item with category - ONS and code - DSDE combination is used to get the discharge date. So the discharge date should be sent as timing (date or period) or as a string value, adhering to the NRCES standards, with the category - ONS and code - DSDE. | Bundle structure | /v1/claim/on_submit/v1/claim/submit |
| PAYR-1101 | The eligibility purpose is not validEvery eligibility check says what you want to know, in CoverageEligibilityRequest.purpose. The payer did not accept the purpose you sent, so it returned no result. | Invalid purpose received as (%s) for beneficiary id (%s) from hospital id (%s). Hence no result will be returned. Please try again with a valid purpose. | Coverage eligibilityPreauthorisation | /v1/coverageeligibility/check/v1/coverageeligibility/on_check/v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1102 | The id you searched with is not validThe payer looks up the beneficiary from the id in your request. The id you sent is not one it recognises. | Invalid search parameter requested. Please try again with a valid id. | Coverage eligibilityPreauthorisationClaim | /v1/claim/on_submit/v1/claim/submit/v1/coverageeligibility/check/v1/coverageeligibility/on_check/v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1103 | The care plan id is not validYour request carries a care plan id. The payer does not recognise the id you sent, so it stopped processing the request. | Invalid careplan id received. Please try again with valid careplan id. | Coverage eligibilityPreauthorisation | /v1/coverageeligibility/check/v1/coverageeligibility/on_check/v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1104 | More than one beneficiary record matchesThe payer looks up the beneficiary from the identifiers in your request. They match more than one record in its system, so it cannot tell which person you mean. | Multiple records found for the beneficiary. Hence request will not be processed further. | Coverage eligibilityPreauthorisation | /v1/coverageeligibility/check/v1/coverageeligibility/on_check/v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1105 | The payer has no configuration for your hospitalThe payer keeps a configuration for each hospital it deals with. It found none for yours, so it could not process your check. | Hospital configuration not found. Please contact support team. | Coverage eligibility | /v1/coverageeligibility/check/v1/coverageeligibility/on_check |
| PAYR-1106 | The payer has no details for a requested procedureAn auth-requirements check lists the procedures you want to know about. The payer holds no details for one of them. | No details found for the requested procedures in the system. | Coverage eligibility | /v1/coverageeligibility/check/v1/coverageeligibility/on_check |
| PAYR-1107 | The check carries no billable itemAn auth-requirements check must list the procedures you want to know about. Yours carries no item the payer can bill against. | No billable item received. Please try again with valid item data. | Coverage eligibility | /v1/coverageeligibility/check/v1/coverageeligibility/on_check |
| PAYR-1108 | The payer has no details for the requested stratificationAn item in an eligibility check can carry a stratification, such as a ward or care level. The payer holds no details for the one you sent. | No details found for the requested stratification in the system. | Coverage eligibility | /v1/coverageeligibility/check/v1/coverageeligibility/on_check |
| PAYR-1109 | The payer has no details for a requested investigationAn eligibility check can ask about investigations, such as laboratory tests. The payer holds no details for one you sent. | No details found for the requested investigations in the system. | Coverage eligibility | /v1/coverageeligibility/check/v1/coverageeligibility/on_check |
| PAYR-1110 | The payer has no details for a requested implantAn eligibility check can ask about implants used in a procedure. The payer holds no details for one you sent. | No details found for the requested implants in the system. | Coverage eligibility | /v1/coverageeligibility/check/v1/coverageeligibility/on_check |
| PAYR-1111 | A payer rule rejected the requestThe payer applies business rules to every check. One of them rejected yours. The message does not say which rule failed. | Rule failure. | Coverage eligibility | /v1/coverageeligibility/check/v1/coverageeligibility/on_check |
| PAYR-1112 | The payer id is not validYour check names the payer it is for. The payer id you sent is not valid, so the payer stopped processing the check. | Invalid payer id received. Please try again ith valid payer details | Coverage eligibility | /v1/coverageeligibility/check/v1/coverageeligibility/on_check |
| PAYR-1113 | An item code is not validEach item in an eligibility check carries a package or procedure code. The payer did not accept the code named in the message. | Invalid item code received as %s. Please try again with valid data | Coverage eligibility | /v1/coverageeligibility/check/v1/coverageeligibility/on_check |
| PAYR-1114 | An item's speciality code is not validEach item in an eligibility check carries a speciality code, such as the code for general medicine. The payer did not accept the one on the item named in the message. | Invalid speciality code received as %s for item %s. Please try again with valid data. Speciality code is available as the code of the category for specific cost of plan in isurance plan | Coverage eligibility | /v1/coverageeligibility/check/v1/coverageeligibility/on_check |
| PAYR-1115 | An item's quantity is not validEach item in an eligibility check carries a quantity. The payer did not accept the quantity on the item named in the message. | Invalid procedure quantity received as %s for item %s. Please try again with valid data. Item quantity should be greater than 1 | Coverage eligibility | /v1/coverageeligibility/check/v1/coverageeligibility/on_check |
| PAYR-1116 | Your hospital is not authorised under the policyA hospital can raise cases only under the policies it is authorised for. Yours is not authorised under the policy in the message. | Hospital is not authorized to raise any case under policy %s. Hence request will not be processed further. Please connect with the support team to get the required authorization | Coverage eligibility | /v1/coverageeligibility/check/v1/coverageeligibility/on_check |
| PAYR-1117 | The payer has no details for the policyYour check names the beneficiary's policy. The payer holds no details for the policy named in the message. | No policy details found for %s. Hence request will not be processed further | Coverage eligibility | /v1/coverageeligibility/check/v1/coverageeligibility/on_check |
| PAYR-1118 | The payer has no details for the requested itemsAn auth-requirements check lists the items you want to know about. The payer holds no details for them. | No details found for requested items. Hence request will not be processed further | Coverage eligibility | /v1/coverageeligibility/check/v1/coverageeligibility/on_check |
| PAYR-1119 | The payer received no details for the payer id from the exchangeThe payer looks up the payer id in your request with the exchange. The exchange returned no details for the id in the message. | No payer details received for payer id %s from HCX. Please try again with valid payer details. | Coverage eligibility | /v1/coverageeligibility/check/v1/coverageeligibility/on_check |
| PAYR-1120 | The reference id has been used beforeEach request carries a reference id. The payer has already received one with the id in the message. | Duplicate reference id found as %s. Please try again with valid reference details. | Coverage eligibility | /v1/coverageeligibility/check/v1/coverageeligibility/on_check |
| PAYR-1121 | The policy is not found for this beneficiaryThe payer checks that the beneficiary holds the policy in your request. It holds no record of that policy for that beneficiary. | No policy details found for %s for beneficiary %s. Hence request will not be processed further. | Coverage eligibility | /v1/coverageeligibility/check/v1/coverageeligibility/on_check |
| PAYR-1122 | The beneficiary has no policy with the payerThe payer looks for the policies held by the beneficiary in your request. It found none. | No policy details found for beneficiary %s. Hence request will not be processed further. | Coverage eligibility | /v1/coverageeligibility/check/v1/coverageeligibility/on_check |
| PAYR-1123 | The beneficiary is not covered by this payerYou sent the check to a payer that does not cover the beneficiary. The beneficiary must be enrolled in one of its policies first. | Beneficiary is not a covered member for requested payer. Please enroll beneficiary for applicable policy of requested payer and try again. | Coverage eligibility | /v1/coverageeligibility/check/v1/coverageeligibility/on_check |
| PAYR-1201 | Claimed amount is zero or above the wallet balanceThe amount you asked the payer to approve is not allowed. It is zero or less, or more than the balance left in the beneficiary's wallet. A PMJAY family shares one wallet across every member's treatment. | Invalid claimed amount received for case number %s. Please try again with a valid claim amount. Claimed amount should be greater than INR 0 and less than equals to balance wallet amount of the beneficiary. | PreauthorisationClaim | /v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1202 | Speciality code is not in the insurance planAn item in your request names a speciality the payer does not recognise for your hospital. Speciality codes must come from the hospital's insurance plan. | Invalid speciality code received as %s for item %s for case number %s. Please try again with valid data. Speciality code is available as the code of the category for specific cost of plan in isurance plan. | Preauthorisation | /v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1203 | Speciality description does not match the insurance planThe speciality description you sent for a procedure does not match the payer's text for that speciality. Descriptions must come from the hospital's insurance plan, word for word. | Invalid speciality description received as %s for procedure %s for case number %s. Please try again with valid data. Speciality description is available as the display of the category for specific cost of plan in isurance plan. | PreauthorisationClaim | /v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1204 | Procedure code is not in the insurance planYou requested a procedure code that the payer does not offer at your hospital. Procedure codes must come from the hospital's insurance plan. | Invalid procedure code received as %s for case number %s. Please try again with valid data. Procedure code is available as the code of the type for benefit component, of specific cost, of plan in isurance plan. | PreauthorisationClaim | /v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1205 | Procedure description does not match the insurance planThe description you sent for a procedure does not match the payer's text for that procedure code. Descriptions must come from the hospital's insurance plan, word for word. | Invalid procedure description received as %s for procedure %s for case number %s. Please try again with valid data. Procedure description is available as the display of the type for benefit component, of specific cost, of plan in isurance plan. | Preauthorisation | /v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1206 | Procedure type is not acceptedThe type you gave a requested procedure is not one the payer accepts for it. | Invalid procedure type received as %s for procedure %s for case number %s. Please try again with valid data. | Preauthorisation | /v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1207 | Procedure factor is not acceptedThe factor you sent for a requested procedure is not one the payer accepts. | Invalid procedure factor received as %s for procedure %s for case number %s. Please try again with valid data. | Preauthorisation | /v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1208 | Item quantity is not acceptedThe quantity you sent for an item is not one the payer accepts. | Invalid procedure quantity received as %s for item %s for case number %s. Please try again with valid data. Item quantity should be greater than 1. | Preauthorisation | /v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1209 | Item net amount is zero or lessAn item in your request has a net amount of zero or less. Every item must carry a positive amount. | Invalid net amount received as INR %s for item %s for case number %s. Please try again with valid data. Item net amount should be greater than INR 0. | Preauthorisation | /v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1210 | Procedure status is not acceptedThe status you sent for a requested procedure is not one the payer accepts. | Invalid procedure status received as %s for procedure %s for case number %s. Please try again with valid data. | Preauthorisation | /v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1211 | Beneficiary and care plan match no rule at this hospitalThe payer found no rule that lets this beneficiary receive this care plan at your hospital. | Requested beneficary details and careplan details does not match any criteria for processing the case at this hospital. Please try again with valid data. | Preauthorisation | /v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1212 | Enhancement has no approved preauthorisationYou asked to extend a preauthorisation the payer never approved. An enhancement only extends a preauthorisation that is already approved. | No previous preauthorization approved record found for the enhancement request for case number %s. Hence request will not be processed further. Please initiate a new preauthorization. | Preauthorisation | /v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1213 | Enhancement sent while the case is still in progressThe payer is still deciding an earlier request on this case. It accepts no enhancement until that adjudication is complete. | Existing case in progress found for case number %s. Hence enhancement request will not be accepted. Please try after the adjudication is completed for the current case. | Preauthorisation | /v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1214 | Resubmission has no approved preauthorisationYou resubmitted a preauthorisation that the payer holds no approval for. It processes the request no further. | No previous preauthorization approved record found for the resubmission request for case number %s. Hence request will not be processed further. Please initiate a new preauthorization. | Preauthorisation | /v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1215 | Resubmission sent while the case is still in progressThe payer is still deciding an earlier request on this case. It accepts no resubmission until that adjudication is complete. | Existing case in progress found for case number %s. Hence resubmission request will not be accepted. Please try after the adjudication is completed for the current case. | Preauthorisation | /v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1216 | New preauthorisation sent for a case already in progressA request on this case is still in progress with the payer. It accepts no new preauthorisation on the case until that finishes. | Existing case in progress found for case number %s. Hence new preauthorization request will not be accepted. | Preauthorisation | /v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1217 | New preauthorisation sent for a case already approvedThis case already has an approved preauthorisation. To change it, extend it or resubmit it. Do not open a new one. | Previous preauthorization approved record found for the new preauthorization request for case number %s. Hence request will not be processed further. Please initiate enhancement/resubmission. | Preauthorisation | /v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1218 | Query response sent for a case that was not queriedYou answered a query the payer never raised. It holds no queried preauthorisation for this case. | No queried preauthorization record found for the query update request for case number %s. Hence request will not be processed further. | Preauthorisation | /v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1219 | Case is not in the queried stateYou sent a query response for a case the payer has not queried. It processes the request no further. | Case number %s is not queried. Hence query updation request will not be processed further. | Preauthorisation | /v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1220 | Investigation description does not match its codeAn investigation in your request carries a description that does not match its code. | Invalid investigation description received as %s for investigation code %s for case number %s. Please try again with valid data. | PreauthorisationClaim | /v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1221 | Investigation code is not validAn investigation in your request carries a code the payer does not recognise. | Invalid investigation code received as %s for case number %s. Please try again with valid data. | PreauthorisationClaim | /v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1222 | Investigation status is not acceptedThe status you sent for an investigation is not one the payer accepts. | Invalid investigation status received as %s for investigation %s for case number %s. Please try again with valid data. | Preauthorisation | /v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1223 | Investigation attachment is not validThe document attached to an investigation could not be accepted. | Invalid investigation attachment received for investigation %s for case number %s. Please try again with valid data. | Preauthorisation | /v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1224 | Implant description does not match its codeAn implant in your request carries a description that does not match its code. | Invalid implant description received as %s for implant code %s for case number %s. Please try again with valid data. | PreauthorisationClaim | /v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1225 | Implant code is not validAn implant in your request carries a code the payer does not recognise. | Invalid implant code received as %s for case number %s. Please try again with valid data. | PreauthorisationClaim | /v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1226 | Implant status is not acceptedThe status you sent for an implant is not one the payer accepts. | Invalid implant status received as %s for investigation %s for case number %s. Please try again with valid data. | Preauthorisation | /v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1227 | Implant attachment is not validThe document attached to an implant could not be accepted. | Invalid implant attachment received for investigation %s for case number %s. Please try again with valid data. | Preauthorisation | /v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1228 | Implant quantity is not acceptedThe quantity you sent for an implant is not one the payer accepts. | Invalid implant quantity received as %s for implant %s for case number %s. Please try again with valid data. | Preauthorisation | /v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1229 | Implant net amount is not acceptedThe net amount you sent for an implant is not one the payer accepts. | Invalid implant net amount received as INR %s for implant %s for case number %s. Please try again with valid data. | Preauthorisation | /v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1230 | Implant unit price is not acceptedThe unit price you sent for an implant is not one the payer accepts. | Invalid implant unit price received as INR %s for implant %s for case number %s. Please try again with valid data. | Preauthorisation | /v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1231 | Claim already raised for this caseThe final claim for this case is already raised. After that, the payer accepts no preauthorisation request on the case. | Claim has already been raised for case number %s. Hence preauthorization request will not be accepted. | Preauthorisation | /v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1232 | Investigations missing for a private hospitalYour request carries no investigation details. For a private hospital, investigation details are mandatory. | No investigation found for case number %s. Investigation details are mandatory for private hospitals. | Preauthorisation | /v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1233 | Wallet short and patient liability not allowedThe request costs more than the beneficiary's wallet holds. Patient liability does not apply at your hospital, so the shortfall cannot move to the patient. | Patient liability is not aplicable for the hospital and beneficiary do not have enough wallet balance with deficit amount INR %s for the requested preauthorization for case number %s. | Preauthorisation | /v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1234 | No preauthorisation found for the case numberYour request refers to a case the payer holds no preauthorisation for. | No preauthorization record found for case number %s. Hence the request will not be processed. | Preauthorisation | /v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1235 | Wallet balance is insufficientThe beneficiary's wallet does not hold enough balance for this request. A PMJAY family shares one wallet, so treatment for any member draws it down. | Insufficient wallet balance. Hence the request will not be processed. | Preauthorisation | /v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1236 | Claim type is not in-patient or out-patientThe request does not say, in a form the payer accepts, whether this is in-patient or out-patient care. | Invalid claim type (in-patient/out-patient) received. Hence the request will not be processed. | Preauthorisation | /v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1237 | Beneficiary has an active preauthorisation at another hospitalThe beneficiary already has an active preauthorisation at another hospital. The payer refuses a second one while that stays active. | Beneficiary is having an active preauthorization request at %s. Hence the request will not be processed. Kindly inform %s to cancel the active preauthorization request or raise a claim to proceed with current preauthorization. | Preauthorisation | /v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1238 | Beneficiary has an active preauthorisation at your hospitalThe beneficiary already has an active preauthorisation at your hospital. Close it before you open another. | Beneficiary is having an active preauthorization request at this hospital with reference number %s. Hence the request will not be processed. Kindly cancel the active preauthorization request or raise a claim to proceed with current preauthorization. | Preauthorisation | /v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1239 | Hospital configuration not foundThe payer has no configuration for your hospital, so it cannot process the request. | Hospital configuration not found. Please contact support team. | Preauthorisation | /v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1240 | Requested procedures not foundThe payer holds no details for one or more procedures in your request. | No details found for the requested procedures in the system. | Preauthorisation | /v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1241 | Registration date is not validThe patient's registration date in your request is missing or not a date the payer accepts. | Invalid registration date received for case number %s. Hence the request will not be processed. | Preauthorisation | /v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1242 | Registration date format is not validThe patient's registration date is present, but not in a format the payer accepts. | Invalid registration date format received for case number %s. Hence the request will not be processed. | Preauthorisation | /v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1243 | Admission date is not validThe admission date in your request is missing or not a date the payer accepts. | Invalid admission date received for case number %s. Hence the request will not be processed. | Preauthorisation | /v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1244 | Admission date format is not validThe admission date is present, but not in a format the payer accepts. | Invalid admission date format received for case number %s. Hence the request will not be processed. | Preauthorisation | /v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1245 | A scheme rule failedYour request broke one of the payer's scheme rules. The payer can put the rule's own text in the message in place of Rule failure. | Rule failure. | Preauthorisation | /v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1246 | Payer id is not validThe request names the payer with an identifier the payer does not accept. | Invalid payer id received as %s. Please try again with valid payer id. | Preauthorisation | /v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1247 | Payer details not received from the exchangeThe payer could not get the details for the payer id in your request from NHCX, so it stopped processing. | Payer details for payer id %s is not received from HCX for the request. Hence the request will not be processed. | Preauthorisation | /v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1248 | Item code is not validAn item in your request carries a code the payer does not accept. | Invalid item code received as %s for item sequence %s case number %s. Please try again with valid data. | Preauthorisation | /v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1249 | Item sequence is not validAn item in your request carries a sequence number the payer does not accept. | Invalid item sequence received as %s for case number %s. Please try again with valid data. | Preauthorisation | /v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1250 | Policy is not listedThe policy code in your request is not one the payer lists. | Requested policy %s is not listed. Please try again with valid policy code. | Preauthorisation | /v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1251 | No billable treatment planYour request carries nothing the payer can bill against for this case. | No billable treatment plan received for case number %s. Please try again with valid treatment plan data. | Preauthorisation | /v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1252 | Case is not in a state that can be cancelledYou asked to cancel a preauthorisation that is not in a cancellable state. Only a submitted or approved preauthorisation can be cancelled. | Case number %s is not in active preauthorization state with the current status of the case with the payer system is %s. Hence the preauthorization can not be cancelled. Only the cases with current status as preauthorization submitted or preauthorization approved can be cancelled. | Preauthorisation | /v1/preauth/on_submit/v1/preauth/submit/v1/task/on_submit/v1/task/submit |
| PAYR-1253 | Case is already cancelledYou asked to cancel a preauthorisation that is already cancelled. | Case number %s is already cancelled. Hence the preauthorization can not be cancelled again. Only the cases with current status as preauthorization submitted or preauthorization approved can be cancelled. | Preauthorisation | /v1/preauth/on_submit/v1/preauth/submit/v1/task/on_submit/v1/task/submit |
| PAYR-1254 | Treatment guideline questionnaire response missingA procedure you requested needs a completed Standard Treatment Guideline (STG) checklist. Your request did not include the response to it. STGs are mandatory in PMJAY. | Response for STG Questionnaire id %s is mandatory for procedure code %s. Hence the preauthorization request will not be processed as the questionnaire response is not received for procedure code. | Preauthorisation | /v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1255 | Case number already cancelledThe case number in your request belongs to a cancelled preauthorisation. A cancelled case number accepts no further preauthorisation. | Case number %s is already cancelled. Hence no preauthorization request will be accepted for this case number. New preauthorization request needs to be raised with new case/reference number to proceed further. | Preauthorisation | /v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1256 | No biometric authentication and no consent questionnaireA new preauthorisation must prove the patient is present at your hospital. Your request carried neither biometric authentication nor the Authentication Consent Questionnaire response. | Response for Authentication Consent Questionnaire is missing for case number %s. This must be sent if the biometric authentication for patient is not available. For new preauthorization request, either biometric authentication for patient or response for Authentication Consent questionnaire must be sent. Please check/update the insurance plan for the policy for the details of the questionnaire. Please adhere to the response of the coverage eligibility for auth-requirements purpose to check the mandatory documents to be attached with the request | Preauthorisation | /v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1257 | Payment already initiated for the casePayment for this case has already started. A case at that stage can no longer be cancelled. | Payment is initiated for case number %s. Hence the preauthorization can not be cancelled again. Only the cases with current status as preauthorization submitted or preauthorization approved can be cancelled | Preauthorisation | /v1/preauth/on_submit/v1/preauth/submit/v1/task/on_submit/v1/task/submit |
| PAYR-1258 | Payment already cleared for the casePayment for this case is already complete. A paid case can no longer be cancelled. | Payment is accomplished/cleared for case number %s. Hence the preauthorization can not be cancelled again. Only the cases with current status as preauthorization submitted or preauthorization approved can be cancelled | Preauthorisation | /v1/preauth/on_submit/v1/preauth/submit/v1/task/on_submit/v1/task/submit |
| PAYR-1259 | Newborn date of birth missingA newborn case must carry the baby's date of birth. Your request did not. In PMJAY, a newborn with no Member ID yet is treated on a parent's card, as a child linked to the parent. | DOB is missing for new born for the case number (%s) with correlation id as (%s) at (%s) | Preauthorisation | /v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1260 | Newborn date of birth is in the futureThe baby's date of birth in your request is in the future. In PMJAY, a newborn with no Member ID yet is treated on a parent's card, as a child linked to the parent. | DOB cannot be a future date for the case number (%s) with correlation id as (%s) at (%s) | Preauthorisation | /v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1261 | Newborn details are not validThe newborn details in your request are not valid. In PMJAY, a newborn with no Member ID yet is treated on a parent's card, as a child linked to the parent. | Invalid new born details for the case number (%s) with correlation id as (%s) at (%s) | Preauthorisation | /v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1262 | Newborn gender missingA newborn case must carry the baby's gender. Your request did not. In PMJAY, a newborn with no Member ID yet is treated on a parent's card, as a child linked to the parent. | Gender is mandatory for the new born beneficiary | Preauthorisation | /v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1263 | Newborn documents missingA newborn case needs supporting documents, and one is missing from your request. In PMJAY, a newborn with no Member ID yet is treated on a parent's card, as a child linked to the parent. | Documents are mandatory for the new born beneficiary | Preauthorisation | /v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1264 | Newborn documents missingA newborn case needs supporting documents, and one is missing from your request. In PMJAY, a newborn with no Member ID yet is treated on a parent's card, as a child linked to the parent. | Documents are mandatory for the new born beneficiary | Preauthorisation | /v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1265 | Newborn documents missingA newborn case needs supporting documents, and one is missing from your request. In PMJAY, a newborn with no Member ID yet is treated on a parent's card, as a child linked to the parent. | Documents are mandatory for the new born beneficiary | Preauthorisation | /v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1266 | Newborn documents missingA newborn case needs supporting documents, and one is missing from your request. In PMJAY, a newborn with no Member ID yet is treated on a parent's card, as a child linked to the parent. | Documents are mandatory for the new born beneficiary | Preauthorisation | /v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1267 | Active newborn preauthorisation at your hospitalThe beneficiary already has an active preauthorisation for a newborn case at your hospital. Close it before you open another. | Beneficiary is having an active preauthorization request for new born case at this hospital with reference number %s. Hence the request will not be processed. Kindly cancel the active preauthorization request or raise a claim to proceed with current preauthorization | Preauthorisation | /v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1268 | Active newborn preauthorisation at another hospitalThe beneficiary already has an active preauthorisation for a newborn case at another hospital. The payer refuses a second one while that stays active. | Beneficiary is having an active preauthorization request for new born case at %s. Hence the request will not be processed. Kindly inform %s to cancel the active preauthorization request or raise a claim to proceed with current preauthorization | Preauthorisation | /v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1269 | Newborn is older than 6 yearsA newborn case is only for a child aged 6 years or under. The date of birth you sent is more than 6 years ago. | Date of birth received for new born beneficiary exceeds 6 years before the current date. New born cases can be raised only for the beneficiary whose date of birth is within 6 years of current date | Preauthorisation | /v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1270 | Item LM100 sent on a preauthorisationYour preauthorisation includes item LM100. LM100 belongs only on a claim, for a patient who leaves against medical advice. | Item LM100 is not applicable for preauthorization request. This item is expected/mandated only during claim submission if the patient is discharged after/during surgery under LAMA/DAMA category for PMJAY cases. | Preauthorisation | /v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1271 | Consent questionnaire answer missingYour request used the Authentication Consent Questionnaire in place of biometrics, but one of its questions has no answer. | No value received for link id %s for Authentication Consent Questionnaire for preauthorization request. This must be sent if the biometric authentication for patient is not available. For new preauthorization request, either biometric authentication for patient or response for Authentication Consent questionnaire must be sent. Please check/update the insurance plan for the policy for the details of the questionnaire. Please adhere to the response of the coverage eligibility for auth-requirements purpose to check the mandatory documents to be attached with the request. | Preauthorisation | /v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1272 | Biometric user token is not validThe token that proves the patient's biometric authentication is not valid. A user token lasts 30 minutes after verification. | Invalid biometric user token received. Please try again with valid valid biometric details of the beneficiary. For any issues with biometric, please try with Authentication Consent Questionnaire, details for which has been received in response for coverage eligibliity auth-requirements. | Preauthorisation | /v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1273 | Questionnaire not found for the selectionA questionnaire response in your request points at a questionnaire the payer cannot find. | No questionnaire found for the received selection. Please validate the questionnaire url from insurance plan/coverage auth-requirements response. | Preauthorisation | /v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1301 | A claim already exists for this caseThe case you named already has a claim, so the payer will not accept a new claim for it. You receive this code when your system sends a second new claim for one case. | Claim has already been raised for case number %s. Hence new claim request will not be accepted. | Claim | /v1/claim/on_submit/v1/claim/submit |
| PAYR-1302 | No approved preauthorisation for this caseA claim is paid against an approved preauthorisation. The payer found none for the case your claim names, so it will not accept the claim. | No preauthorization approved record found for case number %s. Hence new claim request will not be accepted. | Claim | /v1/claim/on_submit/v1/claim/submit |
| PAYR-1303 | No active claim to update for this caseA query response updates a claim that is still open. The payer found no active claim for the case you named, so it refused the update. | No active claim record found for case number %s. Hence query updation request will not be accepted. | Claim | /v1/claim/on_submit/v1/claim/submit |
| PAYR-1304 | The claim for this case is not under queryYou can answer a query only while the payer is waiting for your answer. The payer holds no queried claim for the case you named. | No claim queried record found for case number %s. Hence query updation request will not be accepted. | Claim | /v1/claim/on_submit/v1/claim/submit |
| PAYR-1305 | The use case is not valid for this caseEvery claim request declares what it is: a new claim or a resubmission. The payer did not accept the use case your request declared for this case. | Invalid usecase requested for case number %s. Please try again with valid usecase. | Claim | /v1/claim/on_submit/v1/claim/submit |
| PAYR-1306 | The procedure is not in the preauthorisation requestA claim is checked item by item against the preauthorisation for the case. Your claim bills a procedure that the preauthorisation request did not contain. | No item found in preauthorization request for procedure %s with item sequence %s for case number %s. Please try again with valid items. | Claim | /v1/claim/on_submit/v1/claim/submit |
| PAYR-1307 | The procedure quantity is not validThe payer checked the quantity on a claimed procedure and did not accept it for this case. | Invalid quantity requested for procedure %s with item sequence %s for case number %s. Please try again with valid quantity. | Claim | /v1/claim/on_submit/v1/claim/submit |
| PAYR-1308 | The procedure is not in the active claimAn update to an open claim, such as a query response, must refer to items already in that claim. Your request names a procedure the active claim does not contain. | No item found in active claim request for procedure %s with item sequence %s for case number %s. Please try again with valid items. | Claim | /v1/claim/on_submit/v1/claim/submit |
| PAYR-1309 | The implant is not in the preauthorisation requestA claim is checked item by item against the preauthorisation for the case. Your claim bills an implant that the preauthorisation request did not contain. | No item found in preauthorization request for implant %s with item sequence %s for case number %s. Please try again with valid items. | Claim | /v1/claim/on_submit/v1/claim/submit |
| PAYR-1310 | The implant quantity is not validThe payer checked the quantity on a claimed implant and did not accept it for this case. | Invalid quantity requested for implant %s with item sequence %s for case number %s. Please try again with valid quantity. | Claim | /v1/claim/on_submit/v1/claim/submit |
| PAYR-1311 | The implant is not in the active claimAn update to an open claim, such as a query response, must refer to items already in that claim. Your request names an implant the active claim does not contain. | No item found in active claim request for implant %s with item sequence %s for case number %s. Please try again with valid items. | Claim | /v1/claim/on_submit/v1/claim/submit |
| PAYR-1312 | The investigation is not in the preauthorisation requestA claim is checked item by item against the preauthorisation for the case. Your claim bills an investigation that the preauthorisation request did not contain. | No item found in preauthorization request for investigation %s with item sequence %s for case number %s. Please try again with valid items. | Claim | /v1/claim/on_submit/v1/claim/submit |
| PAYR-1313 | The investigation quantity is not validThe payer checked the quantity on a claimed investigation and did not accept it for this case. | Invalid quantity requested for investigation %s with item sequence %s for case number %s. Please try again with valid quantity. | Claim | /v1/claim/on_submit/v1/claim/submit |
| PAYR-1314 | The investigation is not in the active claimAn update to an open claim, such as a query response, must refer to items already in that claim. Your request names an investigation the active claim does not contain. | No item found in active claim request for investigation %s with item sequence %s for case number %s. Please try again with valid items. | Claim | /v1/claim/on_submit/v1/claim/submit |
| PAYR-1315 | The procedure was rejected at preauthorisationWhen the payer decided the preauthorisation, it rejected one of the procedures. Your claim bills that procedure anyway, so the payer refused the claim. | Rejected item found for preauthorization for procedure %s with item sequence %s for case number %s. Please try again with valid items. | Claim | /v1/claim/on_submit/v1/claim/submit |
| PAYR-1316 | The investigation was rejected at preauthorisationWhen the payer decided the preauthorisation, it rejected one of the investigations. Your claim bills that investigation anyway, so the payer refused the claim. | Rejected item found for preauthorization for investigation %s with item sequence %s for case number %s. Please try again with valid items. | Claim | /v1/claim/on_submit/v1/claim/submit |
| PAYR-1317 | The implant was rejected at preauthorisationWhen the payer decided the preauthorisation, it rejected one of the implants. Your claim bills that implant anyway, so the payer refused the claim. | Rejected item found for preauthorization for implant %s with item sequence %s for case number %s. Please try again with valid items. | Claim | /v1/claim/on_submit/v1/claim/submit |
| PAYR-1318 | The claim has no requested treatment planThe payer looks for the treatment your hospital requested for the case. It found none in the claim. | No requested treatment plan found for case number %s. Please try again with valid items. | Claim | /v1/claim/on_submit/v1/claim/submit |
| PAYR-1319 | The claim has no requested investigation planThe payer looks for the investigations your hospital requested for the case. It found none in the claim. | No requested investigation plan found for case number %s. Please try again with valid items. | Claim | /v1/claim/on_submit/v1/claim/submit |
| PAYR-1320 | The payer has no details for the requested investigationsThe payer looked up the investigations in your claim and found no details for them in its system. | No details found for the requested investigations in the system. Hence request will not be processed. | Claim | /v1/claim/on_submit/v1/claim/submit |
| PAYR-1321 | The workflow id is not valid for this stepEvery request names its step in the claim cycle with a workflow id. The payer could not process the workflow id your request carried. | Error occurred while processing the request due to invalid workflow id as (%s) | Claim | /v1/claim/on_submit/v1/claim/submit |
| PAYR-1322 | The case is not in a state that accepts this requestThe payer refused your request because of the state of the case. You receive this code in two situations, and the message tells them apart. | No active case found for the given case number. | Claim | /v1/claim/on_submit/v1/claim/submit |
| PAYR-1323 | The beneficiary's wallet balance is too lowEach beneficiary has a wallet: the amount the scheme will still pay for them. The wallet does not hold enough to pay this claim. | Insufficient wallet balance. Hence the request will not be processed. | Claim | /v1/claim/on_submit/v1/claim/submit |
| PAYR-1324 | The discharge stage is not validEvery claim says at what stage the patient was discharged, relative to surgery. The stage in your claim is not a value the payer accepts. | Invalid discharge stage received for case number %s. Hence the request will not be processed. | Claim | /v1/claim/on_submit/v1/claim/submit |
| PAYR-1325 | The admission date is not validThe payer read the admission date in your claim but does not accept it for this case. | Invalid admission date received for case number %s. Hence the request will not be processed. | Claim | /v1/claim/on_submit/v1/claim/submit |
| PAYR-1326 | The discharge date is not validThe payer read the discharge date in your claim but does not accept it for this case. | Invalid discharge date received for case number %s. Hence the request will not be processed. | Claim | /v1/claim/on_submit/v1/claim/submit |
| PAYR-1327 | The admission date is in the wrong formatThe payer could not read the admission date in your claim. The date is not in the format it expects. | Invalid admission date format received for case number %s. Hence the request will not be processed. | Claim | /v1/claim/on_submit/v1/claim/submit |
| PAYR-1328 | The discharge date is in the wrong formatThe payer could not read the discharge date in your claim. The date is not in the format it expects. | Invalid discharge date format received for case number %s. Hence the request will not be processed. | Claim | /v1/claim/on_submit/v1/claim/submit |
| PAYR-1329 | The registration date is not validThe payer read the registration date in your claim but does not accept it for this case. | Invalid registration date received for case number %s. Hence the request will not be processed. | Claim | /v1/claim/on_submit/v1/claim/submit |
| PAYR-1330 | The registration date is in the wrong formatThe payer could not read the registration date in your claim. The date is not in the format it expects. | Invalid registration date format received for case number %s. Hence the request will not be processed. | Claim | /v1/claim/on_submit/v1/claim/submit |
| PAYR-1331 | The receiver is not registered in NHCXEvery request names the participant that should receive it. The receiver in your request is not a registered NHCX participant. | Receiver not registered in NHCX. Please try again with valid receiver details. | Claim | /v1/claim/on_submit/v1/claim/submit |
| PAYR-1332 | The Claim Review Committee request is not validA rejected claim can be sent for review by the Claim Review Committee (CRC). The payer did not accept your request for that review. | Invalid CRC request. | Claim | /v1/claim/on_submit/v1/claim/submit |
| PAYR-1333 | The claim type is not validEvery claim says whether the care was in-patient or out-patient. The payer did not accept the claim type in your claim. | Invalid claim type (in-patient/out-patient) received. Hence the request will not be processed. | Claim | /v1/claim/on_submit/v1/claim/submit |
| PAYR-1334 | The payer has no configuration for your hospitalThe payer could not find a configuration for your hospital in its system. The fix is on the payer's side. | Hospital configuration not found. Please contact support team. | Claim | /v1/claim/on_submit/v1/claim/submit |
| PAYR-1335 | The implant quantity is not validThe payer checked the quantity on an implant in your claim and did not accept it. | Invalid implant quantity received as %s for implant %s for case number %s. Please try again with valid data. | Claim | /v1/claim/on_submit/v1/claim/submit |
| PAYR-1336 | The implant unit price is not validThe payer checked the unit price on an implant in your claim and did not accept it. | Invalid implant unit price received as INR %s for implant %s for case number %s. Please try again with valid data. | Claim | /v1/claim/on_submit/v1/claim/submit |
| PAYR-1337 | The implant net amount is not validThe payer checked the net amount on an implant in your claim and did not accept it. | Invalid implant net amount received as INR %s for implant %s for case number %s. Please try again with valid data. | Claim | /v1/claim/on_submit/v1/claim/submit |
| PAYR-1338 | The implant attachment is not validThe payer checked the attachment on an implant in your claim and did not accept it. | Invalid implant attachment received for investigation %s for case number %s. Please try again with valid data. | Claim | /v1/claim/on_submit/v1/claim/submit |
| PAYR-1339 | The implant status is not validThe payer checked the status on an implant in your claim and did not accept it. | Invalid implant status received as %s for investigation %s for case number %s. Please try again with valid data. | Claim | /v1/claim/on_submit/v1/claim/submit |
| PAYR-1340 | The investigation status is not validThe payer checked the status on an investigation in your claim and did not accept it. | Invalid investigation status received as %s for investigation %s for case number %s. Please try again with valid data. | Claim | /v1/claim/on_submit/v1/claim/submit |
| PAYR-1341 | The investigation attachment is not validThe payer checked the attachment on an investigation in your claim and did not accept it. | Invalid investigation attachment received for investigation %s for case number %s. Please try again with valid data. | Claim | /v1/claim/on_submit/v1/claim/submit |
| PAYR-1342 | A case in progress blocks a new reimbursement requestA reimbursement claim is paid back to the hospital after treatment. The payer is still processing an earlier request on this case, so it refused the new one. | Existing case in progress found for case number %s. Hence new reimbursement request will not be accepted. | Claim | /v1/claim/on_submit/v1/claim/submit |
| PAYR-1343 | A reimbursement was already approved for this caseThe payer already approved a reimbursement for this case. It will not process a second reimbursement request for the same case. | Previous reimbursement approved record found for the new reimbursement request for case number %s. Hence request will not be processed further. | Claim | /v1/claim/on_submit/v1/claim/submit |
| PAYR-1344 | The payer has no details for the requested proceduresThe payer looked up the procedures in your claim and found no details for them in its system. | No details found for the requested procedures in the system. | Claim | /v1/claim/on_submit/v1/claim/submit |
| PAYR-1345 | The procedure status is not validThe payer checked the status on a procedure in your claim and did not accept it. | Invalid procedure status received as %s for procedure %s for case number %s. Please try again with valid data. | Claim | /v1/claim/on_submit/v1/claim/submit |
| PAYR-1346 | The procedure description is not validThe payer checked the description on a procedure in your claim and did not accept it. | Invalid procedure description received as %s for procedure %s for case number %s. Please try again with valid data. | Claim | /v1/claim/on_submit/v1/claim/submit |
| PAYR-1347 | The procedure type is not validThe payer checked the type on a procedure in your claim and did not accept it. | Invalid procedure type received as %s for procedure %s for case number %s. Please try again with valid data. | Claim | /v1/claim/on_submit/v1/claim/submit |
| PAYR-1348 | The procedure factor is not validThe payer checked the factor on a procedure in your claim and did not accept it. | Invalid procedure factor received as %s for procedure %s for case number %s. Please try again with valid data. | Claim | /v1/claim/on_submit/v1/claim/submit |
| PAYR-1349 | The procedure quantity is not validThe payer checked the quantity on a procedure in your claim and did not accept it. | Invalid procedure quantity received as %s for procedure %s for case number %s. Please try again with valid data. | Claim | /v1/claim/on_submit/v1/claim/submit |
| PAYR-1350 | The procedure net amount is not validThe payer checked the net amount on a procedure in your claim and did not accept it. | Invalid procedure net amount received as INR %s for procedure %s for case number %s. Please try again with valid data. | Claim | /v1/claim/on_submit/v1/claim/submit |
| PAYR-1351 | The procedure speciality code is not validThe payer checked the speciality code on a procedure in your claim and did not accept it. | Invalid speciality code received as %s for procedure %s for case number %s. Please try again with valid data. | Claim | /v1/claim/on_submit/v1/claim/submit |
| PAYR-1352 | The beneficiary and care plan do not fit this hospitalThe payer checked the beneficiary and the care plan together for your hospital. The combination matches no criteria for handling the case there. | Requested beneficary details and careplan details does not match any criteria for processing the case at this hospital. Please try again with valid data. | Claim | /v1/claim/on_submit/v1/claim/submit |
| PAYR-1353 | The care plan id is not validThe care plan id in your claim is not one the payer accepts. | Invalid careplan id received. Please try again with valid careplan id. | Claim | /v1/claim/on_submit/v1/claim/submit |
| PAYR-1354 | The claim failed a payer ruleThe claim broke one of the payer's rules. The message does not say which rule. | Rule failure. | Claim | /v1/claim/on_submit/v1/claim/submit |
| PAYR-1355 | The payer has no details for the requested implantsThe payer looked up the implants in your claim and found no details for them in its system. | No details found for the requested implants in the system. Hence request will not be processed. | Claim | /v1/claim/on_submit/v1/claim/submit |
| PAYR-1356 | The wallet is short and the patient cannot pay the differenceThe beneficiary's wallet does not cover the amount you claimed. Your hospital is not allowed to charge the patient the difference, so the payer refused the claim. | Patient liability is not aplicable for the hospital and beneficiary do not have enough wallet balance with deficit amount INR %s for the requested preauthorization for case number %s. | Claim | /v1/claim/on_submit/v1/claim/submit |
| PAYR-1357 | The admission date is after the discharge dateYour claim says the patient was admitted after they were discharged. The payer refused it. | Admission date cannot be after the discharge date. Hence request will not be processed. Please correct the data and try again. | Claim | /v1/claim/on_submit/v1/claim/submit |
| PAYR-1358 | The patient was registered too long after admissionThe scheme allows a patient to be registered only within a set number of days after admission. Your claim gives a registration date outside that window. | Registration of the patient is allowed maximum upto %s days after admission. Hence request will not be processed. Please correct the data and try again. | Claim | /v1/claim/on_submit/v1/claim/submit |
| PAYR-1359 | The claim has no billable treatment planThe payer found no treatment item it can bill in your claim for this case. | No billable treatment plan received for case number %s. Please try again with valid treatment plan data. | Claim | /v1/claim/on_submit/v1/claim/submit |
| PAYR-1360 | An item code is not validThe payer did not accept the code on one of the items in your claim. | Invalid item code received as %s for item sequence %s case number %s. Please try again with valid data. | Claim | /v1/claim/on_submit/v1/claim/submit |
| PAYR-1361 | An item sequence is not validEach item in a claim has a sequence number. The payer did not accept one of yours. | Invalid item sequence received as %s for case number %s. Please try again with valid data. | Claim | /v1/claim/on_submit/v1/claim/submit |
| PAYR-1362 | A discharge against medical advice needs the LM100 procedureSometimes a patient leaves before or during surgery against medical advice. For PMJAY claims, the claim must then carry the LM100 procedure, and your claim did not. | No procedure with code LM100 received with 'Requested' status for case number %s. Please try again with valid data. For PMJAY claims, if case comes under LAMA/DAMA scenario with beneficiary being discharged before surgery or during surgery, procedure with code LM100 is mandatory. Only this procedure code will be accepted for LAMA/DAMA case, and all other previous preauthorization approved items will get disqualified for the claim submission | Claim | /v1/claim/on_submit/v1/claim/submit |
| PAYR-1363 | No biometric authentication and no consent questionnaire at dischargeA new claim needs proof that the patient was present at discharge. That proof is biometric authentication, or a response to the Authentication Consent Questionnaire. Your claim had neither. | Response for Authentication Consent Questionnaire is missing for case number %s. This must be sent if the biometric authentication for patient is not available during discharge. For new claim request, either biometric authentication for patient during discharge, or response for Authentication Consent questionnaire must be sent. Please check/update the insurance plan for the policy for the details of the questionnaire. | Claim | /v1/claim/on_submit/v1/claim/submit |
| PAYR-1364 | A consent questionnaire answer is emptyYour claim carries an Authentication Consent Questionnaire response, but one question in it has no answer. | No value received for link id %s for Authentication Consent Questionnaire for claim request. This must be sent if the biometric authentication for patient is not available during discharge. For new claim request, either biometric authentication for patient during discharge, or response for Authentication Consent questionnaire must be sent. Please check/update the insurance plan for the policy for the details of the questionnaire. | Claim | /v1/claim/on_submit/v1/claim/submit |
| PAYR-1365 | The standard treatment guideline response is missingSome procedures come with a standard treatment guideline (STG) questionnaire. A procedure in your claim needs one, and the claim did not include the response. | Response for STG Questionnaire id %s is mandatory for procedure code %s. Hence the preauthorization request will not be processed as the questionnaire response is not received for procedure code. | Claim | /v1/claim/on_submit/v1/claim/submit |
| PAYR-1366 | The biometric user token is not validBiometric authentication gives your system a user token for the patient. The token sent with your claim is not valid. | Invalid biometric user token received. Please try again with valid biometric details of the beneficiary. For any issues with biometric, please try with Authentication Consent Questionnaire for discharge, details for which has been received in insurance plan. | Claim | /v1/claim/on_submit/v1/claim/submit |
| PAYR-1367 | No biometric record for a cycle dateA cyclic procedure, such as dialysis, is given in repeated cycles. Each cycle needs its own biometric authentication, and the payer found none for one of your dates. | No biometric records found for the beneficiary for %s. Please ensure correctness of biometric authentication date for the day for cyclic procedure %s. | Claim | /v1/claim/on_submit/v1/claim/submit |
| PAYR-1368 | Cycle information is missing for some cyclesA cyclic procedure is claimed once, after the last cycle. The claim must describe every cycle, and yours describes fewer than it requests. | %s units of cycle information received for procedure code %s with item sequence %s. Cycle information should be sent for all the requested/processed cycles. | Claim | /v1/claim/on_submit/v1/claim/submit |
| PAYR-1369 | Two biometric authentications on one date for a cyclic procedureA cyclic procedure allows one cycle per day. Your claim gives two or more biometric authentications on the same date for one procedure. | Biometric authentication cannot be performed more than once on the same date. Multiple biometric authentication information has been provided for same date for cyclic procedure %s. Hence case will not be processed. Please check and update biometric authentication execution dates and try again. | Claim | /v1/claim/on_submit/v1/claim/submit |
| PAYR-1370 | A supporting detail has an invalid start dateOne entry in your claim's supporting information has a start date the payer does not accept. | Received invalid start date as %s for supporting details with item sequence %s. Please try again with valid start date. | Claim | /v1/claim/on_submit/v1/claim/submit |
| PAYR-1401 | The policy is not allowed for your hospitalYou asked a payer, through NHCX, for the insurance plan of a policy. The policy is not applicable to your hospital, so the payer returns no plan. | <policy_code> policy not allowed for the hospital. Please reach out to technical support team. | Insurance plan | /v1/insuranceplan/on_request/v1/insuranceplan/request |
| PAYR-1402 | The payer has no policy with the code you requestedYou asked a payer, through NHCX, for the insurance plan of a policy. The payer found no policy with that code in its system. It stops processing the request. | Requested policy <policy_code> found not be associated with any payer for insurance plan request. Hence request will not be processed. | Insurance plan | /v1/insuranceplan/on_request/v1/insuranceplan/request |
| PAYR-1403 | The renewal does not belong to the requested policyYou asked a payer, through NHCX, for the insurance plan of a policy and a renewal of it. The payer found no such renewal under that policy. It stops processing the request. | Requested renewal <renewal_code> found not be associated with requested policy <policy_code> for insurance plan request. Hence request will not be processed. | Insurance plan | /v1/insuranceplan/on_request/v1/insuranceplan/request |
| PAYR-1404 | No treatment is configured for the policy under any specialityYou asked a payer, through NHCX, for the insurance plan of a policy. The payer has no speciality configured for that policy. With no speciality there is no treatment to list, so it returns no plan. | No treatment provided for policy <policy_code> under any speciality. Please reach out to technical support team. | Insurance plan | /v1/insuranceplan/on_request/v1/insuranceplan/request |
| PAYR-1405 | The payer has no enrolled hospital for your HFR id or sender codeYou asked a payer, through NHCX, for an insurance plan. The payer looked your hospital up and found no enrolled hospital. It checked your HFR id and your sender code. With no hospital record, it cannot build a plan for you. | No enrolled hospital found for HFR id <hfr_id> or sender id <sender_code>. Please reach out to technical support team. | Insurance plan | /v1/insuranceplan/on_request/v1/insuranceplan/request |
| PAYR-1406 | An earlier insurance plan request for the same policy is still runningYour hospital asked a payer, through NHCX, for the insurance plan of a policy. An earlier request from your hospital for the same policy is still in progress. The payer refuses the new one until the earlier one finishes. | Existing request with correlation id %s is in progress with the payer. Hence this request will not be accepted until the execution for previous request is complete. Please wait for 15 - 60 minutes to allow the execution of previous requests. For further assistance, please reach out to technical support team. | Insurance plan | /v1/insuranceplan/on_request/v1/insuranceplan/request |
| PAYR-1501 | The surgery date entry carries the wrong kind of valueYour preauthorisation or claim lists the surgery date as a supporting information entry. The PMJAY payer found that entry holding the wrong kind of value. It reads the surgery date only from a timing, meaning a date or a period, or from a string. It refused the request. | Value type received as %s for category - ONS and code - PSP for item with sequence %s in supporting info in claim resource. In supporting info list, item with category - ONS and code - PSP combination is used to get the surgery date. So the surgery date should be sent as timing (date or period) or as a string value, adhering to the NRCES standards, with the category - ONS and code - PSP. | Bundle structure | /v1/claim/on_submit/v1/claim/submit/v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1502 | The admission date entry carries the wrong kind of valueYour preauthorisation or claim lists the admission date as a supporting information entry. The PMJAY payer found that entry holding the wrong kind of value. It reads the admission date only from a timing, meaning a date or a period, or from a string. It refused the request. | Value type received as %s for category - ONS and code - ADDD for item with sequence %s in supporting info in claim resource. In supporting info list, item with category - ONS and code - ADDD combination is used to get the admission date. So the admission date should be sent as timing (date or period) or as a string value, adhering to the NRCES standards, with the category - ONS and code - ADDD. | Bundle structure | /v1/claim/on_submit/v1/claim/submit/v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1503 | The death date entry carries the wrong kind of valueYour claim lists the death date as a supporting information entry. The PMJAY payer found that entry holding the wrong kind of value. It reads the death date only from a timing, meaning a date or a period, or from a string. It refused the request. | Value type received as %s for category - ONS and code - DTM for item with sequence %s in supporting info in claim resource. In supporting info list, item with category - ONS and code - DTM combination is used to get the death date. So the death date should be sent as timing (date or period) or as a string value, adhering to the NRCES standards, with the category - ONS and code - DTM. | Bundle structure | /v1/claim/on_submit/v1/claim/submit |
| PAYR-1504 | The case remarks in your query response are not textThe payer queried your preauthorisation or claim, and your system answered. Your answer carries overall case remarks as a supporting information entry. The PMJAY payer reads those remarks only as a string. Your entry held another kind of value, so it refused the answer. | Value type received as %s for category - NMI and code - CQD for item with sequence %s in supporting info in claim resource. In supporting info list, item with category - NMI and code - CQD combination is used to get the overall case remarks for query response. So the case remarks for query response should be sent as a string value, adhering to the NRCES standards, with the category - NMI and code - CQD. | Bundle structure | /v1/claim/on_submit/v1/claim/submit/v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1505 | A questionnaire response is attached under the wrong category or codeYour preauthorisation or claim attaches a questionnaire response through a supporting information entry. The entry points at a QuestionnaireResponse resource in your bundle. The PMJAY payer accepts that link only under two category and code pairs. Yours used another pair, so it refused the request. | Category received as %s and code received as %s for item with sequence %s in supporting info in claim resource, where the reference value redirects to Questionnaire Response resource in the FHIR bundle. To include a policy/case level Questionnaire Response, in supporting info list there should be an entry with category - INF and code - ODN , and the value as reference. This reference value should refer to a resource of Questionnaire Response in the FHIR bundle. To include response for any STG questionnaire, in supporting info list there should be an entry with category - STG, and the value as reference | Bundle structure | /v1/claim/on_submit/v1/claim/submit/v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1506 | The newborn's gender is not validYour preauthorisation or claim is for a newborn under PMJAY. The newborn has no scheme membership of its own yet. The parent is the main patient, and the child is a separate, linked patient. | Invalid gender received for new born patient. Please try agian with valid gender data as it is mandatory for PMJAY in new born case. Please refer to the valid gender values at https://hl7.org/fhir/R4/valueset-administrative-gender.html | Bundle structure | /v1/claim/on_submit/v1/claim/submit/v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1507 | The newborn's date of birth is not validYour preauthorisation or claim is for a newborn under PMJAY. The newborn has no scheme membership of its own yet. The parent is the main patient, and the child is a separate, linked patient. | Invalid date of birth received for new born patient. Please try agian with valid date of birth as it is mandatory for PMJAY in new born case. | Bundle structure | /v1/claim/on_submit/v1/claim/submit/v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1508 | The newborn link does not lead to a Patient resourceYour preauthorisation or claim is for a newborn under PMJAY. The newborn has no scheme membership of its own yet. The parent is the main patient, and the child is a separate, linked patient. | Invalid resource received for new born patient for url %s. Please try agian with valid Patient resource for the link reference as linked Patient resource is mandatory for PMJAY in new born case | Bundle structure | /v1/claim/on_submit/v1/claim/submit/v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1509 | The newborn's proof of birth attachment is not validYour preauthorisation or claim is for a newborn under PMJAY. The newborn has no scheme membership of its own yet. The parent is the main patient, and the child is a separate, linked patient. | Invalid attachment received for new born patient. Please try agian with valid attachment as attachment is mandatory for PMJAY in new born case | Bundle structure | /v1/claim/on_submit/v1/claim/submit/v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1510 | A parameter code in your request is not validThe PMJAY payer checked the parameters in your request and found a code it does not accept. The message does not say which parameter. Your system has to find it before it resends. | Invalid parameter code received. Please check and try again with a valid parameter code | Bundle structure | /v1/insuranceplan/on_request/v1/insuranceplan/request/v1/task/on_submit/v1/task/submit |
| PAYR-1511 | A parameter value in your request is not validThe PMJAY payer checked the parameters in your request and found a value it does not accept. The message does not say which parameter. Your system has to find it before it resends. | Invalid parameter value received. Please check and try again with a valid parameter value | Bundle structure | /v1/insuranceplan/on_request/v1/insuranceplan/request/v1/task/on_submit/v1/task/submit |
| PAYR-1512 | A patient reference does not lead to a Patient resourceA resource in your FHIR bundle refers to the patient. The PMJAY payer followed that reference and did not find a valid Patient resource. It refused the request. | Invalid resource received for patient for url %s. Please try agian with valid Patient resource for the reference | Bundle structure | /v1/claim/on_submit/v1/claim/submit/v1/coverageeligibility/check/v1/coverageeligibility/on_check/v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1513 | A diagnosis is not sent as a coded conceptYour FHIR bundle lists a diagnosis. The PMJAY payer accepts a diagnosis only as a coded concept: a code, its code system and a display text. Yours arrived in another form, so it refused the request. | Invalid diagnosis received in DiagnosisComponent. In DiagnosisComponent, diagnosis should be sent as CodeableConcept. Please try agian with valid data | Bundle structure | /v1/claim/on_submit/v1/claim/submit/v1/coverageeligibility/check/v1/coverageeligibility/on_check/v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1514 | The discharge information entry does not name a discharge stageYour claim carries discharge information as a supporting information entry. The PMJAY payer reads it as text naming the discharge stage. Your entry held another kind of value, so it refused the claim. | Value type received as %s for category - DIS for item with sequence %s in supporting info in claim resource. In supporting info list, item with category - DIS is used to get the discharge related information. So the discharge information should be sent as string value, with value representing discharge stage (After Surgery / Before Surgery / During Surgery), with the category - DIS and code - DTH/LAMA/DAMA/DTM | Bundle structure | /v1/claim/on_submit/v1/claim/submit |
| PAYR-1515 | An organisation in your bundle has no nameYour FHIR bundle includes an Organization resource for a hospital or a payer. The PMJAY payer requires every organisation to carry a name. The organisation at the reference in the message had no valid name, so it refused the request. | Invalid name received for organization resource with url %s. Name is mandatory for organization resource. Please refer to https://www.nrces.in/ndhm/fhir/r4/StructureDefinition-Organization.html | Bundle structure | /v1/claim/on_submit/v1/claim/submit/v1/coverageeligibility/check/v1/coverageeligibility/on_check/v1/preauth/on_submit/v1/preauth/submit |
| PAYR-1516 | The payer cannot match your error response to any messageYour system sent an error response to the PMJAY payer through NHCX. The payer finds the message your error response answers by three identifiers. It found no message with that combination, so it refused your error response. | No event found for api-caller-id %s and correlation id %s for sender code %s. Hence error response willnot be accepted. | Bundle structure | /v1/communication/on_request/v1/communication/request/v1/error |
| PAYR-1517 | Your error was sent encrypted instead of as a protocol responseYour system sent the PMJAY payer an error through NHCX. An error travels in the ProtocolResponse structure, with its details in clear headers. Yours arrived in the encrypted structure, typed JWEPayloadResponse. The payer does not read errors in that form. | Invalid error structure received for NHCX error. Protocol response structure is expected, but received JWEPayloadResponse. | Bundle structure | /v1/communication/on_request/v1/communication/request/v1/error |
| PAYR-1518 | Your Task resource carries no input parametersYour request carries a Task resource. A Task tells the payer what you want, and names the policy or case through its inputs. Yours had no inputs, so the PMJAY payer refused it. | No input parameters received for task resource. Input parameters are expected for task resource, but not received. Please try again with valid data. | Bundle structure | /v1/communication/on_request/v1/insuranceplan/on_request/v1/insuranceplan/request/v1/task/on_submit/v1/task/submit |
| PAYR-1519 | A Task input parameter has no typeYour request carries a Task resource with inputs. Each input must say what kind of input it is, through a type code. At least one of yours had no type, so the PMJAY payer refused the request. | No type found for task input parameters. Hence request will not be processed further. Please refer to https://www.nrces.in/ndhm/fhir/r4/StructureDefinition-Task.html | Bundle structure | /v1/communication/on_request/v1/insuranceplan/on_request/v1/insuranceplan/request/v1/task/on_submit/v1/task/submit |
| PAYR-1520 | The communication reference does not lead to a Communication resourceThe payer asked your hospital for more information with a communication request, through NHCX. Your system answered with a Task that points at a Communication resource. The PMJAY payer followed that reference and did not find a valid Communication, so it refused the answer. | Invalid resource received for communication for url %s. Please try agian with valid Communication resource for the reference. | Bundle structure | /v1/communication/on_request/v1/communication/request |