HCX registries will act as a source of truth for participant information on the platform. These may be extended from/link to already existing registries in the ecosystem, e.g. registry may extend from National Health Facility Registry provided by NHA. The benefit of extending from an existing registry would be:
- Easy maintenance of base data at the source registry
- The extended registry only needs to maintain additional/supplementary information pertaining to its use case
- Better interoperability
Keeping with the key design principles listed above, registries on HCX will strive to be minimalistic, self-maintainable, support non-repudiability, accessible through OpenAPIs, Extensible and evolvable, and designs for data privacy and security. All registries on the HCX platform will minimally provide the following APIs:
Please note that onboarding of the actors in the registry will take place through workflows defined by domain groups and may change over time, therefore the access to the data modification APIs would be controlled by the HCX instance provider and used as part of the onboarding process.
This registry stores key details about the participants on the exchange who can exchange data through it. It may link with data on the HFR registry and will have fields necessary to facilitate claims data exchange with providers. Proposed attributes of the registry are:
Machine-readable unique identifier of the participant, generated by the HCX instance.
Health Facility Registry code for the participant - used to link the provider record to HFR record
A human-readable name for the participant
Roles assigned to the participant as per the definition in the domain specifications. This will be used for access control.
The physical address of the participant including its geolocation
Email ids for claims related communication
Landline number of the participant
Mobile number for claims related communication
Current status of the participant on the instance. Can be:
URI/file path to the JWT signing certificate
URI/file path to encryption certificate
Default endpoint to make API calls
Default payment details:
While the exchange protocol by itself may not need to focus on the human user (as the exchange is between systems), operational management of the exchange infrastructure may require administrative infrastructure that may necessitate a registry for operational users from organizations running HCX as well as participating organizations. Following are the proposed attributes for the User registry:
Machine-readable user-id as the unique identifier generated by the HCX instance.
Human readable use name - something like email id
Identification pin if needed to be set
Mobile number of the user
Email Id of the user
An array of additional roles (apart from being a base/citizen user which is assigned to every user by default) assigned to the user
Base tenant of the admin user
User ID in the source system
Please review the proposed participant registry details and provide comments on whether the given attributes are a minimal sufficient list for the functioning of the HCX? What other attributes may be included? What should be the cardinality of those attributes?
Please review the proposed participant registry details and any other attributes advised in Question 2 above. Please provide your comments on the data privacy or security aspect of these attributes?
Please review the proposed user registry details and provide comments on whether the given attributes are a minimal sufficient list for the functioning of the HCX? What other attributes may be included? What should be the cardinality of those attributes?
Please review the proposed user registry details and any other attributes advised in Question 3 above. Please provide your comments on the data privacy or security aspect of these attributes?