Page Comparison

...

Estimated: 14:00 to 15:00 CET.

Performed:   14:05 to 16h20 CET.

Agenda

1. Welcoming and introduction (Markus)
   1. CEF building block eDelivery
   2. eHOMB decision
2. Way of working (Markus)
3. Background DIGIT impact analysis (Adrien)
   
   1. Roadmap
4. Status from DIGIT (Adrien)
   
   1. Change requests for the SMP
   2. Business Analysis
5. Status of the integration of the SMP with OpenNCP (PT?)

6. Next steps (Adrien)

7. 1. Specifications for open ncp, task force -> technical committee -> DG Sante

   2. Implementation for openncp

8. Milestones (Adrien)
   1. Connectathon
9. AOB
   1. Next meeting

...

• Adrien FERIAL (DIGIT)
• S
• michele.foucart
• markus.kalliola
• Joao Cunha
• @uwe Uwe Roth
• Yves ADAM (EC DIGIT)
• YacoubouY

Support documents:

...

1. Welcoming and introduction (Markus)
   1. Roundtable of the presentations.
   2. CEF building block eDelivery.
      eHealth DSI is part of CEF, and following CEF use of common building block, robustness and cost efficiency.
   3. eHOMB decision Decision was taken to start this the SML/SMP task force Adrien will present following the impact assessment made by DIGIT, based on which eHOMB made its decisionconducted by DIGIT to use SMP/SML in OpenNCP.
      
      
2. Way of working (Markus)

   1.  Task force meeting frequency

      1. We have only The task force is only composed of people working on the topic, share info..this topic to have an area were this specific topic is discussed, information is shared etc.
      2. Meeting every 2 week? Ok to start like this and schedule additional meeting meetings will be scheduled if necessary
   2. Meeting Task force meetings will be chaired by Adrien
   3. Taking minutes, meeting organization => Meeting organization and meeting minutes will be done by Michele
   4. Tasks will be published in OpenNCP JIRA, as the usual way of working with the OpenNCP Community
      
      
3. Background DIGIT impact analysis (Adrien)
   
   1. Sharing Adrien is sharing the impact assessment document => Please see the support document
   2. Collaborated with the OpenNCP Community (Massi, Joao and Rui) for this analysisAll PN use the config  server.
   3. Presentation of the migration plan in 3 steps:
      1. Baseline architecture:
      2. Deployment of a centralized SMP - to be completed
         
         1. x
         2. x
      3. All participating nations (PN) use the configuration server
      4. Centralized SMP architecture: All PNs use the centralized SMP
      5. Centralized + distributed architecture: Some PNs host a SMP, other PNs keep using the centralised SMP
   4. Joao Cunha: This document is alligned aligned with the document writen written in the eSENS scope
   5. The change requests are presented.
      
      1. Some changes request change in SMP specsspecifications. A consultation has been launched.
      2. Changes in the OpenNCP implementation specifications. It is the role of this task force to identify the changes in specsspecifications
   6. Roadmap (see support document p42): the target is September 2016 to have a centralized SMP.
      
      1. Tests performed Expandathon December 2016
      2. Definition of the interfaces PUT interface will be documented
      3. Developments
      4. Start the integration of the developments with OpenNCP
      5. Testing
      Deploymentin January, February
      6. In parallel, review of SMP docs, openNCP adaptations... + development related to the GET interface of the SMP until end of March
      7. End developments end of April, which should be then available in Acceptance
      8. Development documentation March , April, May
      9. Testing in test, acceptance
      10. Deployment production September
      11. Joao Cunha: does it mean that the client Jar file will be changed?
          1. Adrien FERIAL: Refers to the authentication need. Allow Need to allow each NCP to authenticate and need to authenticate  => will produce a document about this interface, to be shared with the OpenNCP Community
          2. Difference in hosting (from the university university Pireus to DIGIT). Objective is hosting current SMP hosted at DIGIT end of April
      12. End developments end of April, which should be then available in Acceptance
      OpenNCP implementation,
   7. Assignment of the tasks:
      
      1. The development of the interface = for the OpenNCP implementation is the work of this task force. Roles
         
         1. The roles described in the doc are DIGIT/SANTE
         in the document
         1. because document between DIGIT and SANTE. But the idea is to work on this implementation with eSENSE and the OpenNCP Community...
         2. Question of the extension of eSENS after March?Assignment of the tasks:
         1. What would be the resources from eSENS to work on the get interface implementation? Available resources? This question should be asked to Licinio. Joao Cunha will raise the question to Licinio.
         2. eSENSE could notify the task force about the available resources.
      Explanation of the impact on the logical components of the NCP
      1. Change of the workflow
4. Status from DIGIT (Adrien)
   
   1. Change requests for the SMP
      1. Identified in the Digit impact analysis
         1. Available at Open consultation 
         2. Will be submitted to OASIS after consultation 
   2. Business Analysis
      1. "Contract" between OpenNCP and SMP
      2. Work on progress, will be submitted to the task force next week and can be discussed in the next task force meeting
         1. First draft will be about the format not the content
         2. After discussion in the task force focus to the content 
            
            
5. Status of the integration of the SMP with OpenNCP
   1. Joao Cunha: First phase was about submitting files to SMP
      1. TSL files were transformed into SMP files
      2. After transformation files were uploaded to SMP
      3. Development of new functionalities to TSL Editor
      4. SMP server were hosted in the Pireus University
      5. Portugal tested the upload in Expandathon and IHE team validated the test in Gazelle
      6. Test were implemented using a Jar file from DIGIT (from Peppol)
   2. All developments are submitted to Bitbucket and they are available for this task force 
      
      

6. Next steps (Adrien)

   1. Specifications for open ncp, task force -> technical committee -> DG Sante

      1. Joao Cunha mentioned that a change request has already been made and it is available in IHE OpenNCP Jira
      2. Read the impact assessment
      3. Which technical documents need to be modified

   2. Implementation for openncp

      1. Initial brainstorming done by Massi, Joao and Uwe. Problem with caching mechanism. Where the cache should be implemented in OpenNCP architecture. Workflow manager was suggested, but it will not be available for these developments.
      2. Cache need to be solved before starting developments. It need to be done so that when the workflow manager is implemented the architecture doesn't need to be refactored.
      3. Assertions need to be discussed as well. 
7. Milestones (Adrien)
   1. A possible milestone for Connectathon will be discussed in the next meeting
      
      
8. AOB
   1. Next meeting 03 Feb 2016 

...