This space provides information on communities of practice around OpenHIE. All communities encourage
openness and collaboration when it comes to sharing knowledge.
| Info |
|---|
The OpenHIE community historically has maintained several mailing lists for announcements and communication. In December 2019 all messages and conversations from groups marked "List Archived" were migrated from Google Groups to OpenHIE Discourse at discourse.ohie.org. |
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!
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
Mailing list: pepfar-data-exchange-implementer-community@googlegroups.com
Meeting info: PEPFAR Data Exchange Implementer Community Calls
The| Panel | ||
|---|---|---|
| ||
Join us Quarterly at the OpenHIE Implementers NetworkThe |
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. |
 |
Mailing list: ohie-implementers@googlegroups.com "List Archived"
Meeting info: OpenHIE Community Call & OHIN Africa-AsiaMeeting 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. |
The Facility Registry Community (OHIE-FR) is made up of technologists and implementers supporting health facility registries and master facility lists. |
|
|
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
Mailing list: terminology-services@googlegroups.com "List Archived"
Meeting info: Terminology Service Community Call
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. |
|
|
The Shared Health Record Community (OHIE-SHR) aims to enable the collection and storage of electronic health information about individual patients in a centralised repository which is capable of being shared across different healthcare settings.
Mailing list: openhie-shr@googlegroups.com "List Archived"
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. |
|
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. |
|
|
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. |
|
The |
Shared Health Record Community (OHIE- |
Mailing list: openhie-supply-chain@googlegroups.com "List Archived"
Meeting Info: Supply Chain Subcommunity Call
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. |
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. |
| Health Information Exchange Topic |
|---|
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. |
|
The COVID-19 Task Force formed in April 2020 in response to the interoperability and data sharing needs of the global community during the coronavirus pandemic.
Meeting Info: COVID-19 Task Force Calls
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. |
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. |
Interest Groups |
|---|
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:
Meeting info: Currently in drafting stages |
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. |
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 |
The Academy Community works together to create and/or share global goods that are focused on increasing the capacity to build and support health information exchange architecture and processes.
Meeting Info: Academy Community