Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents

Overview

Date: 17.06.2020

Objective: Align scope and roadmap for Formal Sector Integration

...

Date

Topic

Presenter

Comments

13.05.2020

Overview of Formal Sector requirements from Nepal

GIZ Nepal

Formal Sector Workshop Series (I)

20.05.2020

Gap analysis and conception for core modules

SwissTPH

Formal Sector Workshop Series (II)

27.05.2020

Overview of the Product Roadmap for the openIMIS modular re-architecture

BlueSquare

Formal Sector Workshop Series (III)

03.06.2020

Gap analysis and conception for APIs (I)

Healthix

Formal Sector Workshop Series (IV)

10.06.2020

Gap analysis and conception for APIs (II)

Healthix

Formal Sector Workshop Series (V)

17.06.2020

Gap analysis and conception for APIs (III)

Healthix

JSON Extensibility and Scheduled tasks in new architecture

BlueSquare

Align the Product Roadmap

Developers Committee

Product Roadmap

Presentations

Attachments

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

Questions - Challenges - Issues

Next week:

  • finalisation of Healthix workflows incl. timeline

Additional Resources