Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 21 Next »

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:

  • discuss acute openIMIS issues in the developers community
  • introduce the openIMIS developers to the openHIE developers
  • present the openIMIS October release to the openHIE community
  • test run openIMIS interoperability with other openHIE Global Goods
  • on-board new developer teams that will have joined the openIMIS initiative through the Digital Square RFA#2019-16 ("Notice D1")
  • bonding: enjoy Ethiopian food and understand the dangers of tella, tej and katikala

Schedule

Day 0, Monday, 04.11. arrival & preparation

  • openHIE: OpenHIE Academy Intro Courses
StartEndProgramWhoTools


arrivals, (feel free to participate in academy sessions, if you are already there)

13:0014:15Lunch & group photoOpenHIE


Prepare the roomDevelopers Committee
15:3015:45Coffee breakOpenHIE
15:4517:00Review the openIMIS DC scheduleDevelopers Committee

Day 1, Tuesday, 05.11. OpenHIE opening ceremony & selected presentations

  • openHIE: OpenHIE opening ceremony
StartEndProgramWho (& Assistant)Tools
08:3010:30OpenHIE opening & introductionOpenHIE
10:3011:15Coffee break & unconference votingOpenHIE
11:1511:45Project overview & updatesUwe Wahser
11:4512:45openIMIS round of introductionsDevelopers Committee
12:4513:30Lunch & group photoOpenHIE



openIMIS
15:0015:15Coffee breakOpenHIE



openIMIS

Day 2, Wednesday, 06.11.


StartEndProgramWho (& Assistant)Tools





10:1510:45Coffee break






12:3014:00Lunch






Day 3, Thursday, 07.11.


StartEndProgramWho (& Assistant)Tools





11:0013:00Lunch






Day 4: Friday, 08.11. *-a-thon

Day 5: Saturday, 09.11. Wrap-up & Departure

Additional topic Requests: Doodle to select topics

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 how 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.

StartEndProgramWho (& 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.







  • 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







Relevant Resources

  • No labels