Overview

Date: 14.10.2021

Objective: Weekly space for deep dive topics

Participants: (kindly only add your own names, not those of other participants)

• @Uwe Wahser

• @Patrick Delcroix

• @Doreen G. Wamiti

• Stephen

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:

  • STPH:

    • Interface backend first version : openimis/openimis-be-invoice_py at develop (github.com)

      • services (to use in addaptator) :openimis-be-invoice_py/invoice/services at develop · openimis/openimis-be-invoice_py (github.com)

      • signals: all “invoice“ services will send 2 signals but signal from other module can be used

      • models: openimis-be-invoice_py/models.py at develop · openimis/openimis-be-invoice_py (github.com)

    • creation invoice/bill:

      • Invoice for contribution and contract

      • Bill for claim payment, contribution commission, payment fees (will be based on invoice/bill payment)

  • 2M-Corp:

    •  

  • Healthix:

    • Architecture (cmp )

  • MTCC:

    • Our main role will be to integrate MIFOS with openIMIS through openHIM, so our aim is to develop openHIM mediators to integrate the payment channels to openIMIS and work closely with Healthix, STPH and 2M-Corp

  • Y-Note:

• Payment layer - workpackages:

  • openIMIS

    • core modules (STPH/SolDevelo)

    • APIs (STPH/SolDevelo)

  • 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?

  • 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)

  • 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)

  • 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 (04.11.2021):

• Testing scenarios

• offline / distributed scenarios (metadata, policy and claims)

• Beyond Health

• Accounting / Payment layer

• FHIR IG

Additional Resources