The program will be back-to-back with the OpenHIE Conference in Addis. We are in the process of aligning our schedule to that of OpenHIE (real-time version on their wiki), so that both events can profit as much as possible from each other. While the openIMIS sessions are generally open to the OpenHIE community (depending on the size of the room), members of the openIMIS Developers Committee are requested to be present during the openIMIS sessions.
We will try to reflect changes of the OpenHIE schedule as appropriate.Therefore this page will be frequently updated. During the workshop we suggest to keep it open on your phones and to refresh it from time to time. There will be no printout.
Co-ordinates
Dates: 04.11.2019 - 09.11.2019
Venue: OpenHIE Conference 2019, Addis Abeba, Ethiopia
Hotel: Hyatt Regency, Addis Ababa
Participants: Developers Committee & associates
Aim & Objectives
Linking the workshop of the openIMIS Developers Committee to the 2019 OpenHIE workshop aims at gaining momentum from combining the two conferences. A lot of the 2019 development activities in openIMIS focused around creating interoperability with other global goods in the OpenHIE eco-system, namely OpenMRS, Bahmni and DHIS2. The results of these efforts are published in the October release of openIMIS. The OpenHIE connect-a-thon provides an ideal setting for testing the new features with the support of experts from the other projects and allows to make the OpenIMIS package know to a wider audience of eHealth experts. Specific objectives are:
Schedule
Day 0, Monday, 04.11. arrival & preparation
- openHIE: OpenHIE Academy Intro Courses
Start | End | Program | Who | Tools |
---|---|---|---|---|
arrivals, (feel free to participate in academy sessions, if you are already there) | ||||
13:00 | 14:15 | Lunch & group photo | OpenHIE | |
Prepare the room | Developers Committee | |||
15:30 | 15:45 | Coffee break | OpenHIE | |
15:45 | 17:00 | Review the openIMIS DC schedule | Developers Committee |
Day 1, Tuesday, 05.11. OpenHIE opening ceremony & selected presentations
- openHIE: OpenHIE opening ceremony
Start | End | Program | Who (& Assistant) | Tools |
---|---|---|---|---|
08:30 | 10:30 | OpenHIE opening & introduction | OpenHIE | |
10:30 | 11:15 | Coffee break & unconference voting | OpenHIE | |
11:15 | 11:45 | Project overview & updates | Uwe Wahser | |
11:45 | 12:45 | openIMIS round of introductions | Developers Committee | |
12:45 | 13:30 | Lunch & group photo | OpenHIE | |
openIMIS | ||||
15:00 | 15:15 | Coffee break | OpenHIE | |
openIMIS |
Day 2, Wednesday, 06.11.
Start | End | Program | Who (& Assistant) | Tools |
---|---|---|---|---|
10:15 | 10:45 | Coffee break | ||
12:30 | 14:00 | Lunch | ||
Day 3, Thursday, 07.11.
Start | End | Program | Who (& Assistant) | Tools |
---|---|---|---|---|
11:00 | 13:00 | Lunch | ||
Day 4: Friday, 08.11. *-a-thon
Day 5: Saturday, 09.11. Wrap-up & Departure
Additional topic Requests: Doodle to select topics
- Contribution guidelines (naming conventions, ....)
- openIMIS-DHIS2 integration
- Integrate the connectors to DHIS2 into openIMIS repositories?
- DHIS2 as DWH 'module' of openIMIS. Where/how to put the code (technical connectivity and DHIS2 configurations)
- Mobile apps
- current state, future, what do people want to do?
- offline requirements - how are other mobile apps handling mobile & offline scenarios?
- Overview and update on the Target (modular) Architecture
- Review on the use of platforms
- Wiki, Localize, Drive, Forum etc.
- Review on the application of standards
- HL7 FHIR, JLN Process Framework
- Howtos (in new development architecture)
- how to define front end and backend module in order to increase the visibility to implementers
- openIMIS for the IT-System admin:
- docker composition options, security, scaling options, monitoring... and interactions with 'legacy' platform (front and database)
- new openIMIS integration supported strategies and implementation options:
- Frontend specific: SSO, CORS, Proxy Pages, Connected 'widgets' (React Components),...
- Backend specific: SSO, Impersonation,...
- APIs (FHIR vs. GrapQL)
- Exposing internal events (towards micro services integration)
- building (from scratch) a backend module to customize claim validation rules (i.e. replace reference one)
- events (django signals)
- backend module configuration
- providing a "language pack" frontend module
- building (from scratch) a brand new 'FOO' (to keep it simple) complete module, in relationship (FK) of another module (claim or whatever)
- backend: new django model, registering GraphQL (queries and mutations)
- frontend:
- basic contributions entries (main menu,...)
- simple "constant-based" picker
- using pickers from other module
- sending mutations via the "journal"
- openIMIS integration options and challenges (backend/frontend, with/without SSO) and developing a small prototype integration to *** (to be defined)
- backend "advanced" topics:
- transactional/non-transactional signals
- synchronous/asynchronous mutation processing
- batches
- frontend "advanced" topics
- core.Boot contribution, what to do with it (and what not)
- pickers with or without cache (product list vs. health facilities list)
- dialog-pickers, suggestions-based pickers (with debounce, minimal chars#,...)
- Progressive Web Application
- Other topics:
- ...