Welcome!

This is the new space for OpenHIE Communities & Projects. This team space is great for sharing knowledge and collaborating on notes or projects within the OpenHIE community. If you have any recommendations or questions regarding this space please visit the OpenHIE help page or reach out to openhie@gmail.com.


Next, you might want to:



Projects 

This is a place to capture implementation notes concerning the projects that the OpenHIE and DUC Communities are hearing about.  The information is captured based upon the information that was understood at the time of capture. We know it is not perfect, but the intent is to help provide an idea of what is going on in the field.  We welcome your additions/ changes / updates. You must be logged into add to or update the log and revisions are being tracked.  The projects may be sorted by clicking on the column headings.  

COUNTRY (where is the implementation happening) PROJECT NAMEUSE CASE / GOALS (What is the project trying to accomplish) SCALESTATUSPROJECT ORGANIZATIONS (who is involved)Last Updated  (Date or reference to where this project was mentioned) NOTES and additional details.  (May include Data Exchanges, technologies and other details)Does the project team need OpenHIE assistance?
Multiple (Central America and the Dominican Republic)Cross-Border Epidemiological SurveillanceCross-border epi surveillance to support migration across countries.  
InitiativeSICA / COMISCA, Ministries of Health, Goverment of Korea2023-08-03 OHIN CallChallenges include governance, human interoperability and diversity of systems across the countries.  
Multiple (Argentina, Belize, Chile, Colombia, Ecuador, El Salvador, Guatemala, Honduras, Panama, Paraguay, Peru, Surinam, Uruguay)LACPassTraining people in standards (HL7 / FHIR) 

Two conectathon to to test the cross-border interoperability for  vaccine certificates and the IPS.


IDB, Ministries of Health, PAHO, CENS2023-08-03 OHIN CallAdopted and adopting SNOMED CT and HL7 FHIR
BrazilDataSUSCreated a national repository of health data for the MOH.  They have a platform of services that allows users to consume the data based upon needs.  Have data governance.  Enables sharing of information about vaccines and other data in real time.  Also supports survellience from both public and private providers.  

NATIONAL

ProductionMinistry of Health2023-08-03 OHIN CallUse of OpenSource technologies and standards.  
Argentina 
Terminology and alignment on data standards.  The health system is fragmented with both private and national providers.  Created definitions and promoted national terminology and standards across both the public and private sector.  

NATIONAL

ProductionMinistry of Health of the Nation, healthcare providers2023-08-03 OHIN Call

TERMINOLOGY SERVICE.  SNOMED CT


UruguayNational EHRNational architecture for federated systems.  Includes private sector and other health organizations.  

AGESIC / Salud.Uy, Ministry of Health, healthcare providers2023-08-03 OHIN Call

INTEROPERABILITY LAYER


Costa Rica(EDUS) Unique Digital Health Records 2016-2018 worked on capturing electronic records in hospitals and deployment of apps to support patient access to appointments, vaccine certificates and medical records.  This helped solve the data collection layer. 

Costa Rican Social Security2023-08-03 OHIN Call

ZimbabwePatient Identity Project using a deduplication process.  A national identifier is not used for health. There is an id number generated by the system and given to the patient.   The ministry would like to be able to connect all of the facilities together.  One challenge is that many patients are nomadic.  
Use Cases:  Continuity of care and Public health management.  

Currently have "online" facilities that can push data to the central repository in real time.  Approximately have progressed to have 20% online.  Also have "offline" facilities that share data, but not in realtime. 
Currently most facilities are "offline." 
Zim-TTech. I-Tech, Vital Wave, and Ministry of Health2023-07-26 Patient ID Mgmt Collaborative Session

EMRs connect to a central repository through an INTEROPERABILITY LAYER.  Have CLIENT REGISTRY TERMINOLOGY SERVICE (OCL) and a SHR.  
Using biometrics (fingerprints and iris)

For matching the team is using a probabilistic algorithm and using multiple mixture of attributes with different weighting.   


RwandaRwanda Health Information ExchangeOne citizen, one request.  
Had solutions based upon TB, HIV, Malaria and the solutions were diverse and Rwanda is looking a ways to take a patient viewpoint and ensuring that the data is connected.  

The shared health record is updated on a regular basis to ensure that the patient's comprehensive information is available to other systems.  

Pilot stage for connecting EMRs

Have onboarded 65 health facilities

2023-07-20 Facility Registry Call

 - Have documented the interoperability standards that they are planning to use for imaging and other standards.  
 - Using OpenHIM for the INTEROPERABILITY LAYER.  

 - Using a CLIENT REGISTRY and all of the EMRs are connected to the interoperability layer.  
 - Using a FACILITY REGISTRY to align on facility name.  Planning for all of the systems to use the facility registry to align on names.  

- also using a shared health record

 - have a TERMINOLOGY SERVICE
 - have a HEALTH WORKER REGISTRY


KenyaSMART Guidelines standalone app
Pilot
Intellisoft, CDC, GoogleOHIE23 E2 Unconference Session

