Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Table of Contents
excludeContent

Schedule

Main event: 2024-01-22 - 2024-01-26 openIMIS/CORE-MIS Developers Workshop

Day 0, Monday, 2024-01-22, arrival & preparation
Excerpt
nameagenda

Start

End

Program

Who

Tools

arrivals

13:00

14:00

Lunch

14:00

17:00

Prepare the room

Review the workshop agenda

...

Start

End

Program

Who

Tools

09:00

10:30

Wrapping up & summaries

10:30

10:45

Coffee break

10:45

12:30

Securing all evidence

12:30

13:30

Lunch

Additional topic Requests:

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.

Program

Who (& Assistant)

Supporter

  • Contribution guidelines (naming conventions, ....)

  • Mobile apps

  • Review on the application of standards

  • How-To: openIMIS for the IT-System admin:

    • docker composition options, security, scaling options, monitoring...

  • How-To: openIMIS integration supported strategies and implementation options:

    • APIs (FHIR vs. GraphQL)

  • How-To: openIMIS integration supported strategies and implementation options:

    • Frontend specific: SSO, CORS, Proxy Pages, Connected 'widgets' (React Components),...

    • Backend specific: SSO, Impersonation,...

    • 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: backend "advanced" topics

    • How-To: frontend "advanced" topics

    • Review of the module overview

    Uwe Wahser

    • Review of the database scheme

    Uwe Wahser

    • Review of the high-level object diagram

    Uwe Wahser

    Uwe Wahser

    • Hackathon (parallel hands-on session: 3 to 4 functionalities, SolDevelo programming, WB desk-hopping )

      • functionality 1:

      • functionality 2:

      • functionality 3:

      • functionality 4:

    Andrea

    Uwe Wahser

    • Overarching Architecture: Scheme definition, Benefit Plan and enrolment into schemes Alignment proposal

    Patrick Delcroix

    Uwe Wahser

    Patrick Delcroix

    Relevant Resources

    Minutes

    Open topics / questions