Overview

Date: 2025-04-08 - 14:00 am (UTC)

Room:

Objective: Project

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

Agenda:

When (UTC)	Duration	Who	Topic

When (UTC)	Duration	Who	Topic
14:00 (UTC)	5 min	GIZ	Updates & administrative things
14:05 (UTC)	40 min	Swiss TPH , SolDevelo	Project: 2024.T3b Solution Building
14:45 (UTC)	40 min	m4h , Y-Note , Tinker Technologies	https://openimis.atlassian.net/wiki/spaces/OP/pages/4059955305
14:25	5 min		AOB

Minutes

worked on migrations to remove constraints on the FKs
Social Health Insurance:
- ClaimAdmin is attached to User but is managed by Claim module
- Location and HF are managed by same module and there are many dependencies with other modules “killing” the modularity for the solution when you don’t need modules to be loaded
- we need to remove the hard links to sub-locations such as HF, payment points, service points
- location access has to be reworked for ClaimAdmin and restrict the location check
- looking for a generic solution to support developers with best practices (from core functionalities) to manage specific User types and other specificities to core entities
  to be discussed in a DeepDive meeting and estimate no of days
Wiki Spaces
- one Space per solution
- combining components from different spaces (e.g. user documentation from KB space) with specifics
next solution: Claim-AI
- https://openimis.atlassian.net/wiki/spaces/OP/pages/1448542777

Worked on Benchmarking of EMR/EHR for a solution - for interoperability for openIMIS
Looked a few details into openMRS for interoperability - FHIR , https://openimis.atlassian.net/wiki/spaces/OP/pages/4323704834
Need to define context for pros and cons of each possible solution.
openMRS had old module - prototype which is not usable as of now
Master Register that includes - locations Management from master registry, - need to choose the best one. https://openimis.atlassian.net/wiki/spaces/OP/pages/4323999757

	File	Modified

No files shared here yet.