HCX Protocol
v0.9
v0.6v0.7v0.8v0.7.1v0.9
v0.9
v0.6v0.7v0.8v0.7.1v0.9
  • Summary*
  • Glossary*
  • Context
  • Introduction to HCX*
  • Technical Specifications
    • Open Protocol
      • Registries*
        • QR Code Specifications*
      • Claims Data Exchange (HCX) Protocol
        • Message Flows*
          • Primary Message Flow
          • Additional Message Flows
            • Redirect
            • Forward
            • Intra Cycle Communication*
              • Seeking Supporting Information
              • Seeking Beneficiary Consent
              • Seeking Account Information
            • Relay
            • Third party Information sharing
          • Notifications
            • Categories
            • List of key topics
        • Message Structure
        • API Specifications*
          • Registry APIs
          • Primary Flow APIs
          • Supporting APIs
          • Notification APIs
        • Error Handling
      • Data Security and Privacy
        • Transport Security
        • Message Security and Integrity
        • API Security*
      • Audit and Reporting
    • Digital Network Policies
  • Domain Specifications
    • Domain Data Models
      • Handling Attachments
      • Handling Processing Errors
    • Terminologies
    • Domain Specific Languages (DSLs)
    • FHIR Implementation Guide*
  • Business Policy Specifications
    • Access Control (Roles)*
    • Guidelines for Participant Onboarding*
      • Sandbox process
      • Production onboarding (Go live)*
      • Potential De-boarding scenarios
    • Guidelines for Grievance Redressal
      • Scope of disputes
      • Involved participants
      • Guideline process for dispute resolution
      • Guidelines for leveraging FTA
      • Next steps
    • Guidelines for SLAs and ecosystem satisfaction
    • Guidelines for Operating charges
    • Guidelines for Beneficiary Authentication by Providers/Payors
    • Guidelines for Event audits
    • Reference Templates
      • HCX - Terms of use
      • Payer-Provider addendum
      • Payer-Policyholder addendum
    • Next steps
  • Use cases*
    • OPD
      • Typical Workflows
        • Cashless
        • Reimbursement
      • Mapping to the HCX protocol
        • Cashless
        • Reimbursement
    • IPD
      • Typical Workflows
        • Cashless
        • Reimbursement
      • Mapping to the HCX protocol
        • Cashless
        • Reimbursement
    • Implementation Considerations
  • Contributing to the protocol
  • Future Focus Areas*
Powered by GitBook
On this page

Was this helpful?

Edit on GitHub
  1. Domain Specifications
  2. Domain Data Models

Handling Processing Errors

Handling domain/business processing related errors

PreviousHandling AttachmentsNextTerminologies

Last updated 1 year ago

Was this helpful?

While the protocol related errors are expected to be handled as per , this section provides detail on responding when there are errors during business processing of the request.

An error in business processing will be responded using corresponding on_* callback containing corresponding response FHIR profile with following additional constraints:

  1. x-hcx-status needs to be set to "response.error"

  2. Error code in x-hcx-errordetails header needs to be set to "ERR_DOMAIN_PROCESSING" as mentioned in in the Error Response section in the Technical Specifications.

  3. Within the corresponding response FHIR profile {response_resource}

    1. Error status need to be indicated in {response_resource}.outcome attribute

    2. Details of error need to be carried in the corresponding {resopnse_resource}.error attribute.

Error Response section in the Technical Specifications
Recipient error scenarios table