Page Comparison

...

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 31 Mar 2016  (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
         4. •  S/ michele.foucart: Create a banner on Confluence with the message that code will be froozen as from day 31 Mar 2016 
              
            1. 1. Joao Cunha raises the issue regarding the audit message (Audit Message not generated when fetching eP CDA):

                  Jira Legacy
                  server JIRA (openncp.atlassian.net) serverId 5eab37ce-f509-3cbb-9925-c13d0f8d6d44 key AM-25

                  
                  
            2. The issue needs to be assigned to someone with experience with ePrescription
               •  Licinio Kustra Mano proposes to assign the issue to Konstantin Hyppönen
   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 19 Apr 2016 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:03 May 2016 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
         

...