UgandaLab and Hospital system integrationNeed to use OpenHIIM for integrating lab systems
3 hospital management systems are being connectedMOHOpenHIE23

Using OpenHIM ( INTEROPERABILITY LAYER) to connect with Lab systems and had to integrate the the sample tracking component that links the data to a central lab where people can log in and get their results


IndonesiaCHISUOpenHIM as a generic FHIR converter

USAID, Jembi, OpenHIE23

Created an OpenHIM mediator (INTEROPERABILITY LAYER)


MalawiIHRIS / Health Worker Registry

In ProgressMOHOpenHIE23

Malawi

PMCT / Product CatalogPRODUCT CATALOG



In ProgressMOHOpenHIE23Capture trade items and use GS1 standards.  
Malawi 

TERMINOLOGY SERVICE

Putting terminology into the system and used for mapping between DHIS2 and OpenIMIS

MOHOpenHIE23

Malawi

Health FACILITY REGISTRY



ImplementedMOH
Presented at OHIE23
Includes facility details 
Used in the integration with other systems to map facilities 

EthiopiaNational IDPatient identity using biometricsNationalStartingMekelle University, MOH, Gondar2023-05-01 (OHIE23 Day 1)Uses eCHIS and SimprintGovernance documents, connecting infrastructure via VPN,
Nigeria National Biometrics CollaborativeCapture Fingerprints to assist with patient IdentityHIV program 85% of patients are captured
PHIS32023-04-26 Patient ID Mgmt Collaborative SessionWorking on FHIR support for APIs.  Also have experience sharing data with DHIS2, EMRs and Labs.  
Nigeria National Concept dictionary 

Starting 
2023-04-07 Terminology Service Call

PhilippineseHealth Strategy PhilippinesBlueprint / Architecture 

NATIONAL

Published Ministry of Health2023-03-29 OHIN Call

TanzaniaTanzania BlueprintBlueprint / Architecture 

NATIONAL

Published Ministry of Health2023-03-29 OHIN Call

Sri LankaSri Lanka Digital Health Blueprint (V1.0b)Blueprint / Architecture 

NATIONAL

Published Ministry of Health2023-03-29 OHIN Call

Malawi 

Master Patient Index (DDE) Patient Matching 
CLIENT REGISTRY

For case reporting from a central repository

around 170 sites
Ministry of Health EGPAF2023-03-29 Patient ID Mgmt Collaborative Session
  • DDE is built on top of Ruby on Rails.
  • FHIR standards.
  • Offline first architecture. 
  • Produces a pre-generated non-identifiable patient ID for every client. These IDs are physically printed as barcodes and placed as stickers on the patient's Health Passport.
  • Currently 6 million unique clients registered.

Haiti Haiti Master Patient Index (Client Registry)

Lost to follow up 

patient transfer 

labs

Uses patient look up to avoid duplication of patients


PILOTThe initial scale for the pilot is for a specific EMR to a central repository.  Aligning terminologies to move toward support for other EMRs.  

Pilot (two sites to start and learn about infrastructure and needs) DIGI2023-03-29 Patient ID Mgmt Collaborative Session - Using FHIR standards including PIXm and PDQm
 - Integrates with a fingerprint registry
 - focus on integration between an EMR (Esante Plus, an OMRS Haiti implementation) and a client registry 

Mozambiqueinteroperability solutioninteroperability solution between the national Civil Registration and Vital Statistics electronic system (eSiRCEV) and the Vital Events Community Surveillance system (SIS-COVE) of the National Institute of Health (INS) of Mozambique.
ImplementingThe Ministry of Justice, Constitutional and Religious Affairs of Mozambique with technical support from the Jembi Mozambique2023/03 Jembi Mozambique Newsletter #7/2023 
UgandaDifferentiated Service Delivery Models in UgandaEMR to Decongest Facilities (EMR for DSDM) Need to better understand the number of people being served by a facility and treat in the community where possible.  60+ pharmacies

42K patients / 60 facilities
ImplementingMinistry of Health, Makerere University School of Public Health, CDC, Monitoring and Evaluation Technical Support (METS) Program, University of California San Francisco2023-03-09 Treatment Continuity (DUC Meeting)

OpenHIM, FHIR

Data is also synchronized from the Mobile to the EMR  and there is another use case where data is synced with the central repository


MalawiCommunity-based ART Retention and Suppression (CARES) App Community EMR app to collect the same data as the EMR on community visits 
TestingLighthouse Trust,  I-Tech Malawi, Comcare2023-03-09 Treatment Continuity (DUC Meeting)

Comcare application with ability to send and receive data from the EMR 

Planning to add hypertension model in the future.  


Lao People's Democratic RepublicGeoPrism Registry

Interlinking systems (like OpenHIE registries) by common geographies for the correct periods of time. HEALTH WORKER REGISTRY FACILITY REGISTRY

GeoPrism Registry uses the GeoPrism spatial knowledge graph dependency management framework

NATIONAL

Implemented


