HCX Protocol
v0.9
v0.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
  • Context
  • Abstract

Was this helpful?

Edit on GitHub
  1. Technical Specifications
  2. Open Protocol
  3. Claims Data Exchange (HCX) Protocol
  4. Message Flows*

Notifications

Specifications to enable participant notifications on HCX

Context

As a facilitator of the value between various participating entities, while HCX is envisioned to help different participants directly exchange the claims related information in standardised manner, the network would benefit further if the relevant information about such exchanges could also be shared with other interested/relevant participants in a safe and secure manner. Example of such information could be onboarding/de-boarding of participants, information about participant system maintenance/upgrades, availability of new functionality, or specific information needed by a participant on a particular claims use case - e.g. Regulator (IRDA/IIB) or Sponser (NHA/SHA/Corporate/Community) needing to know about completion of a claims cycle, or an ISNP needing to know status of a claim on behalf of its beneficiaries.

Key benefits of such a notification infrastructure would be:

  1. Operational efficiency

  2. Transparency

  3. Trust in ecosystem

  4. Better user experience

  5. Better participant support

This section of the specification describes such needs and proposed enhancements to facilitate such information exchange in the network.

Abstract

Event driven notification can enable valuable near real time information for the HCX network participants in a privacy preserving and secure manner. This proposal outlays the enhancements in the protocol to detail the approach and proposed APIs and data structures to achieve such notification capabilities. Key capabilities proposed to be included are:

  1. Classification of key notification types

  2. Notification templates/data structure

  3. Notification registry (a set of predefined notifications mapped with access control)

  4. Subscribe/Unsubscribe APIs

  5. Notify APIs

  6. Guidelines for policies related to notification capabilities

Following sub-section provides details on the key notification categories and their triggers.

PreviousThird party Information sharingNextCategories

Last updated 1 year ago

Was this helpful?

As part of the overall HCX specifications, the Notification delivery specifications are designed keeping in mind the HCX design principles listed .

here