OpenNCP Community meeting (BiWeekly)

29 Mar 2016 

Estimated - 14:00 to 15:00 CET

Performed - 14:05 to 15:24 CET

AGENDA

1. Housekeeping
2. Connectathon 
   1. Meeting preparation
   2. Scope: eID..
   3. Release
   4. Social event
3. Release Management
   
   1. Release Management Process:
      1. OpenNCP parent pom
      2. Commit mode (pull requests develop branch or direct push from authorized dev to develop)
   2. Release-2.4.0
      1. Security
      2. CDA?
4. Change proposals
   1. National connector and workflow manager
   2. Cache implementation - Status
   3. Message signature
   4. eID
5. Performance test results
6. Terminology synchronization problems => JIRA issue
7. Technical Committee 21/03 - update JIRA issues
8. Status task forces
   1. SMP/SML
   2. Security
   3. Terminology server
   4. eID
9. AOB
10. Next meetings
    
    

...

Marcello Melgara

MEETING NOTES

1. Housekeeping
   
   
2. Connectathon 
   1. Meeting preparation
      1. 2PN fully registered (Portugal & Austria) + DG SANTE + Cyprus 50% registration completed
      2. Doubt on Denmark's participation because they did not complete the registration of their tests in Gazelle and we did not registration not fullfilled + no feedbackFull set of test will be testedhave contact with them since their registration
      3. No meeting again before the Connectathon, but input . Input progress will be done via e-mail + meeting scheduled after the Connectathon
      Scope: eID..
      2. Post-Connectathon meeting scheduled on 26/04, with the following agenda: Retrospective on CAT participation, thinks to improve for the next participation
   2. Scope: Full set of test will be tested: ePrescription, Patient Summary, non-repudiation, SMP/SML, eID
   3. Release freeze 31/03, release RC 2.4.0
      
      1. eID successfully integrated in OpenNCP portal + successfully tested successfully on Portugal side => This release will close the component BB?
         1. 1 bug on eID component was found, but under investigation
   4. Social event Thursday, 14 April 2016
      
      
3. Release Management
   
   1. Release Management Process of the organization of the OpenNCP project itself
      
      1. OpenNCP parent pom
         1. Will help the release procedure, and will clarify which version of the component is being used, having all the same version of components
            1. On the one side hand it is good to have the same version of all components
            2. On the other sidehand, if we do a release, we need to release components that haven't change
         2. What about a release number on 2 parts (OpenNCP release/internal component release). If we have different versions of components yes.
         3. Release number only on the war file
      2. Commit mode (pull requests develop branch or direct push from authorized dev developers to develop)
      3. Process: use AS IS process, where only authorized developers can contribute/commit.
      4. Topic to be discussed on the next Technical Committee meeting + update documentation regarding release management process accordingly
   2. ReleaseContent of release-2.4.0
      
      1. Security fixes and configuration
      2. eID level 3
      3. CDA?
         
         1. Situation December: we have fixed the 3 main issues in the CDA display tool raised by Marcello
         2. Marcello discovered an issue on translation. Items not correctly translated from different sources; Marcello highlighted a discrepancy between the xml file and the CDA specificationsWhat is the issue number?
         3. Conclusion:
            1. Close the issues that have been fixed and include it in the release
            2. Translation issue (related to CDA) - Open a new issue (even if it is outside the CDA tool)
      4. Communication:
         1. Update the installation manual (e.g. Liferay configuration)
         + publish
         2. Publish a keynote announcing the new version of OpenNCP, inviting PN to use this version and/or to join the Community (suggested timing: after Bochum)
            •  michele.foucart and S
              
         3. Announcement in the June IHE world summit Announcement + in Bochum
            
            
4. Change proposals
   1. Change proposal process? Published Change proposal process (work in progress) to be proposed at the eHOMB meeting on the 8th April
      1. Cf http://ec.europa.eu/health/ehealth/docs/ev_20151123_co02_en.pdf + p9
   2. Change proposal already submitted
      
      1. National connector and workflow manager
      2. Cache implementation - Status
         1. source code was already published, tests to be completed and shared on Confluence
      3. Message signature
         1. Ongoing analysis on DIGIT side;
         2. We will share the CP with DIGIT for analysis => To ???
      4. eID
         1. Ongoing analysis on DIGIT side;
         2. We will share the CP with DIGIT for analysis => To Sophie
      5. Next eHOMB we should receive a status from DIGIT on their analysis
         
         
5. Performance test results
   1. New YacoubouY executed new stress test performed last week with Neoload
   2. View PS, view ePrescriptoipePrescription,
      1. 1 - 10; 25 concurrent users during 20 minutes
      2. Good results, snce since performance improved compared to the tests results from Q4 2015, essentially due to the configuration updates
      3. What was tested was the OpenNCP performance it selfitself, not a test with National interfaces
         
         1. Stéphane Spahni: first request, certificate needs to be generated, cannot be anticipated. This is linked to the national patient record infrastructure where the caller has to be identifiable (not linked to the OpenNCP). It is linked to the HCP, pharmacist, clinician. Not linked to the patient. User info kept a few week, can be configured.)
         2. Do we have the same problem with other NCPs? It depends on the access... Not a problem encountered by Malta for instance.
            
            
6. Technical Committee 21/03 - update JIRA issues
   1. We went through the JIRA issue list and every assignee will update their own issues.
   2. The issues assigned to people having left the community will be reassigned.
   3. S will also contact Konstantin to update his issues.
      
      
7. Status task forces
   1. SMP/SML - No update
   2. Security - No update
   3. Terminology server - No update
   4. eID
      1. Audit messaged to failed to be generated in the eHealth use case
      2. Has anyone tested this and encountered the problem? Impact the Connectathon for the ePrescription use case
      3. S sent an e-mail to Constantine AM-25 !!!
   5. CI - Not the time to discuss
      
      
8. AOB
   1. Central services hosted at CONET
      1. 1. We can start using EC configuration services
      => To be mentioned in the meeting minutes + installation manual needs to be updated with the urls
      2. Portugal has already uploaded certificates successfully
      3. 1. : URL: https://webgate.ec.europa.eu/ehealth/tsl 
            •  S will update the installation manual with the urls, the modifications of the configuration etc.
         2. Austria, Croatia, Greece, Malta, Portugal and Switzerland who have updated successfully their TSL file
   2. Terminology server Carecom stops until the end of March => By April, the services will be shut down
      1. Not Crucial for the Connectathon but if new country, we will need to do the synchro synchronization by hand, as long as we don't have the SMP/SML solution in place
      2. 1. Croatia had a problem, which is resolved
         2. But now the problem is that the synchronization takes long 
         3. MVC to be used: version 1.8
            1. Accessible from the download zone
            2. Marcello Melgara: More It is more a question on what has been done on MVC 2.0 (webservices to access MVC 2.0 not yet unable)
               1. Check with Carecom what they suggest to do?
               2. Suggestion from markus.kalliola to have the xls file for 1.8 and 2.0
         4. => Terminology server task force could will enter into relation with Carecom to handle the issue.
            
            1. •  markus.kalliola will contact Carecom to request the xls file
            2. Access error to the TS from Austria? Did they succeed? No update yet
      3. suggestion Suggestion to MS to make a back-up, or to ask CONET to make a complete back-up => We will ask CONET first
         
         
9. Next meetings bi-weekly meeting: 18 Apr 2016