Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Welcome to the OpenHIE Implementers Network (OHIN)


Introduction

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

OHIN takes place in the form of four online, open meetings throughout the year, showcasing OpenHIE implementations and technical demonstrations in addition to sharing resources and updates the community. Following these call topics, space is also saved for call attendees to share insights and challenges they are experiencing.

Image Removed


Background 

Purpose

Use-Cases

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

The OpenHIE Implementers Network (OHIN) is a 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 is an implementers portal and leverages existing peer-based learning networks and creates bridges between networks.

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


Info

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.


Image Added

Panel
borderColorLightGrey
bgColorLightGrey
borderWidth1
borderStylesolid

Latest Updates

OHIE Architecture links

General OpenHIE Communities Page

Join the conversation here

Please visit the OHIN Discourse Page to join the conversation and post a new topic to the forum if you have something you would like to see on an upcoming agenda.


 


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: