OpenHIE Health Management Information System (HMIS)
A Health Management Information System (HMIS), also called a Routine Health Information System, facilitates the collection of periodic health service delivery and public health indicators from a variety of information systems and the effective use of information at facility, district, and higher levels to help improve health care outcomes.
See also Non-Functional Requirements.
OpenHIE HMIS Workflow Requirements
The following workflow is currently supported, and an FHIR-based message is emerging.
# | HMIS Workflows (Described in detail in the later part of this document) | Recommendation / Requirement |
Required |
OpenHIE HMIS Functional Requirements
# | HMIS Functional Requirements | Recommendation / Requirement |
HMISF-1 | An HMIS shall act as a datastore for integrated health system data which can be used for better decision making in the health system. | Required |
HMISF-2 | An HMIS should provide mechanisms (preferably web based) for data entry. | Recommended |
HMISF-3 | An HMIS should provide mechanisms to improve the quality and validity of data (smart forms, validation rules, etc.). | Recommended |
HMISF-4 | An HMIS should provide standard interfaces for the importing of data from other systems (e.g., ADX, FHIR). | Recommended |
HMISF-5 | An HMIS should support the use of an accurate list of health facilities and their geographic and administrative distribution. | Recommended |
HMISF-6 | An HMIS should provide interfaces for sharing health facility information with other systems (facility registry). | Recommended |
HMISF-7 | To support its primary function of data use, an HMIS should:
| Recommended |
Last updated