This space provides information on communities of practice around OpenHIE. All communities encourage openess and collaboration when it comes to sharing knowledge. Please get involved where it makes sense for you.
Note: Those communities marked OpenHIE Architecture.focus on components that make up the
|About our communities of practice...|
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
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.
Mailing list: email@example.com
The Facility Registry Community (OHIE-FR) is made up of technologists and implementers supporting health facility registries and master facility lists.
Mailing list: firstname.lastname@example.org
Meeting info: Facility Registry Community Meetings
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: email@example.com
Meeting info: Terminology Service Community Call
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.
Mailing list: firstname.lastname@example.org
Meeting info: Health Management Information System Community Call
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: email@example.com
Meeting info: Shared Health Record Community Call
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.
Mailing list: firstname.lastname@example.org
Meeting info: Health Worker Registry Community Call
The Client Registry Community (OHIE-CR) is focused on technology that provides accurate, reliable and stable identification and de-duplication of individuals and other entities in a variety of contexts.
Mailing list: email@example.com
Meeting info: Client Registry Community Calls
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.
Mailing list: firstname.lastname@example.org
Meeting info: Interoperability Layer Community Call
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.
Mailing list: email@example.com
Meeting Info: Supply Chain Subcommunity Call
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.
Mailing list: firstname.lastname@example.org
Meeting Info: Health Financing towards UHC Call