Present: Michael Kohn and Marc Abbyad, Medic Mobile/CHT; Brandon Bowersox-Johnson, VillageReach and Josh Zamor, OpenLMIS
Agenda
1. Personal Intros
2. Summary of Medic's interoperability efforts: to-date and planned
3. Summary of VillageReach's interoperability efforts: to-date and planned
4. FHIR advice and/or resources
5. Medic / OpenLMIS
Notes
1. Personal Intros
Michael Kohn - been with Medic 3 years and supports with data & analytics, dashboards, postgreSQL infrastructure; also did warehouse software in the past, and now working on interoperability more. Marc Abbyad, Software Technologist and Product Manager at Medic, had some good collaborations with VR in the past. Brandon and Josh.
2. Summary of Medic's interoperability efforts: to-date and planned
In past years, they did a number of one-off ad-hoc integrations, especially to DHIS-2. But none of those really scaled or took off. One was in Kenya with a specific CSV format and import/export feature. They also prototyped an integration using Apache Nifi: based on schedule they ran a SQL statement on PostreSQL and sent to DHIS-2 using APIs. They are working now with an MoH partner to really define indicators and calculations more clearly. But all of this has been pretty custom. Separately, on OpenMRS implementers conference they built an integration sending data from Medic to and from OpenMRS using Apache Wifi. Also doing another one-off integration with a facility based tool.
3. Summary of VillageReach's interoperability efforts: to-date and planned
Brandon gave 3 slide background:
https://docs.google.com/presentation/d/1hgx0OQNAngYW6zk2jYsDa1j9dKC899f9MFfjXypEJ4Y/edit#slide=id.g3727f1a773_1_126 (OpenLMIS Analytics Infrastructure
Integrations: https://docs.google.com/presentation/d/1hgx0OQNAngYW6zk2jYsDa1j9dKC899f9MFfjXypEJ4Y/edit#slide=id.g3cd8e0844c_0_0
Interoperability: https://docs.google.com/presentation/d/1hgx0OQNAngYW6zk2jYsDa1j9dKC899f9MFfjXypEJ4Y/edit#slide=id.g34f35b867e_0_89
Josh: Some of our plans with DHIS2, FHIR and the Data Warehouse stack are more aspirational.
- If you were to post a FHIR message to DHIS2, it cannot accept that yet (actually it can take in some patient FHIR data, but not aggregate data as FHIR yet). We don't have final project plans and money for DHIS2 to accept FHIR data directly, but we have general agreement that moving towards FHIR is a good thing. For now we are using a FHIR server and a system account where our FHIR server then pushes to DHIS2 in one of two ways: DHIS2 folks are going to put in some FHIR support, or we will fall back to ADX. We will see something in OpenLMIS 3.6. After that, we have more aspirations such as getting FHIR support in a Facility Registry as well as better FHIR representations of a Product.
Michael: Question: What do we use for interoperability layers and facility registries? Josh answered that we are solution-agnostic and also have options where OpenLMIS can be the temporary facility registry at first.
4. FHIR advice and/or resources
5. Medic / OpenLMIS
Brandon: Question: How can we stay in touch about supply chain interoperability with the CHT?
--> get Demo of CHT first, THEN talk about what touch points and workflows could look like.
Should CHT maybe make sure to have an OpenHIE interface?