...
Objective: Align scope and roadmap for Formal Sector Integration
Participants:
Topic Proposals:
Date | Topic | Presenter | Comments |
---|---|---|---|
13.05.2020 | Overview of Formal Sector requirements from Nepal | GIZ Nepal | |
20.05.2020 | Gap analysis and conception for core modules | SwissTPH | |
27.05.2020 | Overview of the Product Roadmap for the openIMIS modular re-architecture | BlueSquare | |
03.06.2020 | Gap analysis and conception for APIs (I) | Healthix | |
10.06.2020 | Gap analysis and conception for APIs (II) | Healthix | |
Align the Product Roadmap |
Presentation
View file | ||
---|---|---|
|
Minutes
Entities
Workflows
Workflows: verify with https://wiki.ohie.org/display/SUB/Health+Financing+Workflows
claims management
APIs
Submit Claims
Track Claims
Dependencies
FHIRBox
Integration with existing structures
Questions - Challenges - Issues
Where did you find the information that the claim from insurees are sent to openIMIS ? same question for pension ?
From SOSYS processes. will be reviewed
What is the healthix fhir box ? an openIMIS module ? is internal or external to openIMIS?
Micro service external to openIMIS running on same server
Do you use the openIMIS FHIR module? How Healthix FHIR Box is interacting with openIMIS?
Why the assessment of the claim is done on SOSYS ? is it only about the valuated claims ?
why status not done from openIMIS ? I believed that the employer has access to SOSYS, is it also the case provider ?
Do you need any batch (or scheduled) processing (sys admin point of view) in openIMIS? [!! capability will be added to the stack along Beneficiary Enrollment migration, expected delivery: 08/2020]
Next week:
Additional Resources
...