Versions Compared

Key

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

...

Aim & Objectives

Excerpt

Aim:

  • Co-ordinate activities of the second phase of the CORE-MIS migration project

Objectives:

  • review roadmap, sprints and timeline for the prioritized modules in detail

  • review technology and architecture

  • review operational procedures for the project

Approach:

  • WB team to present GAP analysis

  • Soldevelo to present technology choices

  • Discussion (implementation and timeline)

Schedule

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

...

Start

...

End

...

Program

...

Who

...

Tools

...

arrivals

...

13:00

...

14:00

...

Lunch

...

14:00

...

17:00

Prepare the room

...

(->)

Insert excerpt
2024-01-22 openIMIS/CORE-MIS Developers Workshop - Day 0, Monday
2024-01-22 openIMIS/CORE-MIS Developers Workshop - Day 0, Monday
nameagenda
nopaneltrue

Day 1, Tuesday, 2024-01-23

...

Minutes:

...

Start

...

End

...

Program

...

Who

...

Tools

...

09:00

...

09:30

...

Official welcome and introductions

...

09:30

...

10:15

...

Review and finalisation of the agenda

...

10:30

...

10:45

...

Coffee break

...

10:45

...

12:30

...

12:30

...

13:30

...

Lunch

...

13:30

...

15:30

...

15:30

...

15:45

...

Coffee break

...

15:45

...

18:00

(->)

Insert excerpt
2024-01-23 openIMIS/CORE-MIS Developers Workshop - Day 1, Tuesday
2024-01-23 openIMIS/CORE-MIS Developers Workshop - Day 1, Tuesday
nameagenda
nopaneltrue

Day 2, Wednesday, 2024-01-24

...

Minutes:

...

Start

...

End

...

Program

...

Who

...

Tools

...

09:00

...

10:30

...

10:30

...

10:45

...

Coffee break

...

10:45

...

12:30

...

12:30

...

13:30

...

Lunch

...

13:30

...

15:30

...

15:30

...

15:45

...

Coffee break

...

15:45

...

18:00

(->)

Insert excerpt
2024-01-24 openIMIS/CORE-MIS Developers Workshop - Day 2, Wednesday
2024-01-24 openIMIS/CORE-MIS Developers Workshop - Day 2, Wednesday
nameagenda
nopaneltrue

Day 3, Thursday, 2024-01-25

...

minutes:

...

Start

...

End

...

Program

...

Who

...

Tools

...

09:00

...

10:00

...

10:00

...

11:00

...

Weekly Developers' Call

...

11:00

...

11:15

...

Coffee break

...

11:15

...

12:30

...

12:30

...

13:30

...

Lunch

...

13:30

...

15:30

...

15:30

...

15:45

...

Coffee break

...

15:45

...

18:00

(->)

Insert excerpt
2024-01-25 openIMIS/CORE-MIS Developers Workshop - Day 3, Thursday
2024-01-25 openIMIS/CORE-MIS Developers Workshop - Day 3, Thursday
nameagenda
nopaneltrue

Day 4: Friday, 2024-

...

01-

...

26, Wrap up & Departure

...

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

...

(->)

Insert excerpt
2024-01-26 openIMIS/CORE-MIS Developers Workshop - Day 4, Friday
2024-01-26 openIMIS/CORE-MIS Developers Workshop - Day 4, Friday
nameagenda
nopaneltrue

Additional topic Requests:

...

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

...