20160405 - Meeting minutes, Tuesday, April 5th March, 2016 - OpenNCP Steering Committee

OpenNCP Steering Committee Meeting

 

Estimated - 16:00 to 17:00 CET

Performed - 16:05 to 16:50 CET

AGENDA

  1. Connectathon
  2. eHOMB 8/4
  3. Issue AM-25 audit message not generated when fetching eP CDA  AM-25 - Getting issue details... STATUS
  4. Operational issues with the current TS (also mentioned in bi-weekly meeting 29/02: https://openncp.atlassian.net/wiki/pages/editpage.action?pageId=78479381)
  5. epsos expand central services
  6. Change proposals
    1. Process
    2. CP already received
  7. Release 2.4.0
  8. Joinup admin rights
  9. Release planning (OpenNCP issues updated + 34 issues still to be discussed in technical Committee)

 

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. 4 MS: PT, AU, DK, CY, DG SANTE
      1. Will monitor DK an CY
      2. Side event on Tuesday where Markus will present
    2. Close and test 2.4.0
    3. Close and test eID level 3
  2. eHOMB 8/4
    1. Go through the draft agenda of next eHOMB
    2. Comment regarding topic "DIGIT MoU1 & 2" & eID:
      1. eSens project is testing features that we can include in the eHDSI
        1. Soeren Bittins: results are a bit disappointing
          1. Lot of effort to be aligned with BB digital signature...waiting feedback on what to do on the new software. The BB only flow into 1 direction + there need an extension in the BB. At the end we might end up by not meeting our requirements
      2. Discussion liaison eID with eHDSI
        markus.kalliola proposes to Licinio Kustra Mano to introduce the eID topic and see with teh participants specific actions to work on the liaison.
        • Licinio wil prepare a short message o introduce and stress the eSens CEF eHDSI liaison opportunity
  3. Issue AM-25 audit message not generated when fetching eP CDA  AM-25 - Getting issue details... STATUS
    1. No eP expert, task assigned to Konstantin but without success. May impact test on ePrescription. No outcome, and don't know who we could target...
      • michele.foucart will send the request to the Technical Committee still today
        1. If no answer: Send the request to the OpenNCP Community for help
  4. Operational issues with the current TS (also mentioned in bi-weekly meeting 29/02: https://openncp.atlassian.net/wiki/pages/editpage.action?pageId=78479381)
    1. Syncro problem raised months ago, but has never been fixed (no update from Carecom)
      1. Check the database structure of the LTR, needs to be optimized (impact on the conception of OpenNCP => to be included in EPICs (1 LTR, 1 synchro)  => Soeren Bittins suggests to the technical team to analyse this closely
    2. Now Carecom contract has ended. Discussion ongoing with Carecom on how we could get the back-up from them.
    3. Licinio Kustra Mano: the issue is more a bandwidth problem. More important is to get the back-up of MS
  5. Change proposals - Not discussed
    1. Process
    2. CP already received
  6. Release 2.4.0
    1. Recommendation for a public communication as soon as 2.4.0 has been tested, after the Connecttahon
    2. Restriced communication to the participants to the Connectathon to ensure they install the correct version
  7. Joinup admin rights - contact Joinup to explain epsos expand context, and ask the creation of a new user explicit from DG SANTE
  8. Release planning (OpenNCP issues updated + 34 issues still to be discussed in technical Committee) - Not discussed
    1. Feedback received from most of the members.
    2. Revert to Soeren if something is not clear in the feedback received