TerraFrame, Clinton Health Access Initiative (CHAI), Health GeoLab Hub, Vital Wave2023-03-23 Facility Registry Call (Presentation - see recording and notes) 
2023-02-24 OHIE Architecture & Standards Call

FHIR, GeoJSON, VectorTiles

Direct integration with DHIS2 and Reveal.

 


MozambiqueGeoPrism Registry

Interlinking systems (like OpenHIE registries) by common geographies for the correct periods of time. HEALTH WORKER REGISTRY FACILITY REGISTRY

GeoPrism Registry uses the GeoPrism spatial knowledge graph dependency management framework

PILOT

Implementing

TerraFrame, Clinton Health Access Initiative (CHAI), Health GeoLab Hub2023-02-24 OHIE Architecture & Standards Call

FHIR, GeoJSON, VectorTiles

Direct integration with DHIS2 and Reveal.


Sri LankaInformation ExchangeInteroperability between HMIS and OpenMRS.  Working on implementing FHIR standard

NATIONAL

ImplementingMinistry of Health 2023-02-24 OHIE Architecture & Standards CallHapiFHIR 
KenyaThe Local Health System Sustainability Project - Cross Border Digital Health SolutionPatient Identity for reporting

MULTI-NATIONAL

PILOT (scope to rest of EAC countries)

DevelopmentIntelliSOFT Consulting2023-02-24 OHIE Architecture & Standards Call

OpenHIM and EMR

HapiFHIR SHR

Standards : FHIR / Client Registry / OCL Terminology Services: CIEL / OCL

S/W solution: OpenMRS, DHIS2


UgandaThe Local Health System Sustainability Project - Cross Border Digital Health SolutionTracking patients along the border of Kenya and Uganda.  Patient Identity for reporting

MULTI-NATIONAL

PILOT(scope to rest of EAC countries)

DevelopmentIntelliSOFT Consulting2023-02-24 OHIE Architecture & Standards Call

OpenHIM and EMR

HapiFHIR SHR

Standards : FHIR / Client Registry / OCL Terminology Services: CIEL / OCL

S/W solution: OpenMRS, DHIS2


Multiple CountriesPSI Digital Health consumer interventionsConsumer app to drive consumers to facilities for interventions (referral app) 

PSI 2023-02-24 OHIE Architecture & Standards Call

 RapidPro/WFA>OpenHIM > HapiFHIR > NiFi > Postgres > Superset

OpenHIM/ HapiFHIR/ WA/ SMS /FBM/ Superset/ PBI


Multiple CountriesTraining / Capacity Building OHIE Certificate reimbursement program - OHIE session in AeHIN General Meeting (Indonesia Oct 2023)
PlanningAeHIN2023-02-24 OHIE Architecture & Standards Call

PhilippinesTraining / Capacity Building promote OHIE Academy as free training for DOH and PHIC staffers, general public - encourage DOH/PHIC to look for OHIE certificate for employments - offer Virtual Instructor-led Training  (on academy.ohie.org) - offer face-to-face training (on academy.ohie.org)

UP Manila - Standards & Interoperability  Lab (UPM-SILab)2023-02-24 OHIE Architecture & Standards Call

Applying WHO SMART Guidelines for FHIR profiles/IG development (eg, viral hepatitis, liver diseases, etc)

connectathon among EMR developers using the FHIR profiles with DOH/PHIC/WHO observing


Sri LankaDebt2HealthBreaking silos between hospitals.  Created a Digital health bluepriint and NDC health care and TB EHR

NATIONAL

DevelopmentGlobal Fund2023-02-24 OHIE Architecture & Standards CallCR and other building blocks are being put in place as well as a client portal. Also looking at OCL.   


OpenMRS based EMR for Primary Healthcare cluster

Asian Development Bank (ADB)2023-02-24 OHIE Architecture & Standards Callconnectathon among EMR developers using the FHIR profiles with DOH/PHIC/WHO observing
Multiple CountriesAeHIN Community of Interoperability Labs (COIL)Demonstration of syndicated TS between Region and PH ontoserver (eg, medications)


2023-02-24 OHIE Architecture & Standards CallRegional Terminology Server ontoserver (c/o SIL-Thailand) - Regional Terminology Server ontoserver (c/o SIL-Thailand) - National TS ontoserver  (c/o UPM-SILab)

WSO2 based Interoperability layer OCLTS OpenMRS based cluster EMR Sunbird based PR


2023-02-24 OHIE Architecture & Standards Call

Ethiopia, Chile, Malawi?Terminology Service Implementation

NATIONAL

MaintenanceCENS (Chile)TS Implementer Series: Chile

KenyaTerminology Service ImplementationNational Health Data Dictionary

NATIONAL

Early implementation, work ongoing

Palladium

University of Nairobi




NigeriaOpenMRS 3.X and OCL Terminology Service Implementation


Started

PHIS3




Sri LankaOCL Terminology Service Implementation

StartedMOH Sri Lanka


N/AOpenMRS ANC Reference ImplementationOpenMRS is implementing ANC SMART Guidelines to do things like Decision Support

PILOT

Development

OpenMRS

WHO




Communities of OpenHIE

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