OpenHIE Health Worker Registry (HWR)
The system shall support the ability to set up and manage users, permissions for reading data, writing data (posting, validation, publishing), viewing data and system administration. The Health Worker Registry serves as the central authority for maintaining the unique identities of health workers within a country. The Health Worker Registry is a database containing a minimum dataset of details of all health workers working in both the public and private sectors. With multiple and disparate sources of data on health workers, it is a complex task to pull together and maintain a master and canonical list of all health workers in a country. The health worker registry seeks to reduce the complexity of this task by:
Pulling the minimum dataset of health workforce information from the various source data systems.
Merging the source data systems into an authoritative registry of health workers according to a data governance policy.
Allowing queries of health worker information by client systems.
See also Non-Functional Requirements.
OpenHIE HWR Workflow Requirements
A core principle of the OpenHIE architecture is to allow the various infrastructure services (such as the HWR) to be interchangeable. To support this, the OpenHIE Standards and Profiles used by the Health Worker Registry are outlined in the workflows below.
To be an OHIE HWR component, the HWR application must be able to support the OHIE workflows listed below. Implementations may support only the workflows needed to support their use case:
# | HWR Workflows (Described in detail in the later part of this document) | Recommendation/ Requirement |
Requirement (One of HWWF-1 or HWWF-2 must be supported) | ||
Requirement (One of HWWF-1 or HWWF-2 must be supported) | ||
Recommendation | ||
Requirement |
OpenHIE HWR Functional Requirements
# | HWR Functional Requirement | Recommendation/ Requirement |
HWRF-1 | The system shall support the ability to retain received updates from source data systems. | Required |
HWRF-2 | The system shall support the ability to respond to queries on health worker data that has been stored. | Required |
HWRF-3 | The system shall support the ability to query (API) source data systems for updates to health worker data. | Required |
HWRF-4 | The system should be able to send updates to upstream data repositories (such as an InterLinked Registry). | Recommended |
HWRF-5 | The system should have flexible standards-based APIs, based on CSD or mCSD | Required |
HWRF-6 | The system should support the ability to maintain old versions of health worker data when it has been updated. (Audit log) | Recommended |
HWRF-7 | Recommended | |
HWRF-8 | The system should be able to allow for configuration of key attributes that support the context of the implementation | Required |
HWFR - 9 | The system shall support the ability to set up and manage users, permissions for reading data, writing data (posting, validation, publishing), viewing data and system administration. | Required |
HWRF - 10 | The system shall generate standard reports inline with the core HW attributes. | Required |
HWRF - 11 | The system should generate customizable reports inline with the core HW attributes. | Recommended |
HWRF - 12 | The system should support the ability to do bulk imports. | Recommended |
Last updated