2020-06-24 Formal Sector Workshop Series (VII)

2020-06-24 Formal Sector Workshop Series (VII)

Overview

Date: 24.06.2020

Objective: Align scope and roadmap for Formal Sector Integration

Participants:

  • @Patrick Delcroix

  • @Xavier Gillmann (Unlicensed)

  • @tabea.boateng

  • @Uwe Wahser

  • @Nirmal Dhakal

  • @Dragos Dobre

  • @Maguette T. NDONG

  • @Doreen G. Wamiti

 

Topic Proposals:

Date

Topic

Presenter

Comments

Date

Topic

Presenter

Comments

13.05.2020

Overview of Formal Sector requirements from Nepal

GIZ Nepal

https://openimis.atlassian.net/wiki/spaces/OP/pages/1362427912

20.05.2020

Gap analysis and conception for core modules

SwissTPH

https://openimis.atlassian.net/wiki/spaces/OP/pages/1369735179

27.05.2020

Overview of the https://openimis.atlassian.net/wiki/spaces/OP/pages/40763442 for the openIMIS modular re-architecture

BlueSquare

https://openimis.atlassian.net/wiki/spaces/OP/pages/1400569860

03.06.2020

Gap analysis and conception for APIs (I)

Healthix

https://openimis.atlassian.net/wiki/spaces/OP/pages/1422196737

10.06.2020

Gap analysis and conception for APIs (II)

Healthix

https://openimis.atlassian.net/wiki/spaces/OP/pages/1437564993

17.06.2020

Gap analysis and conception for APIs (III)

Healthix

https://openimis.atlassian.net/wiki/spaces/OP/pages/1450705502

 

JSON Extensibility and Scheduled tasks in new architecture

BlueSquare

24.06.2020

Gap analysis and conception for APIs (IV)

Healthix

 

 

Align the https://openimis.atlassian.net/wiki/spaces/OP/pages/40763442

https://openimis.atlassian.net/wiki/spaces/OP/pages/589561913

https://openimis.atlassian.net/wiki/spaces/OP/pages/40763442

Presentations

  File Modified

PDF File DigitalKe-Scope2-24-06-2020.pdf

Jun 24, 2020 by Doreen G. Wamiti

Minutes

Entities

Workflows

Workflows: verify with https://wiki.ohie.org/display/SUB/Health+Financing+Workflows

APIs

APIs: verify with openIMIS FHIR implementation: openIMIS FHIR modules

  • Which FHIR resource for contribution?

    • FHIR resource to be defined

      • Possible candidate Contract/asset (contract may have several contribution, 1 per employee)

  • Use and difference between FHIR Patient and Person?

    • Carl: do not use 2 FHIR resources to represent the same openIMIS entity

    • Group and claims are linked to Patients (not persons) therefore using Patient make more sense to the community (no one expressed any oppositions)

  • FHIR Payment resource for Contribution payment?

    • Can FHIR PaymentReconciliation be used?

  • FHIR resources: “the ones in red“ - building afresh means building from scratch or create a R4 version?

    • will be build using FHIR 4

    • Patient and Coverage to amend => change colour in green

  • InsurancePlan should be provided?

    • check with Nepal team if they need the list of openIMIS Products in SOSYS

  • Challenge: add extensions for openIMIS required fields to comply with openIMIS data structure

  •  

Dependencies

  • HF to be linked directly through OpenHIM

    • Carl: preference for openIMIS and HF to interact through OpenHIM

Questions - Challenges - Issues

  • Detailed Product & Contract resource still needs to be communicated by Nepal S4H

  • Alignment with STPH contributions: most APIs are dependent on the STPH development. Do we need to wait for all of that to finish, before Healthix development starts?

  • Inter-dependencies:

    • Make empty be modules:

      • Models -

      • Service function:

        • Update

        • Create

        • Delete

      • Security not yet done because it could be added later

        • Rule set on the model → “Query set” like claims will force the ORM to comply to security define (with rules)

  • Module size: Watch out if the module have more than several thousand lines of code.

Next week:

  •  

Additional Resources