Overview

Date: 17.06.2020

Objective: Align scope and roadmap for Formal Sector Integration

Participants:

• Uwe Wahser

• tabea.boateng

• Doreen G. Wamiti

• Eric Darchis

• Xavier Gillmann (Unlicensed)

• Dragos Dobre

• Patrick Delcroix

• Purushottam Sapkota

• Nirmal Dhakal

• Fourie, Carl

• Maguette T. NDONG

• Siddharth Srivastava

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

• claim payment is not managed in openIMIS (flows):

  • feature looks very useful, but the structures are not available in openIMIS, yet.

  • verify with Nepal, if feature is requested - other implementers?

• claim FHIR to send from openIMIS to SOSYS exists (flows)

  • currently done via file? technically it’s an exiting FHIR API in openIMIS and would need to be extended

• REST C# is not an extension and is not part of the FHIR (separate component to connect mobile applications) => will be deprecated by modular architecture

• (Patrick Delcroix ) I am not sure that the contribution are supported in the current FHIR module, the contribution is, as per the e-payment definition, the amount claimed as sent, for the formal sector, we aim to use the contribution as the tri-parties agreement for a given period (Employer - employee - Insurance), the FHIR resources that match this definition is the contract; on employer will have only one contract for a given period, all employee will be mentioned as FHIR Asset. In openIMIS this FHIR contract will be called “contribution collection”

• We need to consider the legacy integrations using R3 FHIR for OpenMRS and Bahmni when thinking about upgrades etc.

  • check required FHIR resources between STU3 and R4

Dependencies

• MS-SQLJSON vs. Postgrs JSON(B)

  • no indexing in MS-SQL JSON

  • language not normalised

  • add column to the DB scheme for selected object types even in the legacy DB

• Batch / Background scheduler: Apache Airflow vs. openHIM

  • more suitable outside of the openIMIS internal workflows

  • integration into OpenHIE?

  • alternatives:

    • Django Celery: https://github.com/celery/django-celery

    • django-cron

    • django-scheduler

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

Questions - Challenges - Issues

Next week:

• finalisation of Healthix workflows incl. timeline

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/