The ICNP BaTFrom Translation Tool To Translation Web Service

Ulrich Schraderhttp://info.ulrich-schrader.de

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

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

Select version

Select language

1

Select language

2

Language 1

Language 2

Multilingual/Multiversion

A multilingual dictionary of nursing concepts

Ulrich Schrader, FH Frankfurt am Main – University of Applied Sciences

Integrated Languages

• German

• Norwegian

• Cantonese

• French

• Polish

• Slovenian (ICNP Beta)

• Italian (ICNP Beta)

Experiences leading to this talk• Existing translations come in all kinds of formats:

– MS Word– MS Excel– Text files (CSV)

• Import into the database– Manual– Time comsuming– Error prone

• Challenging if different translations have to be integrated into information systems

Uses of a translation service1st scenario

• Multilingual countries– eg. Switzerland (French, German, Italian,

and Rhaeto-Romanic)

• Multilingual nursing workforce– globally recruited

• Goal: Multilingual nursing documentation

Properties of 1st scenario

• All nursing concepts of the specific domain

• Target languages are known

Uses of a translation service2nd 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

Properties of 2nd scenario

• Only some nursing concepts of the specific domain need to be translated

• Languages are unknown beforehand

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.

Possible Solution

• Each system in each institution maintains all translation tables to all available languages

• Challenges– Version changes of the ICNP– Intermediate revisions of each translation

(eg. Correction of typos, errors)– New versions have to be imported

(manually?)

Consequence:Constant update is necessary

TranslationServer

ProposedSolution

Code, version,target language

Concept intarget language

Service-oriented architecture (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)

PrototypeProof of concept• XML-RPC (modified library)

– 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

To do

• Authentication/Authorization

• Encryption?

• Evaluate other protocols– XML-RPC– Simple object access protocol (SOAP)

WS-Security

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

Ulrich Schrader, FH Frankfurt am Main – University of Applied Sciences

Further information:www.ulrich-schrader.de

slideshare.com

Thank you foryour attention

Photo by Stephen Downes