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

...

3. NEXT RELEASE (Alexandre)

4. Pre-EXPANDathon Tests (Kostas)

5. AOB

6. Next Meeting (Rui)

 

LOCATION
  •   Adobe Connect

PARTICIPANTS


Today's Meeting Participants:

...

Licinio Kustra Mano

Konstantin Hyppönen

 

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. CDA Display Tool Update + Model-Based Validator (Kostas + Tech Committee + EC Team)

...

  • Kostas Karkaletsis:
    •  Started Pre-EXP Tests and validate tokens - found some issues.
    • Issues needed to be fixed - policy files.
    • I will change them and commit them...
    • Proxy feature...
    • Is this going to be included? Or only the Non-Rep changes... 
    • They affect all the components that have dependencies on epSOS UTILS

3. PRE EXPANDATHON TESTS

...

    • Is IHE/EXPAND will send and e-mail to participants in order to express what to test, which version will be tested, in which day tests ...
    • Request answer from them, that they agree...
    • Kostas Karkaletsis: Pre-EXP Tests are specifically for this.

 

4.  NEXT RELEASE

END OF THIS WEEK - will be communicated to the community.

5. AOB

  • Marcello Melgara (About eID)
    • Also my workflow (I sent in the mail) - we are changing the workflow - DESCRIBE THE WORKFLOW IN CASE OF EMERGENCY
    • PIN CODE is requested only once... We must be rigorous about this - This is CRITICAL! Must be done in a controled way...
    • Show something in Lisbon that does not comply... We will miss the value of "showing something"...
    • Alexandre Santos: Possibly we'll need to skip LAM+
    • Marcello Melgara: Legal issue is very complex - LAM for Emergency only (just for now)
    • Alexandre Santos: Not the most user-friendly, but got from Soeren that all those screens are needed for legal issues, patient consent... 

5. Next Meeting

...