Date: 07.10.2020
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 presentation |
contract: Contract Module
coverage: FHIR R4 - Coverage
SOSYS:
eligibility request openIMIS → SOSYS
if failed, openIMIS will manage
automated claims management (openIMIS)
invoice notice (openIMIS → SOSYS)
need definition/documentation of SOSYS openIMIS API
“c#”- Integration
SOSYS wants to use their system over openIMIS for employer management
SOSYS wishes only to send the “enrollment“ (insuree + dependent) data to openIMIS, the name of the employer could be included, all the insurance product are the same, → batch registration
SOSYS will provide a service that could be called automatically (every day)
SSF want still to be able to add manually data on openIMIS
SOSYS needs API need to replace an Excel file (content unknown), apparently from IMIS (Maybe excel reports for claims valuation)
Issues:
How openIMIS will know how to update the removed insuree
How openIMIS will keep the manual entry (not being erase by every day update)
Which kind of data will be sent every day, only the changes or full dump (clear performance risks)
SPTH formal sector will be useless, quick fix should be enough
funding function of openIMIS will be useless (relative pricing, matching funds, …)
https://wiki.ohie.org/display/SUB/Health+Financing+Workflows
Issues:
Enrollment should use the contract resource (From the FHIR page, enrollment is used the amend a contract by adding insuree)
Lacks the formal sector flows:
enroll company
group contract/enrollment including multiple offer (insurance product)
payments
Daniel Futerman How can propose updates ?
sign up to the openHIE wiki
join the monthly UHC call of openHIE (next one: Thursday at 16:00 CET):
SwissTPH
3 shell back end module delivered on github
Calculation module will use a function to manage the event error
Django signal are not run in parallel, meaning that the sender of the signal can check the result for the signal processing.
Healthix: mapping tables (SOSYS → FHIR → openIMIS) : https://docs.google.com/spreadsheets/d/157TQovOmWERJlxJ1VxbavsPjQUkD-f1o/edit#gid=1141968318