This space provides information on communities of practice around OpenHIE. All communities encourage openness and collaboration when it comes to sharing knowledge. In addition, this page serves as a resource for community descriptions, call information, community leads, and ongoing common work.

Get involved when and where it works for you!

Join us Quarterly at the OpenHIE Implementers Network

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.

The OpenHIE Implementers Network Logo

Meeting info: OpenHIE Implementers Network Call

Communities of Practice

OpenHIE Core Component

Architecture & Standards Community

The OpenHIE Architecture & Standards community was created for members of OpenHIE and its Communities to discuss cross-cutting technical issues about how components work with one another and the affect they have on our health information exchange. Link to Architecture Specification.

Community Leads: Jose Costa Teixeira Chris Bell  Carl Fourie Shaun Grannis
Meeting info:
Architecture Subcommunity Calls

Facility Registry Community

The Facility Registry Community (OHIE-FR) is made up of technologists and implementers supporting health facility registries and master facility lists.

Community LeadsRita Sembajwe Martin OsumbaAdam Preston
Meeting info:
Facility Registry Subcommunity Calls

Health Management Information System Community

The Health Management Information System Community (OHIE-HMIS) leads the development and deployment of technologies to better manage health information thus providing better patient care.

Community LeadsBob Jolliffe Austin McGee 
Meeting info: Health Management Information System Subcommunity Calls

Health Worker Registry Community

The Health Worker Registry Community (OHIE-HWR) leads the development and deployment of provider registries, developed using technologies to support a comprehensive database of all providers of health care services in a certain population. 

Community Lead: Ally Shaban  Dana Acciavatti
Meeting info
: Health Worker Registry Subcommunity Calls

Patient Identity Management Community

The Patient Identity Management Community is focused on technology that provides accurate, reliable and stable identification and de-duplication of individuals and other entities in a variety of contexts.

Community Lead: Mary Pittman Toan Ong   Shaun Grannis 
Meeting info: Patient Identity Management Community Calls

Interoperability Layer Community

The Interoperability Layer Community (OHIE-IL) aims to enable easier interoperability between Health Information Systems by providing a forum for discussion and knowledge sharing and by designing and developing an interoperability layer that connects the components within the OHIE.

Community LeadRyan Crichton
Meeting info
: Interoperability Layer Subcommunity Calls

Shared Health Record Community

The Shared Health Record Community (OHIE-SHR) aims to enable 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.

Community Lead: Ryan Crichton 
Meeting infoShared Health Record Subcommunity Call Page

Clinical Metadata / Terminology Service Community

The Terminology Service Community (OHIE-TS) serves as a central authority to uniquely identify the clinical activities that occur within the care delivery process by maintaining a terminology set mapped to international standards such as ICD10, LOINC, SNOMED, and others.

Community LeadsJack Bowie Jonathan Payne Joe Amlung 
Meeting infoTerminology Services Subcommunity Call Page

Health Information Exchange Topic

Health Financing towards UHC Community

The Health Financing towards UHC Community (OHIE-UHC) is focused on identifying health care financing data exchange needs, and working synergistically with the OpenHIE community to ensure that data exchange processes and requirements meet the needs of the health care financing communities.

Community Lead: Uwe Wahser Dragos Dobre Saurav Bhattarai 
Meeting Info: Health Financing Toward UHC Subcommunity Calls

Lab Information Systems Community

The Lab Information Systems Community (OHIE-LIS) offers a space for knowledge sharing and collaboration around LIS/LIMS and support efforts to standardize systems for better data sharing.

Community Leads: Rufus Nyaga Casey Iiams-Hauser 
Meeting Info:
Lab Information System Subcommunity Call

PEPFAR Data Exchange Implementer Community

The PEPFAR Data Exchange Implementer Community (PEPFAR-DEIC) serve for knowledge sharing between stakeholders involved in data import into DATIM, and to provide them with information on upcoming data exchange offerings.

Meeting info: PEPFAR Data Exchange Implementer Community Calls

Supply Chain Community

The Supply Chain Community (OHIE-SC) is a sub-team that engages with OpenHIE to leverage knowledge from real-world projects and lessons-learned from OpenHIE to explore the use/creation of standards and standard processes that might be used to support healthcare supply chain tasks.

Community Leads: Pierre Dane  Josh Zamor 
Meeting Info: Supply Chain Subcommunity Call

Interest Groups

Capacity Strengthening Subcommunity 

As countries contemplate their implementation approaches to health data sharing, many are beginning to discern how to strengthen capacity in data exchange and other HIE related topics. This community is focused on working collectively to strengthen capacity to guild and support health information exchange projects through:  

  • Identification and prioritization of training and capacity strengthening needs
  • Identification, sharing and dissemination of existing global goods including guides and training resources
  • Creation of global goods relating to training or guidance

Community Leads:
Jennifer E Shivers 

Meeting info: Currently in drafting stages

DevOps Community

The DevOps subcommunity has discussions around strategy, leadership and coordination to; verify integration, communicate and demonstrate OpenHIE concepts, support implementer use of OpenHIE and conformance testing. 

Community Leads: Sovello Mgani Chris Bell 
Meeting Info: DevOps Subcommunity Calls

Privacy and Security Working Group

Like all of our subcommunities this working group is open for all to join at any time. The group is in its early stages discussing scope and goals/outputs for the working group and what kind of products might be out there.

Community Leads: Bob Jolliffe @Michael Markevich

Meeting Info: Privacy and Security Working Group Call

  • No labels


  1. Would suggest we add the MEDIC CR's updated source repository. The MEDIC CR open source community has moved to recently...

    1. Thanks for letting us know Justin.  I went ahead and added MEDIC CR.  In the future feel free to add valuable missing information like this.