This document proposes a solution to the challenges of managing translations of nursing terminology standards like ICNP across multiple languages and versions. It suggests developing a translation web service that institutions could access to lookup terminology translations, rather than each institution maintaining its own translation tables. A prototype was created using XML-RPC that demonstrated translation lookups with average response times of 0.13 seconds, fast enough for real-time translation. The service would help support consistent terminology use across borders and systems.

1. The ICNP BaTFrom Translation Tool To Translation Web Service Ulrich Schraderhttp://info.ulrich-schrader.de

2. Content Briefly: The web-based translation tool used to help with translating the ICNP 2 Scenarios using different translations in practice Challenges posed for information systems Proposal for a solution Experiences with a prototype

3. Ulrich Schrader, FH Frankfurt am Main – University of Applied Sciences ICNP BaTBrowser and Translation-Tool Support all three phases of a collaborative translation effort Translation phase Evaluation phase Finalizing and export Multilingual Support several languages Multi-version Support the concurrent translation of several versions of the ICNP Automate the migration of already existing translations of a prior version of the ICNP to the next version Support multiple translation of a concept Preferred term, synonyms Support the communication, cooperation, and coordination between teams of translators and evaluators of a specific language

4. Multilingual/Multiversion Select language 1 Select language 2 Select version Language 2 Language 1

5. A multilingual dictionaryofnursingconcepts

6. Ulrich Schrader, FH Frankfurt am Main – University of Applied Sciences Integrated Languages German Norwegian Cantonese French Polish Slovenian (ICNP Beta) Italian (ICNP Beta)

7. Experiencesleadingtothis talk Existingtranslationscome in all kindsofformats: MS Word MS Excel Text files (CSV) Import intothedatabase Manual Time comsuming Error prone Challengingif different translationshavetobeintegratedintoinformationsystems

8. Usesof a translationservice1st scenario Multilingual countries eg. Switzerland (French, German, Italian, and Rhaeto-Romanic) Multilingual nursing workforce globally recruited Goal: Multilingual nursing documentation

9. Properties of1stscenario All nursing concepts of the specific domain Target languages are known

10. Usesof a translationservice2nd scenario Patient traveling to another country Goal: Nursing documentation should be at least partly readable in another language Coded content can be translated automatically, if translation table for this language available

11. Properties of 2nd scenario Only some nursing concepts of the specific domain need to be translated Languages are unknown beforehand

12. Assumptions Nursing care data are represented as standardized terms sometimes appended with free text. ICNP is used in a computerized system as interface terminology or reference terminology Translation would require looking up the code mapped to the desired translation.

13. Possible Solution Eachsystemin eachinstitutionmaintainsall translationtablesto all availablelanguages Challenges Version changesofthe ICNP Intermediate revisionsofeachtranslation(eg. Correctionoftypos, errors) New versionshavetobeimported (manually?)

14. Consequence:Constant update isnecessary ProposedSolution TranslationServer Code, version,targetlanguage Concept in target language

15. Service-orientedarchitecture (SOA)Translation service Web service based on HTML protocol(No extra ports needed) Accessible over the internet Machine readable (XML based) Independent of operating system Request for All translations of a target language of an ICNP version (scenario 1) A few translation s of a target language of an ICNP version (scenario 2)

16. PrototypeProofofconcept XML-RPC (modifiedlibrary) getLanguages getTranslationByCode getTranslationByText Performance Rented, commercial, virtual server PC client application (PHP script) Average response 0.13 seconds (getTranslationByCode) Almost enough for translation on the fly

17. To do Authentication/Authorization Encryption? Evaluate other protocols XML-RPC Simple object access protocol (SOAP)WS-Security

18. Conclusions Challenges not restricted to ICNP translations Translations do change frequently over time It does not make sense for each institution to maintain their own translation tables A central translation server using SOA could simplify the maintenance task of the translation tables

19. Ulrich Schrader, FH Frankfurt am Main – University of Applied Sciences Furtherinformation:www.ulrich-schrader.deslideshare.com Thankyouforyourattention Photo by Stephen Downes