Page Comparison

...

1. Housekeeping
   
   
2. Status
   1. Gap analysis FH Dortmund Terminology Server
      1. Uses cases -
         
         1. importing data. Import of a code system (ICD and ATC) from the CLAMs'file on a local instance
            1. issue on import of value set
               •  Marco Bernardini will see with Robert Muetzner
            2. Giorgio Cangioli: value set as explicit list? Or define value set through rules? (e.g. provide me all children of that code concept) - Peter Haas : Can have it as a response but not as a rule based value-set
               
               1. Synchro LTR with the content of TS, what is need to have the expansion of concepts
               2. Peter Haas: virtual rule based is interesting for the future but not implemented yet.
            3. Giorgio Cangioli: Value set is derived from a specific code system version? Peter Haas: yes implemented. Not only for 1 code system but also a combination of code systems
         2. Other gap/issue noticed? No
      2. Data
         1. Looking on data in DB
         2. Looking further mapping between LTR data base & what we need to have with FHD
            •  Marco Bernardini will try to integrate the info published by Giorgio on CTS2 mapping
              1. Giorgio Cangioli: precizes that this is a working document
   2. Synchronization FH with OpenNCP in compliance with CTS2
      1. Giorgio Cangioli shared epSOS documentation on TSAM composant
         1. Did not find the detailed technical specs of the API. Giorgio Cangioli
            •  Giorgio Cangioli is investigating for the document
            1. Doc as starting point to undersand how it works: How the components in NCP are organized and work : TSAM, TSAM-sync, LTR...
               1. Missing part is the detailed specs of the API => cf. previous point
            2. Peter Haas: How compliant is the documentation? Giorgio Cangioli snswers that it SHOULD be compliant to. What is missing is the actual call done to retrieve the info from the central server. Less details on the synchronization part => See previous points
            3. Components impacted by the implementation of a new TS:
               1. In current phase: TSAM-sync. no impact on the other components in a first phase ( if we want to replicate current features of current NCP).
               2. If we would like to include additional capabilities e.g. possib of having value sets derivefd from different code systems - update LTR structure + update oder components.
   3. Management of the different code systems
      1. Organizational licences and agreement => out of scope => a sub-group on terminology of MS experts has been set up during the last eHMSEG, and will make a proposal for June
      2. Technical part: support different formats, type of information etc; For the migration and for the future arrangements => in scope
         1. file format
         2. How to import
         3. what is the update mechanism (e.g; 2 release of code systems; others might have continuous updates...)
         4. etc.
         •  Giorgio Cangioli, Marta Terron Cuadrado will start to enrich the dedicated page with their respective knowledge. Everyone is free to contribute with his/her knowledge for each code.
           
           
3. Next meetings: 21 Mar 2016 12:00 am CET

...