Overview

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

Room:

Objective: Project updates and indepth discussions

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	https://openimis.atlassian.net/wiki/spaces/OP/pages/940048440	Updates & administrative things
14:05 (UTC)	40 min	Swiss TPH , https://openimis.atlassian.net/wiki/spaces/OP/pages/835387396	Project: 2024.T3b Solution Building
14:45 (UTC)	40 min	m4h , Y-Note , Tinker Technologies	Project: 2024.T4 Sandbox Setup
14:25	5 min		AOB

Minutes

working on initialization
- new Docker container called migration that will initialize and load the data if empty
- BE and worker will start only at the end of the initialization
next
- removing basic config from SQL files - load them as fixtures and part of BE
- PR open on claim module migration for Claim-AI solution

Last week we represented interoperability with Nepali vendor (Nyayahealth).
CHT-medic interoperability - record feedback from CHT side to openIMIS, in order to that, insuree code (present in card normally). From insuree code,cht will inquire Insuree uuid (patient uuid), through ?Patient=code.
Workflow described in Re: Medic / CHT Feedback → openIMIS - V1 | Comment . for CHT we will discuss in comming meeting. Propose json_ext? for field to be able to save feedback.
- To do : Update Workflow to design an openHIE workflow
- To do : Is it possible to apply for DCI standards for grievance ? Not clearly defined already as an interoperibility use case but can be design on openIMIS first. Will request DCI api development for Grievance
EMR / EHR Solution Simple form demo
- FHIR R4 compatibility
  - Challenges :
    - Support in uploading claim attachements (invoices0 in fhir
    - Coverage Request
    - Patient request
  - Demo of simple interface for Claim management through a dedicated UI

	File	Modified

No files shared here yet.