OpenNCP liaison with IHE.
Estimated: 10:00 to 11:00 CET.
Performed:
Agenda:
- Feedback tests
- Results of the testing session in Bochum - Abderrazek
- planned vs.performed
- Issues
- Lessons learned, things to improve
- 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.
------------------------------------------------------------------------------------------------
Supporting document:
Participants:
Abderrazek
- Results of the testing session in Bochum - Abderrazek presentation
- planned vs.performed
- Please see meeting minutes of the biweekly meeting : 20160418 - Meeting minutes, Monday, April 18th, 2016 - OpenNCP Community meeting (BiWeekly) I
- Issues
- 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
- Had to cut the CDA ID in order to pass the test
- Issue reported in JIRA by Massimiliano Masi (OPENNCP-92)
- Some issues related to eP and eD messages
- Certificates:
- Validator used for validating the certificates vs. specs
- TSL editor, TSL SYNC - 1 major issue
- 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)
- Massimiliano Masi: how do we know if it is a root self-signed certificate? Kostas Karkaletsis will check.
- We can create an issue and assign it to Massimiliano Masi.
- Massimiliano Masi: how do we know if it is a root self-signed certificate? Kostas Karkaletsis will check.
- CDA level 1 validator:
- Topic discussed with Abderrazek & Giorgio after the Connectathon
- We are using the IHE Scanned Document specifications as reference to validate the tests.
- in previous Connectathon we were using the "friendly" validator
- 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
- We have to inform countries to use the correct specifications:
- http://www.epsos.eu/uploads/tx_epsosfileshare/D3.5.2_Appendix_B_Data_Elements_Correspondance_01.pdf
- epsos download area WP3.5 - http://www.epsos.eu/home/download-area/deliverables.html
- Scanned document template ids:
- Is the template id for scanned document correct?
- It was correct in epsos specs in 2011... some elements are missing, but the required documents should be present
- 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
- @tobias: The same id is specified in the epSOS WP3.5 May 1rst 2010
- 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...
- 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
- michele.foucart will open a task for this
- We are using the IHE Scanned Document specifications as reference to validate the tests.
- Topic discussed with Abderrazek & Giorgio after the Connectathon
- Order services - AM 25 (can be closed) and AM 26 (new) - epsos code 32
- Joao Cunha: A hot fix was delivered in the we before the Connectathon - How do we include it in open ncp release?
- Kostas Karkaletsis proposes to do a release in RC1 or RC2 (release 2.4.1)
- Joao Cunha: A hot fix was delivered in the we before the Connectathon - How do we include it in open ncp release?
- 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)
- 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
- Lessons learned, things to improve
- Massimiliano Masi: some test definition that should be rewritten, ongoing task with eSENS
- 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
- Joao Cunha will check if this document is up to date and if it can be shared (as it is an internal document)