20160120 - Meeting minutes, Wednesday January 20th 2016 - Task force Terminology Server: Kick off

Owned by michele.foucart
Last updated: Jan 20, 2016
4 min read

 

Estimated: 14:00 to 15:00 CET.

Performed: 14:05 to 15:05 CET.

Agenda

 

  1. Welcoming and introduction
  2. Presentation of epSOS/EXPAND ( Marcello or Michele)
  3. Presentation of eHealth DSI (Michele)
  4. Terminology server
    1. First study (Michele)
    2. Second study (Natasha)
    3. eHOMB decision (Michele)
  5. Way of working (Natasha)
  6. Task force tasks for Spring, introduction to what needs to be done (Natasha)
  7. Scheduling next meeting

Location

  • AdobeConnect:

http://ec-wacs.adobeconnect.com/openncp/
Room Passcode:  markus.kalliola or michele.foucart
------------------------------------------------------------------------------------------------
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.
------------------------------------------------------------------------------------------------

Support documents:


Meeting Notes:

  1. Welcoming and introduction
    Round table with the presentation of the different participants.

  2. Presentation of epSOS/EXPAND
    Please see PDF support document.

  3. Presentation of eHealth DSI
    Please see support document "eHealth DSI".
    1. eHealth DSI governance
    2. New documents from eHealth Network: Organizational Framework for NCPeH, Governance for eHealth DSI
    3. Core and Generic, what are the roles of EC and what is the role of MS

  4. Terminology server
    Please see support document "eHealth DSI".
    1. Introduction - Please see the support document "Preparatory document for the kick-off meeting of the Task Force Terminology Server –  The epSOS MVC / MTC, and the eCRTS (epSOS Central Reference Terminology Server)"
      1. Marcello Melgara says that the initial xls file uploaded in the terminology server was just a working document, an informal representation. The approval/validation of MVC are done on the terminology server, the MVC can then be exported from the terminology server. So the only official/valid versions of the MVC are the ones exported for the terminology server.
      2. Importance of the requirement "multi-language management" since we have 24 official EU languages. But FH Dortmund TS is a generic solution so multilanguage is not an issue.
    2. First study
      1. Market analysis of the terminology servers available on the market (open source and commercial solutions were considered).
      2. Decision to analyse further the solution developed by FH Dortmund which is open source and CTS2 compliant
    3. Second study
      1. Concluded that FH Dortmund is mature and fits the requirements of DG SANTE eHealth DSI demands.
      2. But it is not a ready product, adaptations are needed
    4. eHOMB decision
      1. Gave the approval to start a task force on terminology server to assess in detail what needs to be done.
      2. Activities of the task force will be amongst others to
        1. Perform a GAP analysis highlighting the changes that have to me implemented to the terminology server.
        2. Upload the MVC (Master Value sets Catalogue) from 2 different MS and introduce it in the server. We’ve asked 2 experts from the MS
        3. Testing stability etc..
      3. Deadline for the analysis: May 2016
      4. Final decision on the choice of terminology server: June 2016, based on the detailed study.
  5. Way of working
    Please see support document "eHealth DSI".
    1. Currently there are apparently two forks of the project, one in Dortmund and one in Austria, are there others?
    2. How should eHealth DSI work with the project, do we fork or try to manage with sources in a common place? What the pros/cons
      1. An organization/governance have to be put in place
        1. FH Dortmund would be kept as master
        2. The idea would be to build a terminology server steering team led by Peter and Robert
        3. Each modification of the terminology server should be made via JIRA & Github, then decision to be made on who implement and the push the code to the Master
        4. Need for test/development instances of the server to work on a secure way, this is becoming urgent
        5. There are also some design decisions to be taken
      2. Impact analysis when we make change to ensure we're not disturbing the organizations which use the terminology server for their operations
    3. EC plan would be to keep the source code open and available even if we fork
    4. How to manage fixes, bugs, ticketing, releases etc? Whose Jira to use etc.
    5. Miscellaneous:
      1. Most of the topics discussed need further reflection. Natasha Carl will prepare a proposal and send an e-mail to the members of the task force to collect the reactions. The outcome of this reflexion will be discussed at the next terminology server task force meeting.
      2. It is also important to distinguish the legal, functional and semantic aspects from the technical aspects
      3. Importance to define the goal, the processes (how to define the MVC, how to generate the MTC etc.) - Marcello Melgara has provided a document which can be used as input, but that has to be considered as a working document, not for distribution.
  6. Task force tasks for Spring, introduction to what needs to be done
    Please see support document "eHealth DSI".
    See also "miscellaneous" from previous chapter "way of working".
    A closed collaborative space to share "working" documents would be more than welcome. We plan to migrate the wiki, this requirement will be clearly considered. In the meantime We'll see how we could restrict some parts of the current openNCP wiki, if possible (michele.foucart)

  7. Scheduling next meeting

Next meeting will take place on Monday