Overview

Date: 21.10.2020

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

Participants:

Topic Proposals:

Topic	Presenter	Comments
verify field mapping after review	dave mutinda	Healthix: mapping tables (SOSYS → FHIR → openIMIS) : https://docs.google.com/spreadsheets/d/157TQovOmWERJlxJ1VxbavsPjQUkD-f1o/edit#gid=1141968318
align business processes (SOSYS - openIMIS)
definitions (processes & fields) - eg. technical names
Status of the Conceptualization	Patrick Delcroix	Versioning --https://code.djangoproject.com/wiki/AuditTrail → should we Create a new VersionedUUIDModel ? Shell modules: https://github.com/openimis/openimis-be-contract_py : Shell delivered, working on graphQL https://github.com/openimis/openimis-be-policyholder_py : shell delivered https://github.com/openimis/openimis-be-contribution_plan_py : Shell delivered Other backend https://github.com/openimis/openimis-be-calculation_py : empty module Profile Front end: Not yet available
SOSYS presentation

Presentations / Attachments

	File	Modified

You are not logged in. Any changes you make will be marked as anonymous. You may want to Log In if you already have an account.

No files shared here yet.

Drag and drop to upload or browse for files

How openIMIS will know how to update the removed insuree

How openIMIS will keep the manual entry (not being erase by every day update)
Which kind of data will be sent every day, only the changes or full dump (clear performance risks)
SPTH formal sector will be useless, quick fix should be enough
funding function of openIMIS will be useless (relative pricing, matching funds, …)