Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device. Atlassian cookies and tracking notice, (opens new window)
20160607 - Meeting minutes, Tuesday June 7th - Task force Terminology Server
20160607 - Meeting minutes, Tuesday June 7th - Task force Terminology Server
Jun 07, 2016
Estimated: 14:00 to 15:00 CET.
Performed: 14:00 to 14:45 CET
Agenda
Outcome of the study
Feedback user testing
Executive summary
eHOMB decision
Next steps
Next meetings
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. ------------------------------------------------------------------------------------------------
Did not evaluate the capability of the system of handing MVC 2.0
Problems with the import of special characters
OID
Capability to update code systems - sometimes it is useful to change a code system without changing code system version
Administration capability - see if this feature could be allowed for other kinds of roles
Some actions could be performed by several kinds of resources
Open questions of how to take advantage of code system import
Translations: same kind of problems as with Carecom for translations in bulgarian and in spanish
Is it possible to assign a translation not to a specific language but for a specific language use in the country (e.g. US EN, CA EN, US EN)
Use of language ISO
Assign designation
Mapping
Giorgio was not able to complete the process; it has been tested by Marta and Marco
Exporting value set
Import of translations
No problem with the characters
Same question as for other functionalities - authorization/role
Would be good to have some status handled to support the different translations phases: reviewed, approved...
Audit log...
In epSOS there were 2 different scopes: preparation test environment and eHealth integration environment
We need to figure out how this would be handled
User context
Critical functionalities
Mapping import
Profiling, granting, auditing of the actions and minimum workflow management
Differentiate official release + what is part of the extension per country
Preparation test environment and eHealth integration environment
Executive summary
eHOMB decision: Host the terminology server at EC and further develop the functionalities that are not yet covered, especially with regards to user/profile and auditing of actions...
Next steps: List the requirements (based on input from the tests) and prioritize them using Moscow method.