20160226 - Meeting minutes, Friday, February 26th, 2016 - OpenNCP Steering Committee

OpenNCP Steering Committee Meeting

 

Estimated - 14:30 to 15:30 CET

Performed - xx to xx CET

AGENDA

  1. Connectathon
  2. Resources:
    • eSENS continuity
    • JASeHN assistance on the task forces
    • Dortmund university (terminology server)
  3. Continuity of eSENS
  4. Open NCP eID vision

 

LOCATION

  Adobe Connect

http://ec-wacs.adobeconnect.com/openncp/

Room Passcode:  markus.kalliola or Licinio Kustra Mano

----------------

If you have never attended an Adobe Connect meeting before:

Test your connection: http://ec-wacs.adobeconnect.com/common/help/en/support/meeting_test.htm

Get a quick overview: http://www.adobe.com/products/adobeconnect.html

Adobe, the Adobe logo, Acrobat and Adobe Connect are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States and/or other countries.

PARTICIPANTS

Today's Meeting Participants:

Licinio Kustra Mano

Soeren Bittins

markus.kalliola

michele.foucart

MEETING NOTES

  1. Connectathon
    1. Confirmation participation to the Connectathon:
      1. email sent
      2. EC will cover the costs for the system, MS will pay for their member costs, travel and accomodation
      3. Urgency to make the registration - 1 week to go to register
      4. We need at least 4 MS participating
    2. Need to highlight value added to participate to the event:
      1. From Portugal point of view :
        1. test eID level 2 that is now available
        2. Test 2.4.0 (previously we were testing the release candidate)
      2. Problem that it was not integrated tests:
        1. Components level 3, we need the back-end services but were not able to establish the connection quick enough
        2. Buit an offline tool to test. Online tool to test assersions and TSL...
        3. Ressources for eID testing, change request for eID testing should be to IHE to publish officially.
    3. Roundtable with the MS to see who wants to participate, to test eID level 2: PT will go, Austria may go, to check with Italy, CH won't go...
      1. 2 people from Fokus also present at the Connectathon Bochum, could also participate
    4. Monday bi-weekly meeting: underline again the value added to participate
      1. We would need to test by ourselves but we'll probably not have the test reports generated by IHE for the new functionalities
      2. eID level 2 should be ready for compliance testing, as value added for the Connectathon
        1. the tool is in principle already prepared for eID, already been done by EXPAND:
          1. Soeren Bittins confirms that all test artefacts are in place and ready for testing: TRC, ES-Trust RST, RSTR, signatures,WS-trust
          2. encompass from level 1 to level 3
        2. Next eHOMB meeting should be on the 8th April, too short before the Connectathon
    5. Licinio Kustra Mano will contact IHE, OpenNCP to see if we can include the eID tests for the Connectathon in Bochum
  2. Resources, having a view on the involvment in the different OpenNCP activities
    • eSENS continuity:
      • until level 3
      • if identify MS willing to participate in eID, will also commit to provide support to eID level 4 (mobile eID, connection with eIDAS). Software component, doc, support (bug fixing...)
      • People involved: olaf, raik, and soeren
      • We don't know from Portugal
    • MS contribution: From Portugal, 2 people working on the SMP and on the eID task force
    • JASeHN assistance on the task forces:
      • CEF ops support (task 5.6), participation in Steerco, Tech Committee + support specifically terminology but with no certainty yet
      • JASeHN is composed essentially of policy profiles, not technical profiles + question that this is core services tasks, covered by core services budget. Need to phrase it the right way: Core => generic. Need to sub-contract. "Pre-production testing" from the MS
      • Next JASeHN meeting:  where this topic can be discussed => Licinio proposes to draft the text, proposed to the agenda, and if they accept the point, see how we can do the presentation
    • Dortmund university (terminology server) - 120 md
    • EC (SANTE & DIGIT)
  3. Continuity of eSENS
    1. Licinio Kustra Mano: need to come back after the 15th March to talk about Continuity
  4. Open NCP eID vision
    1. Soeren Bittins: Technical problem with eID level 3: Too many technicians in the team in proportion to politiciens. How do we bring issues encountered? (We're reached the level of maturity and usability that we can. But feedback is that doctors don't want to use it? Not technical issue...)
    2. markus.kalliola: DIGIT analysis on compliance with eIDAS etc. but did not discuss the end-users acceptance problem. Cannot build different authentification scheme depending on the profession. This is the rationale behind eIDAS...
    3. Licinio Kustra Mano:
      1. as a country, will start field testing to see if feedback received is "theory" or corroborated on the field.
      2. Future: we should keep level 3 + use the mobile mechanism
      3. Are we able to build on previous levels to reach level 5 (mobile technology...)?
        1. From the practical point of view: most countries do have a card-based solution, with some problems
    4. We need to elaborate this topic in eSENS eID task force and scale it up at the different levels, discuss it also with DIGIT dealin with the topic. Problem not only for OpenNCP. In EC for instance we use ECAS and EID integrated in this authenticatino mechanism...
    5. Licinio Kustra Mano: Attention point that healthcare has unique requirements than any other sector does not have. e.g. patient inconscious not able to provide his credential, or even his eID...
    6. Licinio Kustra Mano: On the OpenNCP we need to provide a vision (from the NCP, from the patient centric vision), a clear view of what is possible, what is implementable.