Overview

Date: 28.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	Overall progess: working contract testing: mocks when possible database when complex structures (use available helpers, default + over-right specific fields) Helpers for new entity → Should we add that on the Contribute BE ? Versioning – https://django-simple-history.readthedocs.io/en/latest/ → 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 → to be integreted in the core 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

Mapping fields - add a column for SOSYS and put the name of the field instead of informing if FHIR field is available in SOSYS too
After completing all required fields in SOSYS and their match in FHIRR4, share the document with Nepal for feedback