House Keeping

• Minutes approved.
• Matters rising and action items from previous meetings.
• Agree on today agenda.
  
  

OpenNCP Roadmap

• Next release 2.4.2.
• Releases plan and cycle.
• Version for the Bootcamp (January 2017).
• Content of the release until the GoLive in 2018.

Related Wiki page: https://openncp.atlassian.net/wiki/x/GYDDAw

S presents a draft agenda of the releases plan with the main functionalities:

2.4.2 October 2016 after the CEF Digital migration (minor bugfix and components re organization)

2.5.0 December 2016 (SMP PEPPOL mock services, CTS2 Synchronization Services)

2.6.0 March 2017 (SMP OASIS, Workfow Manager, CTS2 Terminology Services)

3.0.0-RC Operation Ready end of July 2017 (National Connector, Namespace re-branding)

Stéphane Spahni highlight the fact that July 2017 is a little bit late for the release because of the summer break and ask if it's possible to do the release earlier in June.

Heiko Zimmermann asks which version of OpenNCP will be used during the Bootcamp session → according the planning: 2.5.0

• Review of the Building Blocks integration. Licinio Kustra Mano and S
• Review of the releases content (2.4.2, 2.5.0, 2.6.0, 3.0.0-RC). Licinio Kustra Mano and S
• The related wiki page has to be updated according the current status of the OpenNCP software. Licinio Kustra Mano and S
• Provide and validate the final date of the release 3.0.0-RC (Operation Ready) Licinio Kustra Mano

OpenNCP Technical Discussion

• Technical roadmap validation of sustainable frameworks, tools etc.
  
  

• SMP/SML integration

  • Status

  • SMP Editor
    
    

• eID implementation:
  
  

• Terminology Services:
  
  

• Evidence Emitter storage:
  
  
• WorkflowManager and National Connector

Related Wiki page: https://openncp.atlassian.net/wiki/x/C4CBBg

Technical Committee members fully agree to the fact that we must update to JDK8 for sustainability, security and performance reasons.

Update of the main framework of the OpenNCP reference implementation should be also realized (Spring, Hibernate etc.). This operation could be mandatory because of the JDK8 use.

The TC also highlights the risk of too many impacts on each components because of the interconnection of the products etc. Only the MUST operation have to be performed in priority. More details will be added to the dedicated wiki page.

In an infrastructure point of view, the decision to continue with Apache Tomcat and MySQL database for the reference implementation, and without using Api strongly linked with the application server or database vendor.

Kostas Karkaletsis explains that the goal is to keep the implementation as much independent as possible. Support of others products will be a nice to have.

We also agree about the Logging strategy which should be efficient.

++++++++++++++

SMP/SML:

++++++++++++++

Terminology Services:

S asks some technical details about the top down synchronization between the central terminology repository and the local one according the CTS2 specification.

Heiko Zimmermann proposes to find experts with knowledge about the full specification and technical experience with it. And mentioned as an example that in Trillium Bridge project, the PHAST terminology server and perhaps some interesting information to find from this experience. Perhaps, Giorgio Cangioli would also be able to share his experience in this domain.

++++++++++++++

eID (Patient identification):

Marcello Melgara explains different level of eID and the importance of piloting in eSens, and also the level 4 and 5 which are relevant with the eIDAS regulation.

++++++++++++++

Evidence Emitter storage, Workflow Manager and National Connector:

The different change proposals have to be relaunch and proposed to the validation structure (governance) and then the implementation have to be launched, this is a really huge challenge.

• TRC-STS component will be migrated to Apache CXF as a pilot and in order to provide a feedback for the others WSDL components . S

• Implementation of the SMP Editor Dimiter Petrov

• Check the status of the different CP and relaunch the process Christophe.DUMONT

Wrap Up and Next Steps

• Next Meetings (calendar subscription)
• 06 Oct 2016 11:00 CET
• AOB

AOB:

Heiko Zimmermann asks about the Bootcamp and the mandatory LTRDB in order to proceed the full installation and configuration of the node for the OpenNCP newcomers.

• Validate and synchronize the deadline for the terminology services with the vital functionnalities. Licinio Kustra Mano and S
• Preparing some CDA dataset for test.