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:

Presentations

	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

Entities

Workflows

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

APIs

APIs: verify with openIMIS FHIR implementation: openIMIS FHIR module

• 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

• Support for formal sector schemes - Incubator page in this wiki

• http://hl7.org/fhir/financial-module.html - FHIR R4 objects (financial Module)

  • openIMIS FHIR module

• OpenHIE Health Financing Group: https://wiki.ohie.org/display/SUB/Health+Financing+towards+UHC+Subcommunity

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

• JLN Processes Background - Joint Learning Network for UHC

  • Glossary: Glossary

• Product Roadmap

  • Beneficiary Enrollment

  • Persons & Families module scope

  • Policies module scope

  • Contributions module scope

• FHIR in openIMIS

  • openIMIS FHIR module

  • SolDevelo FHIR modules (example of BAHMNI): https://soldevelofoundation.org/new-modules-for-openmrs-and-openimis/

• Batch processing: Django APScheduler: https://github.com/jarekwg/django-apscheduler