20160426 - Meeting minutes, Tuesday 26th March 2016 - Retrospective on CAT participation

OpenNCP liaison with IHE.

 

Estimated: 10:00 to 11:00 CET.

Performed:

Agenda:

  1. Feedback tests
    1. Results of the testing session in Bochum - Abderrazek
    2. planned vs.performed
    3. Issues
  2. Lessons learned, things to improve
  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.
------------------------------------------------------------------------------------------------

d

Joao Cunha

Kostas Karkaletsis

Tobias Pass

Massimiliano Masi

Abderrazek

S

michele.foucart

Meeting Notes:

  1. Results of the testing session in Bochum - Abderrazek presentation

  2. planned vs.performed
    1. Please see meeting minutes of the biweekly meeting : 20160418 - Meeting minutes, Monday, April 18th, 2016 - OpenNCP Community meeting (BiWeekly) I
  3. Issues
    1. Issue related to a probem with the MOC of the national infrastructure (between PT and AT) creating a problem with CDA document id, creating an id longer than 16 characters
      1. Had to cut the CDA ID in order to pass the test
      2. Issue reported in JIRA by Massimiliano Masi (OPENNCP-92)
    2. Some issues related to eP and eD messages
    3. Certificates:
      1. Validator used for validating the certificates vs. specs
      2. TSL editor, TSL SYNC  - 1 major issue
        1. By design does not import root certificate in case of self-signed certificate => need to import certificate manually (reason is that root certificate not certified by official authority)
          1. Massimiliano Masi: how do we know if it is a root self-signed certificate? Kostas Karkaletsis will check.
            1. We can create an issue and assign it to Massimiliano Masi.
        2. CDA level 1 validator:
          1. Topic discussed with Abderrazek & Giorgio after the Connectathon
            1. We are using the IHE Scanned Document specifications as reference to validate the tests.
              1. in previous Connectathon we were using the "friendly" validator
            2. There are elements specified in epSOS level 1 document, but the content of the PDF enclosed (the original document) to CDA level 1 (in particular the header of the CDA level1) is not specified
            3. We have to inform countries to use the correct specifications:
              1. http://www.epsos.eu/uploads/tx_epsosfileshare/D3.5.2_Appendix_B_Data_Elements_Correspondance_01.pdf
              2. epsos download area WP3.5 - http://www.epsos.eu/home/download-area/deliverables.html
              3. Scanned document template ids:
              4. Is the template id for scanned document correct?
                1. It was correct in epsos specs in 2011... some elements are missing, but the required documents should be present
                2. Kostas Karkaletsis: <templateId root="1.3.6.1.4.1.19376.1.5.3.1.1.1" />    <templateId root="1.3.6.1.4.1.19376.1.2.20" />  Scanning device of level 1 document - not described in the document according to Kostas
                3. @tobias: The same id is specified in the epSOS WP3.5 May 1rst 2010
            4. Extra elements to be displayed in the header are missing + all countries don't use these specifications because they miss this part of the document and are using the wrong template id...
            5. Update specs will be a big effort (lot of people will like to be implicated) but it would be the right approach in order to be able to verify against specifications
        3. Order services - AM 25 (can be closed) and AM 26 (new) - epsos code 32
          1. Joao Cunha: A hot fix was delivered in the we before the Connectathon - How do we include it in open ncp release?
            1. Kostas Karkaletsis proposes to do a release in RC1 or RC2 (release 2.4.1)
  4. Lessons learned, things to improve
    1. Massimiliano Masi: some test definition  that should be rewritten, ongoing task with eSENS
    2. S: Joao has done a guidance document for SPMS which is very usefull to execute the tests with Gazelle... It would be a good idea to share this document or to do a new one, especially for new participants
      1. Joao Cunha will check if this document is up to date and if it can be shared (as it is an internal document)