What must it be implemented

1. Create and send a list of eligible languages to CARECOM for setting eCRTS (see note 1) 
2. Create a file of eligible languages to be used in the NCP end user interface
   1. I propose to change the end user interface with languages available in LTR  
      1. if yes, implement or find a get_language_list function 
   2. Or just a file (????)
3. Check multi-translation
   1. when 1 is ready do synchronisation and check availability of translation in LTR 
4. Add unit-tests for multi-translation in TM  (TSAM?) 
   1. (i.e. In TM, indicates the right parameter (targetLanguageCode) in translate(epSOSCDA, targetLanguageCode) instead of translationLanguage in property file)
5. Present the list of eligible languages on NCP end user interface
   1. I propose to change the end user interface with languages available in LTR  
      1. if yes, implement or find a get_language_list function 
   2. Or just a file (????)
   3. Or country B
    
   
   

Functional description

• • 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) 

...