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!
Communities of Practice
|OpenHIE Core Component|
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 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 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.
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-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.
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 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.
The Case Surveillance and Indicator Extraction subcommunity works to: Identifying gaps in and establishing standards for data exchange priorities, provide documentation and guidance to improve adherence to these standard, and ensure that rapidly deployed solutions can be integrated into the national digital health architectures
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.
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.
Meeting Info: Privacy and Security Working Group Call