OpenHIE Architecture Specification
Staging
Staging
  • Specification Overview
  • How to use the Specification
  • Architecture Specification
    • Architecture
    • Architectural Principles
    • Standards and Profiles
  • OpenHIE Component Specifications
    • Non-Functional Requirements
    • Client Registry (CR)
    • OpenHIE Facility Registry (FR)
    • OpenHIE Finance and Insurance Service (FIS)
    • OpenHIE Health Management Information System (HMIS)
    • OpenHIE Health Worker Registry (HWR)
    • OpenHIE Interoperability Layer (IOL)
    • OpenHIE Logistics Management Information System (LMIS)
    • OpenHIE Product Catalogue (PC)
    • OpenHIE Shared Health Record (SHR)
    • OpenHIE Terminology Service (TS)
    • Point-Of-Care Systems
  • Workflow (Exchange) Specification
    • Aggregate Reporting Workflows
      • Export Aggregate Data
      • Validate and Save Aggregate Data
    • Alerting / Sending Reminders or Information
      • Send Client Alert Workflow
      • Send Health Worker Alert Workflow
    • Care Services Discovery
      • Query Health Worker and/or Facility Records Workflow
      • Query Care Services Records Workflow
      • Search Care Services Workflow
      • Request Care Services Updates Workflow
    • Laboratory Work Flows
      • Order Laboratory Test
      • Report Lab Results
    • Patient Identity Management Workflows
      • Create Patient Demographic Record Workflow
      • Update Patient Demographic Record Workflow
      • Query Patient Demographic Records by Identifier Workflow
      • Query Patient Demographic Records by Demographics Workflow
    • Shared Health Record
      • Save Patient-level Clinical Data Workflow
      • Query Patient-level Clinical Data Workflow
    • Terminology Service Workflows
      • Expand Value Set
      • Translate Code
      • Verify Code Existence
      • Verify Code Membership
      • Query Value Set
      • Query Code Systems
      • Query Concept Maps
      • Lookup Code
    • Vaccine Workflows
    • OpenHIE Finance and Insurance Services Workflows
      • HFW-001: Enroll Beneficiary
      • HFW-002: Query Beneficiary
      • HFW-003: Check Coverage Eligibility
      • HFW-004: Claiming
      • HFW-005: Claim Tracking
  • How to Provide Feedback and Input
  • Change Log and Versioning
Powered by GitBook
On this page
  • OpenHIE HMIS Workflow Requirements
  • OpenHIE HMIS Functional Requirements
  1. OpenHIE Component Specifications

OpenHIE Health Management Information System (HMIS)

PreviousOpenHIE Finance and Insurance Service (FIS)NextOpenHIE Health Worker Registry (HWR)

Last updated 3 years ago

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 .

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:

  • Be able to further aggregate and analyze data (e.g., provide annual report from monthly data)

  • An HMIS should offer an interface to query its data in a flexible way across different dimensions (analytics API)

  • An HMIS should provide customized graphic visualizations of data

Recommended

Non-Functional Requirements
HMISWF-1
Validate and Save Aggregate Data