Overview

Date: 16.09.2020

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

Participants:

Topic Proposals:

Date	Topic	Presenter	Comments

Date	Topic	Presenter
16.09.2020	verify field mapping after review	@dave mutinda
	align business processes (SOSYS - openIMIS)
	definitions (processes & fields) - eg. technical names
	Status of the Conceptualisation	@Patrick Delcroix

Presentations / Attachments

	File	Modified

No files shared here yet.

contract: Contract Module
coverage: FHIR R4 - Coveragearchived
missing fields will be mapped from openIMIS according to:
- the data item must be required by SOSYS
- the data item must be available in the openIMIS data model or can be generated from there
- extensions in FHIR if the field is not available in FHIR

clearer definition on distribution of workflows:
- which workflows are needed?
- which system is doing which step of the process?

FHIR implementation review: need to map FHIR4 - openIMIS DB tables
- openIMIS FHIR R4 Overview Page

more information on SOSYS data needed
- SSF SOP can be found there:Employment Injury Insurance - Social Security Fund Nepal
Master-slave system repository (data responsibility)

SOSYS presentation by SSF
- use cases from Formal Sector Modules can be a guidance
Healthix: mapping tables (SOSYS → FHIR → openIMIS)