People:

Annika Hansen, Arnaud Gaudinat, Gorgio Cangioli, Gegerly Héja, Marcello Melgara, Marcelo Fonseca, Steen Manniche

Objectives: 

Goals are to give an overview of the requirements of the Semantic miniproject (aka TM, TSAM and TSAM-SYNC) of OpenNCP to be able to support 3 of the use cases described in D1.4.3 (EED SERVICES including specifications for all services) which are PAC (Patient Access), MRO (Medical Related Overview) and HCER (Health Care Encounter Report).

List of relevant documents for the topic:

WHERE are modifications needed?

• PAC :
  • Semantic services: yes ( in TSAM-SYNC , TSAM, TM)
  • Semantic signifiers: no 

• HCER :
  • Semantic services: no (TSAM-SYNC), yes in (TM ,TSAM)
  • Semantic signifiers: yes

• MRO :
  • Semantic services: no (TSAM – SYNC), yes in (TM ,TSAM)
  • Semantic signifiers: yes

Notes from Marcello  about MRO and HCER: 

• Which are the dataset for theses use cases
• Minimum changing of XML files (Schematron)
• => should be handle by POSAM (TODO: ask to Milada)

HOW will it work:

• PAC Services:
  • Translation for PAC will be handle by country A
  • Translation for PAC will be available in eCRTS
  • NCPA have to load all eligible translations from eCRTS  into one LTR (it was decided to have only one LTR)
    • CARECOM has to flag eligible downloadable translations (from a list of eligible translation) in HealthTerm
      • A translation is eligible for PAC:  
        • If all valueset translated
        • If respect procedure of administration and review
        • If no business constraint exist for this country
      • Eligible languages should be:
        • fr  (French)
        • it (Italian)
        • de (from Austria)
        • sp (Spanish)
        • sk (Slovakian)
        • others to complete
    • TSAM-SYNC will Download only new data available
      • Incremental SYNC
      • With several translations the SYNC could be longer (to be tested)
    • Download only translations available for country A, handle by eCRTS (ie Snomed translation for Germany) ( there is a lice)

• • • How to know if a new version of translation for country B is available:
      • When any change in the MTC is introduced by a PN, the PN has to start the Change Management process, in accordance to the procedure defined by the CAG (only procedure, where maintain set of lang
    • Only one translation per language (ie: fr-FR for French and not fr-CH)
  • What can be display (list of languages) for user interface (to be discussed)
    • static html
    • from central service
    • portal B

HOW to do ( to discuss Friday 8th):

-       PAC services:

• TSAM-SYNC :
  • LTR already able to handle several designations for one CODE_SYSTEM_CONCEPT in DESIGNATION table
  • add a configuration option (PAC_option) to support  PAC

• TM, TSAM:
  • In TM, indicates the right parameter (targetLanguageCode) in translate(epSOSCDA, targetLanguageCode) instead of translationLanguage in property file
    • TSAM: This will call in TSAM: getDesignationByEpSOSConcept()) in DESIGNATION table of LTR

TO DO:

-       Continue the discussion Friday 8^th with Milada

-       Identify the tasks for dev team