2020-10-28 Formal Sector Developers Call
Overview
Date: 28.10.2020
Objective: Weekly Co-ordination call of the Formal Sector developers
Participants:
@Uwe Wahser
@Luciana Rajula
@Patrick Delcroix
@Doreen G. Wamiti
@dave mutinda
@Eric Darchis
@Maguette T. NDONG
Topic Proposals:
Date | Topic | Presenter | Comments |
---|---|---|---|
| verify field mapping after review | @dave mutinda | Healthix: mapping tables (SOSYS → FHIR → openIMIS) : FHIR4 fields mapping.xlsx
|
| 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
Versioning – https://django-simple-history.readthedocs.io/en/latest/ → should we Create a new VersionedUUIDModel ? Shell modules:
Other backend
Front end:
|
| SOSYS presentation |
|
|
Presentations / Attachments
Minutes
Entities
add contract entity in openIMIS data model?
Workflows
APIs
Testing
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 orproduct_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.
Questions - Challenges - Issues
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
Next meeting (28.10.2020):
Additional Resources
Did you encounter a problem or do you have a suggestion?
Please contact our Service Desk
This work is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License. https://creativecommons.org/licenses/by-sa/4.0/