Date: 28.10.2020
Objective: Weekly Co-ordination call of the Formal Sector developers
Participants:
Topic Proposals:
Date | Topic | Presenter | Comments |
|---|---|---|---|
verify field mapping after review | 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 | Overall progess: working contract Unit testing: How to create data
Versioning – https://django-simple-history.readthedocs.io/en/latest/ → should we Create a new VersionedUUIDModel ? Shell modules:
Other backend
Front end:
| ||
SOSYS presentation |
add contract entity in openIMIS data model?
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