IOL

OpenHIM (www.openhim.org)

Jembi Health Systems (www.jembi.org)

The OpenHIM is an interoperability layer that facilitates OpenHIE workflows. It allows easy configuration and setting up of channels and endpoints that allow systems to connect and exchange information. The use of mediators allows implementer/developers to add logic and custom flows to the channels. This is the current reference technology for the IOL community of OpenHIE.

Connectathon offering:

The OpenHIM will be setup and available for teams to create their own channels and the Jembi team be available to advise of how mediators and additions can be made.

TBD

SHR

HEARTH

(https://github.com/jembi/hearth)

Jembi Health Systems (www.jembi.org )

HEARTH is Jembi's HL7 FHIR server that serves as an SHR on many of Jembi's internal projects. This FHIR server allows for FHIR resource management and has been used in multiple ways to manage more than just patient health data; such as patient management, facility mangement etc.

Connectathon offering:

HEARTH will be setup and available for teams to leverage and engage with the endpoints that include the storage and retrieval of FHIR resources from the tool

TBD

CR / MPI

FR

LMIS

OpenLMIS (www.openlmis.org)

VillageReach, OpenLMIS Community

OpenLMIS is an electronic logistics management information system that manages and automates logistics processes at over 10,000 health facilities across 9 country implementations in Africa. In the OpenHIE landscape, key areas of interoperability are: Facility Master Data, Product Master Data, and pushing data out to HMIS and third-party reporting/dashboard/analytics tools.

Connectathon offering:

OpenLMIS is available at a demo site in the cloud with a documented REST JSON API. This demo site is available for teams to log in and access the APIs to demonstrate integrations.

TBD

HWR

TS

Open Concept Lab (OCL)

Regenstrief/Apelon

OCL provides cloud-based community-driven terminology management. OCL lowers implementation barriers by 1) providing access to major terminologies, such as the Columbia University eHealth Laboratory's interface terminology (CIEL, utilized in OpenMRS) and other international standards like ICD-10 and 2) supporting standards based operations to enable interoperability.

Connectathon offering:

OCL is available at a demo site for teams to utilize on various levels, from exploring how standardized terminologies and indicators can be represented to testing out the REST API and initial FHIR Terminology Services.

TBD

UHC

openIMIS (www.openimis.org)

openIMIS Community

openIMIS is an open-source MIS designed to facilitate the move towards Universal Health Coverage (UHC) by supporting the management of various types of social health protection schemes, including management of policies - financial information but also included medical supplies and services -, insurees - incl. Enrollment and renewals - and claims.

Connectathon offering:

A connectathon instance will be available to analyse and demonstrate ongoing work to develop integrations with POS applications and potential OpenHIE registry components.

TBD

HMIS

DHIS2 (www.dhis2.org)

JSI

DHIS2 is a tool for health information collection, management, analysis and reporting. It is the current reference software for the HMIS component within the openHIE architecture.

Connectathon offering:

A sandbox instance of the latest version of DHIS2 software will be available locally and on the cloud specifically for use within the connectathon/hackathon.

TBD

POS (mobile)

CHT Core Framework (communityhealthtoolkit.org)

Medic Mobile (medicmobile.org)

The Community Health Toolkit includes resources to support full-featured, scalable digital health apps that equip health workers to provide better primary health care in their communities. The Core Framework can support many languages, run offline when needed, and work with basic phones (via SMS), smartphones, tablets, and computers. App developers are able to define health system roles, permissions and reporting hierarchies, and make use of five highly configurable areas of functionality: messaging, task and schedule management, decision support workflows, longitudinal person profiles, and analytics.

Connectathon Offering:  

A sandbox environment and a few teammates from Medic Mobile will be available to connect with other components in the ecosystem.

TBD

POS (mobile)

CommCare

JSI

CommCare is an open source mobile platform designed for data collection, client management, decision support, and behavior change communication. CommCare's mobile application is used by client-facing community health workers in visits as a data collection and educational tool and includes optional audio, image, and video prompts. Users access the application-building platform through the website which Dimagi operates on a cloud-based server.

Connectathon Offering:  

A sandbox environment of CommCare will be available in the cloud for use to connect with other components in the ecosystem.

TBD

OpenHIM Mediator Development

Tutorial and training on developing an OpenHIM mediator.

Jembi Health Systems

CommCare - DHIS2 Interface

Automate data exchange between CommCare and DHIS2 using the OpenHIM, to limit duplication of efforts and data entry errors for health workers  collecting community health information using the CommCare mobile app and managing aggregate data on CommCare server and in DHIS2.

The two systems (CommCare and DHIS2) have the same organization unit structure and data elements which will make the data exchange process less complicated.

JSI

openIMIS Data Exchange and Interoperability

TBD

openIMIS Community

Community Health Toolkit

The Community Health Toolkit (CHT) includes resources to support full-featured, scalable digital health apps that equip health workers to provide better primary health care in their communities. This stream will look at opportunities to incorporate the CHT into the OpenHIE framework as a mobile POS, interfacing with HIE components e.g. - creating a patient, health worker, or facility in the CHT could create the corresponding records in the Client Registry, Health Worker Registry, or Facility Registry.

(Medic Mobile) Michael Kohn

Computable Care Guidelines

The World Health Organization is creating Computable Care Guidelines as FHIR Implementation Guides; bundles of artifacts to help streamline implementation of WHO guideline content. Use the newly proposed $cpg-next-step operation to invoke this decision support from a simplified client.

https://docs.google.com/presentation/d/1XmVaYnoFIWD-xidQTGe4JwSuYlNzr1pli2Z1ukVV1t0/edit?usp=sharing

CCG Working Group, WHO

Bryn Rhodes

DHIS2/FR - Administrative Area Registry Interface

Develop an interface between DHIS2 or Facility Registry with the Administrative Area Registry used in Tanzania.

Oswald Luoga