20160324 - Meeting minutes, Thursday 24th March 2016 - OpenNCP Task Force - eID.

Owned by Joao Cunha
Last updated: Sept 06, 2016 by S
3 min read

eID task force meeting.

 

Estimated: 16:00 to 17:00 CET.

Performed: 16:05 to 16h50 CET

Agenda:

  1. Monitor the progress towards the integration of eID Level 3;

  2. Plan joint effort towards IHE CAT on the 11th and 15th of April.
  3. Next Steps

Location:

  • AdobeConnect:

http://ec-wacs.adobeconnect.com/openncp/
Room Passcode:  Ask if necessary michele.foucart or markus.kalio
------------------------------------------------------------------------------------------------
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.
------------------------------------------------------------------------------------------------

Licinio Kustra Mano

Joao Cunha

S

michele.foucart

Meeting Notes:

  1. Monitor the progress towards the integration of eID Level 3;
    1. A new version will be available.
    2. Not update regarding the integration of level 3
    3.  The JNLP file has been downloaded, but it is similar to the file that we already have.
      • Joao Cunha will send the e-mail 
      • Licinio Kustra Mano will try to contact the artefact provider to see if everything has been published the right way.
    4. Plan B: use LAM level 2 to test again, with the risk that the new test prepared by IHE are not compliant to level2

  2. Plan joint effort towards IHE CAT on the 11th and 15th of April.
    1. We need the level 3 to be able to test. Austria is waiting a card reader to run pre-tests
    2. S raises the question regarding the version to be released and to be used for the Connectathon: 
      1. Licinio Kustra Mano suggests to close 2.4.0
        1. Last release candidate was last summer.
        2. Freeze the code on day   (e. eID level 2).
        3. Start release process the 13/03 and close it the 1rst of April, asking the Community members to test it before going to the Connectathon
          • S/ michele.foucart: Create a banner on Confluence with the message that code will be froozen as from day  
            1. Joao Cunha raises the issue regarding the audit message (Audit Message not generated when fetching eP CDA): AM-25 - Getting issue details... STATUS
          2. The issue needs to be assigned to someone with experience with ePrescription
    3. Scope Bochum : eID level 2
      • S: Ensure artefact eID is available on Joinup for download
  3. Different visions regarding eID:
    1. EIDAS, the Stork perspective, CEF eID BB...
    2. There is no consensus yet
    3. The following was agreed: eSENS will organize a meeting on  in order to bring a consolidated proposal on how eID should be used for eHealth. JASeHN will also participate to that meeting.
      1. After 19/04: eSENS will bring the proposal to OpenNCP Community and to eHOMB
      2. There is no sense to keep organizing eID task force before having clearance
        1. Next eID task force meeting should happen after Licinio brings the oucome of the eSENS/JASeHn eID focus meeting: 4pm CET
      3. Next eHOMB is scheduled on 8th April, so decision on eID will be taken at the next eHOMB meeting, ideally to be requested within the 2 weeks

Next Steps:

  1. Meetings:
      1. eSENS/JASeHn eID focus meeting
      2. eHOMB meeting ; next eHOMB meeting TBD
      1. 4pm CET eID task force meeting
      2. After 19/04: we'll bring the proposal to OpenNCP Community => Will it be accepted from eHOMB , OpenNCP... after that date, there will be no sense to keep eID task force before having clearance
      3. Next eID task force meeting should happen after Licinio brings the oucome of the eSENS/JASeHn eID focus meeting: 4pm CET
        1. eHOMB scheduled on 8th April => Need to request another eHOMB within 2 weeks
  2. ACTIONS