Versions Compared

Key

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

OpenNCP Technical Committee Meeting

 

Estimated - 13:00 to 14:00 CET

Performed - 13:00 to 14:20 CET

AGENDA

1. Housekeeping (Rui)

2. Developments status

...

5. Next Meeting (Rui)

 

LOCATION
  •   Adobe Connect

PARTICIPANTS


Today's Meeting Participants:

...

Stéphane Spahni

Kostas Karkaletsis


OpenNCP Community Governance: 

  • From Jan. 2015 to Dec. 2015;
    • Nominated OpenNCP Committees: https://openncp.atlassian.net/wiki/x/DYANAg
    • Scope OpenNCP in EXPAND
      1. Take the OpenNCP to the next version;
      2. Assist and resolve any support issues that may arise;
      3. Handover to (DG-SANTÉ) for long term sustainability organisation;

 

FROM PREVIOUS MEETING:

Since we could not have the full Technical Committee on 3rd August (Stephane on holidays) no decisions were taken beyond the following guidelines:

a) During August, consolidate as much as possible the three open epics with e-SENS (NonRP, eID Level 1, SMP assessment), no new epics should be taken on board.

b) Meet as soon as everyone is back from holidays: September 2nd, 13h00 CEST.

MEETING NOTES

0.1. Overarching Vision

    • MISSION
      • Along epSOS:
        • Open group of people orchestrated by an agile software development methodology conducting effort on designing, coding, testing and delivering OpenNCP software

      • Beyond epSOS:
        • Open group of people orchestrated by common principles, conducting effort on designing, coding, testing and delivering eHealth Interoperability technology

    • VISION
      • Along epSOS:

        • Design and develop a set of Open Source Components (OpenNCP) that can be adopted by Participating Nation, to build their local implementation of the epSOS NCP.

      • Beyond epSOS:
        • Design, develop and sustain a set of open source components (OpenNCP) that can be adopted by anyone, to build an eHealth Information Exchange Point.

0.2. Development Roadmap

  • NATURE
    • NEW FEATURES
    • CONSOLIDATION (fix improvements)
  • Perspectives of discussions:
    • What MUST be ready by the end of 2015;
    • What SHOULD be included in 2016 roadmap;
  • RELEASE
    • ONLY 1 BRANCH...no different versions to be maintained.
  • RELAXATIONS (removal of)
    • CTS2 compliance.

2. Developments status

a. Non-Rep (Tech Committee + Alexandre + EC Team)

...

c. eID (if we have time, because there is a scheduled meeting about this for tomorrow);

 

3. Roadmap for 2015

a. Probably will be postponed until next week (Rui)

 

4. AOB

Marcello Melgara: Update/upgrade the display tool: must be available on the EXPANDATHON to test

...

Marcello Melgara: Point everybody how LAM is included in the Portal and LARMS as well. A discussion with Marcello and Alexandre...

  •  Rui

 

5. Next Meeting

...