Skip to end of metadata
Go to start of metadata

Welcome to the OpenHIE Implementers Network (OHIN)


OHIN: What is this forum and who is involved?

OpenHIE supports a collaborative space for those leveraging electronic health information by standardizing it in environments with constrained resources.

The OpenHIE Implementers Network (OHIN) provides a peer-learning forum for implementers to engage with one another, interact with the OpenHIE community, and create bridges between networks through OpenHIE hosted events. OHIN events are open to everyone, with special emphasis for the work of country implementers, domain experts, and developers wanting to adopt and implement OpenHIE standards.

What do typical OHIN events look like and how can I participate?

OHIN takes place in the form of open, virtual meetings held throughout the year, showcasing OpenHIE implementations, technical demonstrations, and other topics of interest to the community. In addition, resources and updates surrounding the community are also shared. Following these main meeting topics, space is also saved for attendees to share insights and challenges they are experiencing.

Community members are encouraged to bring questions, problems, and ideas unique to implementing the OpenHIE Architecture and tools to these meetings to take advantage of the peer-learning network.


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:

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.

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:



  • No labels