Notifications
Specifications to enable participant notifications
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 participating entities in a safe and secure manner. Example of such information could be onboarding/deboarding 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 patient.
Key benefits of such a notification infrastructure would be:
Operational efficiency
Transparency
Trust in ecosystem
Better user experience
Improved support and risk mitigation
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:
Classification of key notification types
Notification templates/data structure
Notification registry (a set of predefined notifications mapped with access control)
Subscribe/Unsubscribe APIs
Notify APIs
Guidelines for policies related to notification capabilities
As part of the overall HCX specifications, the Notification delivery specifications are designed keeping in mind the overall HCX design principles.
Last updated