...
Feel free to add sessions in a new line at the end of the table. If you feel that a certain session is especially important, kindly add your name to the supporters. You can also propose a moderator / presenter or volunteer for a session in the 'Who' column. We'll then see who to best slot it into the above schedule. If you feel responsible to take over a session as moderator, you might also want to create a sub-page for the session.
Start | End | Program | Who (& Assistant) | Supporter |
---|
|
| - 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?
|
|
|
|
| |
| |
|
| - Review on the use of platforms
- Wiki, Localize, Drive, Forum etc.
|
|
|
|
| - Review on the application of standards
|
| |
|
| - How-To: how to define front end and backend module in order to increase the visibility to implementers
|
|
|
|
| - How-To: openIMIS for the IT-System admin:
- docker composition options, security, scaling options, monitoring... and interactions with 'legacy' platform (front and database)
|
|
|
|
| - How-To: 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)
|
| |
|
| - How-To: building (from scratch) a backend module to customize claim validation rules (i.e. replace reference one)
- events (django signals)
- backend module configuration
|
| |
|
| - How-To: providing a "language pack" frontend module
|
|
|
|
| - How-To: 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"
|
| |
|
| - How-To: openIMIS integration options and challenges (backend/frontend, with/without SSO) and developing a small prototype integration to *** (to be defined)
|
| |
|
| - How-To: backend "advanced" topics:
- transactional/non-transactional signals
- synchronous/asynchronous mutation processing
- batches
|
|
|
|
| - How-To: 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
|
|
|
|
|
|
|
|
...