REGISTRATION IS OPEN for #OHIE19 4-8 Nov, 2019 in Addis Ababa, Ethiopia - CLICK HERE
Skip to end of metadata
Go to start of metadata

Welcome to the OpenHIE Implementers Network (OHIN)

Introduction

The OpenHIE Implementers Network (OHIN) is a forum dedicated to bringing countries and implementers who are working in some of the most challenging environments on the planet together to share questions, problems and ideas so we can work on solutions together.

Background 

Drivers for an implementation community:

  • OpenHIE wants to be implementation driven
  • Increasing demand from countries and funders
  • Need to build up evidence base for what works and doesn't
  • Facilitate collaboration between implementations

Purpose

The OpenHIE (OHIE) Implementers Network (OHIN) is a new community network to support three identified user groups:

  1. Country implementers
  2. Domain experts
  3. Developers wanting to adopt and implement OpenHIE standards.

The OHIN has an implementers portal and a mailing list. It will also leverage existing peer-based learning networks and create bridges between networks.

Reference Technologies

OpenHIE has a set of existing reference technologies that support the component architecture and workflows. A list of these are found here: Reference Technologies

Use-Cases

During the course of our discussions we are engaging with various use-cases and scenarios where impmlementers are trying to understand how OpenHIE can and is being used. Below are some links to existing discussions that are being captured:


Thoughts from the community:

What would make OpenHIE easier to adopt?

  • Example tools that can illustrate the ability to solve common problems implementations face. I.e. enabling automatic retires of requests to OpenHIE services when there are connection issues/outages.
  • A reference implementation/tooling for connecting to common key partner platforms like OpenMRS and other mobile tools
  • Aggregate data reporting to an HMIS with a TS as an intermediary to handle indicator mapping, would be a common use case. outlined here for # of HWs -> HMIS: https://wiki.ohie.org/display/documents/Provide+Aggregate+Health+Worker+Information+Statistics. A similar workflow could apply where we are  looking at aggregating data from a POS or SHR..

Mailing lists

Join the mailing list here: https://groups.google.com/forum/#!forum/ohie-implementers

Subscribe: ohie-implementers+subscribe@googlegroups.com
Post: ohie-implementers@googlegroups.com

Draft email invitation text: OHIN Email Invitation Text

 


Resources

 


 

FEEDBACK - Discussion Pages

As the OpenHIE Implementers Network is growing we are wanting to make sure it is a space that is able to address the questions and provide the answers each member is looking for. We would value your input into and on the following:


  • No labels