This space provides information on communities of practice around OpenHIE. All communities encourage openness and collaboration when it comes to sharing knowledge. Please get involved where it makes sense for you. In addition, this page serves as a resource for community descriptions, call information, community leads, and ongoing common work.
Join us Monthly at the OpenHIE Implementers Network
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.
Meeting info: OpenHIE Community Call & OHIN Africa-Asia
Communities of Practice
| OpenHIE Architecture & Standards Component Communities |
|---|
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. |
The Facility Registry Community (OHIE-FR) is made up of technologists and implementers supporting health facility registries and master facility lists. |
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. |
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. |
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. |
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 centralised 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 Communities |
|---|
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. |
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. |
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. |
| Project-Based Communities |
|---|
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. |
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. |
Yearly Community Needs Checklist
Strategic Direction |
|---|
- Ensure strategic integration of activities and proceeds of working groups
- Identifies gaps or opportunities for technical collaboration between sub-communities as it related to the OpenHIE architecture and brings those issues to the Architecture Review Board for discussion
- Ensure someone is representing your sub community on the Architecture Review Board
- Check in on progress on the roadmap / goals and adjust as appropriate
| Implementer Support |
|---|
- Document OpenHIE workflow including a documented use case or success story
- Ensure that an exemplar solution is created
- Reviewing/contributing to materials and recommending technical approaches
- Creating implementation support materials and learning materials as appropriate.
| Specification and Testing |
|---|
- Document, maintain, and review for changes - the component section of the OpenHIE Architecture Specification
- Maintain workflow (data exchange) documentation and determine when standards or processes need to be updated
- Determine conformance testing needs (e.g., IHE, FHIR, or other) for workflow in coordination with Exemplar Software Owner and Associate Architects; with a focus on reusing existing tools and approaches.
- Review the architecture diagram and determine if there are any needed updates or changes
| Support Community Engagement Practices |
|---|
- Draft materials for the subcommunity, support facilitation, help establish and maintain the subcommunity roadmap
- When needed, create agendas, facilitate meetings, and engage in community outreach to get key audiences involved
- Look for work in progress to push to the OHIN calls for sharing with larger community
- Identify and promote success stories by bringing them forward to the larger group