2025-05-20 Developers Deep Dive Call: Solutions & Sandbox
Overview
Date: 2025-05-20 - 14:00 am (UTC)
Room:
Objective: Project updates and indepth discussions
Participants: (kindly only add your own names, not those of other participants)
Agenda:
When (UTC) | Duration | Who | Topic |
|---|---|---|---|
14:00 (UTC) | 5 min | Updates & administrative things | |
14:05 (UTC) | 40 min | ||
14:45 (UTC) | 40 min | ||
14:25 | 5 min |
| AOB |
Minutes
Admin Stuff
EU Testing harness: https://interoperable-europe.ec.europa.eu/collection/interoperability-test-bed-repository/solution/interoperability-test-bed
if it can speed up our projects, let’s have a look at it, but it might be time consuming to prepare standard specification for this
Swiss TPH - Project: 2024.T3b Solution Building
we work on the menu and initialization parts
tasks from CoreMIS PRs such as app name config
AI solution to be looked at after these tasks
coordination desk will provide specific color scheme & logos for new solutions
m4h - Project: 2024.T4 Sandbox Setup
Installation of sandbox virtual machine(s) - openspp, openhim, openimis. Further discussion how to access those virtual machine for deploying , (reverse proxy?)
current - Discussion on how community is deploying instance => opnSense - Traefik (reverse proxy), docker
Domain names (DNS server?) => it might be with cloudflare? - pick subdomain and will consult to someone who knows the dns. (proceed with s2)
Met with medic interoperability on last meeting. Idea for interoperability would be feedback module (quite useful for Nepal & Cameroon) - It would rely on communication / communication request resource in FHIR → this is more related to claim - feedback rather than grievance. example can be (create some questionnaire (form) or json in medic-cht) + there could be more use-cases like using family/group as well.
can maker-chercker logic be de-activated in the etl module? yes
openSPP (v2) api on openIMIS side will be developed to support subscription method (openCRVS has this method webhook subscription) for interoperability , but it does not limit to openSPP only but will be widely utilized by any DCI standard system , so this part can be utilize later when the system is available.
ETL- workflow involves transformation of collected json(s) to inmemoryuploadfile (InMemoryUploadedFile (CSV) format and uploads to verification for individual module
Financial scope of interoperability → mojaloop,
Sandbox team is still reviewing and waiting for EMR/EHR due to because it require few developed in any EMR/EHR system widely available in open source.
Looking towards, enrollment of any beneficiaries data / patient data from some ehr/hmis could a scope for interoperability.
IO Standards created around openIMIS in the last years
We equipped openIMIS with a set of FHIR APIs based on FHIR 4 (mainly around the FN): https://fhir.openimis.org/artifacts.html
In the OpenHIE Initiative, we defined 5 selected standard workflows for health insurance.
From our implementations in different countries (which are all funded and run by other organisations), we have a few interoperability scenarios in production (though not necessarily aligned to standards): recording of community presentation of some use-cases
Based on the above work done in OpenHIE, the IHE agreed to mature these into the FAIS profile, which was published last year.
WHO seems to be picking up on the digital health financing part in their full-STAC concept now, as we were invited to present the above work in the last Open Digital Health Summit in Nairobi last year (recording & slides)
In the openIMIS Initiative we just awarded a contract to set up an interoperability sandbox around openIMIS to showcase interoperability scenarios in health and social protection. They are about to start their work soon.
Questions / AOB
Presentations / Attachments
Additional Resources
Did you encounter a problem or do you have a suggestion?
Please contact our Service Desk
This work is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License. https://creativecommons.org/licenses/by-sa/4.0/