20160226 - Meeting minutes, Friday February 26th 2016 - Terminology Server CTS2

Owned by michele.foucart
Last updated: Mar 03, 2016
3 min read

 

Estimated: 11:00 to 13:00 CET.

Performed: 11:05 to 12:15  CET.

Agenda

  1. Housekeeping
  2. Agree on agenda/working method

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.
------------------------------------------------------------------------------------------------

Giorgio Cangioli

Marco Bernardini

Robert Muetzner

Marta Terron Cuadrado

Peter Haas

michele.foucart

Support documents:

See the 2 documents attached in e-mail sent on 18/02/16 "epSOS CTS2 based specifications":

  • WP3A_epSOS_EED_TSAMSync-CFP_v0 07
  • WP3A_epSOS_EED_TSAMSync-CIP_v0 05 (2)

Meeting Notes:

  1. Housekeeping
  2. Objective of the meeting:
    1. Migration path to onboard the value set... in order to allow the NCP to work
    2. Amongst the pre-requisites:
      1. TS CTS2
      2. OpenNCP CTS2
      3. ...
  3. TS fullfilment of CTS2 from OpenNCP perspective
    1. Possible approaches:
      1. list the functionalities that we need (service translation etc.
        1. Peter is mentioning an xls listing the functionalities we need
        2. Highlights in HL7 specs: Mapping the functionalities in HL7 specs and technical binding with OMG services
      2. Proceed incrementally, see following steps, from the functional point of view (reaching something "working" as today)
        1. From API point of view: recreate the current situation in order to allow the NCP to work TS independant (without Carecom)
          1. Instead of TS Sync => use standard ops
          2. To be sure that we reach the working state (from the functional point of view) without investing in new APIs...
        2. Users part - which is another topic
      3. Of course the end point of the server needs to be changed.
      4. Agreement on the incremental approach
  4. Specs of TSAM
    1. Giorgio Cangioli proposes to find the specs and reference implementation of the client part.
      1. From that FH Dortmund to assess if ok or directly go to step 1?
      2. we can check if it conforms to the info of the TS...
        1. identifyer of the concept, identifyer of the term, the status of the concept, language... info that need to be handled, ref to the code system, id of the value set...
        2. As soon as we have the specific rule, we can discuss on that
      3. Based on the costs of implementation we can decide if we can skip the step or not
      1. In // we can start to investigate the following steps
    3. Peter Haas: If we have a migration project, first question is if we have a big schema mismatch.
    4. Align implementation strategy based on the best implementation choice/approach (FHD)
    5. Is there documentation of the services? (Healthterm) - Giorgio Cangioliwill get in touch with Peter to highlight those definitions.
    6. Peter Haas: Over 40 service methods...H2 retrieve an concept and translation
    7. Where can we find API specs of FHDT? http://www.wiki.mi.fh-dortmund.de/cts2/index.php?title=Terminologieserver_-_Webservice_Dokumentation
      1. Example: http://www.wiki.mi.fh-dortmund.de/cts2/index.php?title=Terminologieserver_-_Search_-_ListCodeSystemConcepts
      2. http://193.25.22.69:8080/TermServer/Search?wsdl
      3. Critical point is to be able to handle those messages
    8. Giorgio Cangioli:
      1. We need to investigate: they changed the synchro services a bit to allow an incremental synchronization, using solution which is a bit complex. Allow the NCP to make the complete resync. Might be more complex if we try to download more than one language...Code system is in leading language (ENg) in the service call you can ask specific translation. Then get the translation and original language...
      2. Need to investigate if we can obtain the information through the value-set content or other
    9. Giorgio Cangioli: proposes to retrieve original TSAM Sync, then see how to map with existing services, then in // with OMG services that we want to use.
  1. Marco Bernardini has also started the GAP analysis of the datamodel.
  2. How to phase the management of the different code systems and H2 approach them?
    1. e.g. EDQM have different properties, assets to be considered... How 2 represent terms, H2 keep in touch with the people working...frequent updates of the terms...
    2. Procedural aspects to be handled, technical aspects, relationship...=> We should start to list those aspects. Orga aspects, administration of semantic can be discussed in //. Giorgio Cangioli proposes to create a page listing the diffrent topics to be handled and start with that in //.
  3. Next steps
    1. For the moment 4 main activities are identified:
      1. Work from the specs, focussing on recreating the current situation => Giorgio Cangioli, Former user (Deleted), Peter Haas
      2. TS on our current Infrastructure => Marco Bernardini
      3. GAP data model => Marco Bernardini
      4. Management of the different code systems, organizational and technical aspects => Giorgio Cangioli will start the page, Marta Terron Cuadrado participation
        1. start a meeting as soon as we are a bit more mature on the topic
    2. Working space OpenNCP task force Terminology server can be used (need to be logged in to see the page: /wiki/spaces/ncp/pages/72417309
  4. Next meeting: Terminology task force meeting on 1pm CET