Overview

Date: 2025-03-25 - 14:00 am (UTC)

Room:

Objective: Project

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

• GIZ

  • @Uwe Wahser

  •  

• OPM

• Worldbank

  • @Wei Lu

• m4h , Y-Note , Tinker Technologies

  • @Sunil Parajuli

• Swiss TPH , SolDevelo

•  

  •  

Agenda:

Minutes

Admin Stuff

GAP Analysis

Swiss TPH - Project: 2024.T3b Solution Building

• https://github.com/openimis/solution-builder/tree/feature/web-configurator - javascript version (with UI for selection of solution)

• https://github.com/openimis/solution-builder/tree/develop - python CLI version

• Documentation on:

  • list of available pre-configured solutions, including brief summaries of objectives and functionalities of each solution

  • deploy a configuration on a Docker image

  • create a configuration (starting from scratch or from the default config of a pre-configured solution)

• suggestion: - The order of README content should be changed - to start from basic information about the module (openimis-pe-by) and dev set up requirements and steps, not starting from huge table of configuration

• menu: now it’s possible to change the icon for main menu and submenu items by adding “icon“ property. For example (name coming from name of component from material-ui lib):

  { "menus": [ { "position": 1, "id": "SocialProtectionMainMenu", "name": "Social Protection", "icon": "HowToReg", "description": "Social Protection", "submenus": [ { "position": 3, "id": "individual.api_imports", "icon": "Sync" }, { "position": 4, "id": "socialProtection.benefitPlans", "icon": "Assignment" }, { "position": 1, "id": "individual.individuals" }, { "position": 2, "id": "individual.groups" } ] }, ]}

  if icon isn’t defined in the config - the default icon from source code is taken. Example of configuration file:

• roles: need a default set of roles for a typical cash-transfer solution

m4h - Project: 2024.T4 Sandbox Setup

• Sandbox - use-case analysis - categories (registries / EHR/EMR system like openMRS / openCRVS?/ middleware i.e. openHIM / Financial / Dashboards like Apache Superset / DHIS2 interoperability usecases)

• Server Management - should be at first priority to install sandbox components.

  • Financial - accounting system → interoperability something like Ledger-cli but it’s not user friendly.

  • Financial - MIFOS (seen less implementation of mifos x)

• which BI component should we use?

• Suggestions : system component / workflow that can work together which is working (success i.e. like openhim, openmrs,) e-claiming workflow (pick anything that works best). Synthetic data generations is important and should take in consideration.
  
  

Questions

Presentations / Attachments

Additional Resources