2021-12-02 Developers Deep Dive Call
Overview
Date: 02.12.2021
Objective: Weekly space for deep dive topics
Participants: (kindly only add your own names, not those of other participants)
@Uwe Wahser
@Doreen G. Wamiti
@Momodou Lamin Jarju
@Dragos Dobre
@Purushottam Sapkota
@Musa Ndow
Topic Proposals:
https://openimis.atlassian.net/wiki/spaces/OP/pages/3025108997 , https://openimis.atlassian.net/wiki/spaces/OP/pages/3115581566 , https://openimis.atlassian.net/wiki/spaces/OP/pages/3115778141 ,
,
Presentations / Attachments
Minutes
Payment Layer - short recap:
:
invoicing and billing in one BE Invoice module (on github develop branch):
invoicing and billing FE in development
calculation rules: , ,
Payment Plan
FHIR Invoice resource mapping & endpoint:
working on FHIR bill :
create push event mechanism in FHIR
-
Hospital/Insurance Organization, Patient, Invoice-Invoice, Invoice-Bill
:
create new table with bank accounts
working on Mojaloop API in openIMIS
Kubernetes no longer needed if Docker image is also working: need feedback from STPH - set up call between STPH & 2M
:
need clarification:
Mifos - Mojaloop: direct connect:
triggering mechanism from openIMIS - OpenHIM - MIFOS
:
How can OpenHIM know that data was changed in openIMIS?
according to BlSq a module to listen to the internal event and push the information to an API (web-hook) in openIMIS is not too complicated
APIs extension for bank account needed in the openIMIS patient API
Y-Note:
2do list: openIMS - openHIM (going to MIFOS)
integrate account number into patient & claim/invoice ressource => Swiss TPH
account information will be added to openIMIS tables => 2M Corp
create push event mechanism in FHIR => Swiss TPH
-
Hospital/Insurance Organization, Patient, Invoice-Invoice, Invoice-Bill
Payment layer - workpackages:
openIMIS
core modules (STPH/SolDevelo)
FHIR APIs (STPH/SolDevelo) -
definitions: End of this week
development: end of next week
Payment Switch APIs & module (2M-Corp)
MojaLoop customisations/configuration
development (2M-Corp)
packaging of customisations (2M-Corp)
packaging/availing of core software
Kubernetes → available on openIMIS servers as VN - who can do the Kubernetes configuration?
docker:
Alternative: mojaloop sandbox
MIFOS customisations/configuration (Healthix)
development (Healthix)
how can openIMIS accounts be translated to MIFOS? What needs to be done in MIFOS without copying existing openIMIS functionality?
packaging of customisations (Healthix)
how can the developments packaged and pushed in to a bare MIFOS installation?
packaging/availing of core software (link to docker version was shared) - (STPH T1)
link to demo server: https://mifos.s1.openimis.org/community-app/#/
OpenHIM customisation/ configuration
aligning openIMIS (FHIR) to MIFOS (Financial Standards?) - mapping matches to 80% what about the rest? (Healthix)
development of the mediators (MTCC)
packaging of the mediators (MTCC)
packaging/availing the core software (STPH T1)
docker compose needs to include special port configurations for nginx (MTCC <> STPH)
Sandbox
install openIMIS (STPH)
QA/showcase: STPH
install MojaLoop ( ? )
QA/showcase: 2M Corp
install MIFOS (STPH)
QA/showcase: Healthix
install openHIM (STPH)
QA/showcase: MTCC
Questions - Challenges - Issues
Next meeting (25.11.2021):
Testing scenarios
offline / distributed scenarios (metadata, policy and claims)
Beyond Health
Accounting / Payment layer
FHIR IG
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/