Overview

Date: 18.11.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

Topic Proposals:

• Project: 2021.T3 Payment Layer , Project: 2021 Payment Layer - MojaLoop Integration , Project: 2021 Payment Layer - MIFOS Integration , Project: 2021 Payment Layer - OpenHIM Integration

• Calculation rules , Calculations Module

Presentations / Attachments

	File	Modified

You are not logged in. Any changes you make will be marked as anonymous. You may want to Log In if you already have an account.

No files shared here yet.

Drag and drop to upload or browse for files

Upload file

File description

Minutes

• Payment Layer - short recap:

  • STPH: Project: 2021.T3 Payment Layer

  • 2M-Corp: Project: 2021 Payment Layer - MojaLoop Integration

    • certificates needed from Mojaloop (challenge that needs to be signed by openIMIS)

    • ticket open to be able to work on additional attributes: OSD-154, OSD-152

    • working on Mojaloop API in openIMIS

    • Kubernetes no longer needed if Docker image is also working: need feedback from STPH

  • Healthix: Project: 2021 Payment Layer - MIFOS Integration

    • APIs for MIFOS shared:

    • need clarification:

      • Mifos - Mojaloop: direct connect or via mediator (e.g. openHIM)

  • MTCC:

    • How can OpenHIM know that data was changed in openIMIS?

      • Events in openIMIS are only internal, API itself does not trigger anything

      • 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

  • Y-Note:

• 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: https://hub.docker.com/u/mojaloop

      • 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

• Incubator: Integration of a Payment Layer

• Project: 2021.T3 Payment Layer