...
Objective: Weekly Co-ordination call of the Formal Sector developers
Participants:
Topic Proposals:
Date | Topic | Presenter | Comments |
|---|---|---|---|
verify field mapping after review | |||
align business processes (SOSYS - openIMIS) | |||
definitions (processes & fields) - eg. technical names | |||
Status of the Conceptualisation | |||
SOSYS presentationRoshan Kumar Thapa |
Presentations / Attachments
...
contract: Contract Module
coverage: FHIR R4 - Coverage
Workflows
claims:
hospitals will send claims directly to openIMIS, not through SOSYS
SOSYS receives the adjudication response ClaimResponse
accounting system is included in SOSYS
Master repositories
FS => SOSYS
Claim => openIMIS
APIs
APIs
need definition/documentation of SOSYS openIMIS API
Dependencies
Questions - Challenges - Issues
...
user roles: can django groups be used? Existing role + new ones
Next meeting (30.09.2020):
SOSYS presentation by SSF
use cases fromSOSYS-openIMIS API: on which side is the API and who makes the calls?
Missing data model from SOSYS:
existing in SOSYS: employer, contributor (see SOSYS-openIMIS API), dependants, claim (see SOSYS-openIMIS API)
maybe new in openIMIS FS: contract, payment validation
Requirements/Use cases need to be validated by Digital Square, but SSF, Djibouti, Myanmar and Implementer Committee could also be asked for validation (see Objectives in Formal Sector Modules (in development)
can be a guidance)
Dates for the use cases validation will be added on the FS wiki
Next meeting (07.10.2020):
Healthix: mapping tables (SOSYS → FHIR → openIMIS)
...