2022-02-03 Developers Deep Dive Call

 

Overview

Date: 03.02.2022

Objective: Weekly space for deep dive topics

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

  • @Uwe Wahser

  • @Eric Darchis

  • @Dragos Dobre

  • @Patrick Delcroix

Topic Proposals:

Presentations / Attachments

  File Modified
No files shared here yet.

Minutes

Payment Layer - short recap:

  • :

    • done - invoicing and billing in one BE Invoice module (on github develop branch):

    • done - invoicing FE

    • wip - billing FE

    • done - calculation rules: ,

    • wip -

    • wip - Payment Plan

    • FHIR Invoice resource mapping & endpoint:

      • done - FHIR Invoice-Invoice example:

      • done - FHIR Invoice-Bill example:

      • open - integrate accounting in patient resource

      • wip FHIR IGs

    • wip - create push event mechanism in FHIR

      • -

      • Hospital/Insurance Organization, Patient, Invoice-Invoice, Invoice-Bill

    • done - search parameters updated

  • :

    • wip - Mojaloop API in openIMIS

      • done - step 1: openIMIIS → MojaLoop: verify account on ML

      • done - step 2: openIMIIS → MojaLoop: verify account with DFSP (service provider)

      • wip - step 2: ML → oI: request for consent

      • open - step3: authentication

      • open - step4: register credentials

      • open - step5: make payments

    • data structures in oI:

      • done - Patient Account

      • done - Hospital Account

  • :

    • waiting

  • :

    • done - main items

    • done - technical documentation in work

    • wip - OpenHIM → MIFOS - mapping information needed

    • wip - docker compose to be uploaded

2do list: openIMS - openHIM (going to MIFOS)

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

        • curl -X POST "http://sandbox.mojaloop.io/switch-ttk-backend/thirdpartyTransaction/partyLookup" \ -H "accept: application/json" \ -H "Content-Type: application/json" \ -d '{ "transactionRequestId": "b51ec534-ee48-4575-b6a9-ead2955b8069", "payee": { "partyIdType": "MSISDN", "partyIdentifier":"16135551212" } }'

           

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

      • demo:

        • need to receive demo data

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

        • solution on release: BE done, FE end of February

        • QA/showcase: STPH in February

        • Documentation: design documents in the wiki, overview page

      • install MojaLoop ( STPH / 2MCorp )

        • Developments: first week of February

        • QA/showcase: 2M Corp end of February

        • Documentation: in February

      • install MIFOS (STPH)

        • solution on release: done

        • QA/showcase: Healthix - February

        • Documentation: documentation on project page (verify)

      • install openHIM (STPH)

        • solution on release: first week of February

        • QA/showcase: MTCC - first week of February

        • Documentation: mapping document on the wiki, ongoing

      • First test-run: second week of February

Questions - Challenges - Issues

  • Use payment-layer channel in discourse to ask questions (register here: )

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/