Overview

Date: 22.03.2021

Objective: Weekly Co-ordination call of the Formal Sector developers

Participants:

Topic Proposals:

#	Topic	Presenter	Comments

#	Topic	Presenter	Comments
1	https://openimis.atlassian.net/wiki/spaces/OP/pages/2161147963 Interoperability openIMIS - SOSYS	@dave mutinda	Healthix project progress
2	https://openimis.atlassian.net/wiki/spaces/OP/pages/2161147938	@Patrick Delcroix	STPH project progress
3
4	AOB

Presentations / Attachments

	File	Modified

No files shared here yet.

In the architecture, OpenMRS should not connect through OpenHIM too?
FHIR STU3 was already migrated to FHIR R4. Scope to extend the FHIR R4 module?
- based on the work of FHIR4 project
FHIR Patient already there. What usage for FHIR Person?
- Please fix in the interaction diagram
Organisation is FS PolicyHolder?
Remaining FHIR R4 resources (affiliation)?
- Group: done
- organisationAffiliation: clarification needed
- Contract: not done (need adaptation to support FS for GET, and PUSH/PUT not implemented)
What is manual trigger doing in OpenHIM?
- Scheduling where openHIM is the trigger (@dave mutinda can you confirm?)
How the benefit is sent from Healthix? Which FHIR resource?
- POST FHIR Coverage (coverage has limitation, it is more to get what the patient can get: how many surgery left … , contract will be better)
How do you know the details of a Claim: diag, services, items, insuree, etc. ?
- Get references from ClaimResponse (received through OpenHIM) and get details directly from openIMIS
Will publish both Python and Node mediators?
- R4 update (to be reviewed, AP SwissTPH)
- Python mediator: (to be reviewed, AP SwissTPH)
- Node mediator: (I don’t find it on github, @Davis Mutuku did you pushed it ?)