Want create site? Find Free WordPress Themes and plugins.

Integration Platform Architecture (Explained)

Integration Platform Architecture

The integration platform architecture which share the same concept in design as OpenHIE architecture supports interoperability by creating a framework that maximally leverages health information standards, enables flexible implementation and supports interchangeability of individual components. HITRAC through the integration platform architecture has brought human resources data of doctors, nurses, paramedics, rehabilitation practitioners, environmental health practitioners, pharmacists, facilities, ministry of health and child welfare human resources and various external systems such as DHIS2 together a fundamental basis of interoperability in harmonizing the context with which information is collected in so that it’s broadly reusable to a much larger set of stakeholders. The following terminology has been adopted from OpenHIE Architecture.

External Systems

Who benefits from Integration Platform?

The external systems are a diverse group of actors that leverage the health information exchange to improve the quality of care by using higher quality and more timely data to support their activities. These systems include DHIS2, TrainSmart, mobile messaging tools (SMS/IVR), electronic medical records, laboratory or stock management systems, and monitoring and evaluation tools

Interoperability Layer

Who facilitates complex interactions where multiple actors are involved?

The Interoperability Layer (IL) is the component that enables easier interoperability between disparate information systems by connecting the infrastructure services and client applications together. An interoperability layer receives transactions from external systems and coordinates interaction between components of the integration platform and provides common core functions to simplify the interoperability between systems.

Terminology Services

What vocabulary do we agree to use?

The Terminology Services (TS) component of the Integration platform Architecture provides a centralized source for the local and international standards and definitions, including terminologies, ontologies, dictionaries, code systems, and value sets. Other Integration platform components can use these standards and definitions to normalize clinical data and achieve consistent aggregation and reporting.

Client Registry

Who received health Services?

The Client Registry (CR) supports the unique identification and management of client identities. These are desperate databases of council systems such as Nurses council of Zimbabwe, Medical and Dental Practitioners Council of Zimbabwe etc.

Shared Health Record

What is a person’s cumulative health history?

A Shared Health Record (SHR) enables the collection and storage of electronic health information about individual patients in a centralized repository which is capable of being shared across different healthcare settings. This is coming soon through utilizing the integration platform, pharmacy system and clinical system being developed by HITRAC.

Facility Registry

What facilities provide health services?

The Facility Registry (FR) serves as the authority for maintaining the unique identities of facilities such as Hospitals, Clinic Surgeries etc. where health services are provided. This is the service that manages a master facility list dataset. This data is being consumed from Health Professions Authority of Zimbabwe (HPA).

Health Workforce Observatory

Who provides health services (the personnel)

The health workforce observatory  supports actions that address HRH challenges through promoting, and developing knowledge base for HRH information that is based on reliable analysis for effective use at sub-national, national and regional level.

Did you find apk for android? You can find new Free Android Games and apps.