Overview

Date: 28.10.2020

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

Participants:

Topic Proposals:

Date	Topic	Presenter	Comments

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 Unit testing: How to create data sequence script to initialized location …. (demo database) (AP demo data Patrick) 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 : Shell delivered Other backend : empty module Profile → to be integreted in the core Front end: Not yet available
SOSYS presentation

Presentations / Attachments

	File	Modified

No files shared here yet.

Bluesquare used three ways to create test data: demo DB script (like locations that are always the same), mocks (when practical), test_helpers that allow to create custom data like create_test_insuree() that uses sensible defaults or product_service = create_test_product_service(product, service, custom_props={"limit_no_adult": 20}) that allows to customize any field. Devs to exchange and agree how to align on those.

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