Multiple translators

Sebastian Garde sebastian.garde at oceaninformatics.com
Fri Mar 13 13:04:23 EDT 2015


Hi Ian,

Yes, I agree that that is a better place - but I think you will find 
that while this is in the rm, tooling support for 
TRANSLATION_DETAILS/other_details it is rather poor at present.

In CKM, we could add something like this to the translation pages, which 
would make it easy for the (main) translator to add this.

Sebastian




On 13.03.2015 16:38, Ian McNicoll wrote:
> Hi Silje,
>
> The current AOM has an other_details attribute inside 
> TRANSLATION_DETAILS which would allow something like
>
> other_details =<
>     ["secondary_translators"] = <"Ian McNicoll, freshEHR, UK", 
> "Sebastian Garde, Ocean Informatics, DE">
>  >
>
> would that be enough, or do we need accreditation details for each 
> translator? That would need a change to the Archetype Object model - 
> easy to do but not until we get ADL 2.0 tooling.
>
>
> Ian
>
>
>
>
>
> Dr Ian McNicoll
> mobile +44 (0)775 209 7859
> office +44 (0)1536 414994
> skype: ianmcnicoll
> email: ian at freshehr.com <mailto:ian at freshehr.com>
> twitter: @ianmcnicoll
>
> Director, freshEHR Clinical Informatics
> Director, openEHR Foundation
> Director, HANDIHealth CIC
> Hon. Senior Research Associate, CHIME, UCL
>
> On 13 March 2015 at 15:06, Bakke, Silje Ljosland 
> <silje.ljosland.bakke at helse-bergen.no 
> <mailto:silje.ljosland.bakke at helse-bergen.no>> wrote:
>
>     Hi,
>
>     At the Norwegian CKM http://arketyper.no, we’ve been doing quite
>     extensive translation of international (English language)
>     archetypes into Norwegian. During this process, we’re finding more
>     and more translation isn’t a one-person job, but usually there’s a
>     primary translator and one or more secondary translators. As of
>     now there seems to be only one field in which to put translator
>     information, so to attribute more than one person as the archetype
>     translator, we need to put more than one name, organisation, etc
>     into the same fields. This sort of works, but it’s not exactly
>     elegant. Is there a better way to do this, either right now or in
>     the works?
>
>     Kind regards,
>     *Silje Ljosland Bakke*
>
>     **
>
>     Special Adviser, RN
>
>     R&D dept, E-health section, Bergen Hospital Trust
>
>     **
>
>     Coordinator, National Editorial Board for Archetypes, National ICT
>     Norway
>
>     Tel. +47 40203298 <tel:%2B47%2040203298>
>
>     Web: http://arketyper.no <http://arketyper.no/>/ Twitter:
>     @arketyper_no <https://twitter.com/arketyper_no>
>
>
>     _______________________________________________
>     openEHR-clinical mailing list
>     openEHR-clinical at lists.openehr.org
>     <mailto:openEHR-clinical at lists.openehr.org>
>     http://lists.openehr.org/mailman/listinfo/openehr-clinical_lists.openehr.org
>
>
>
>
> _______________________________________________
> openEHR-clinical mailing list
> openEHR-clinical at lists.openehr.org
> http://lists.openehr.org/mailman/listinfo/openehr-clinical_lists.openehr.org

-- 
*Dr. Sebastian Garde*
/Dr. sc. hum., Dipl.-Inform. Med, FACHI/
Ocean Informatics

Skype: gardeseb


---
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
http://www.avast.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openehr.org/pipermail/openehr-clinical_lists.openehr.org/attachments/20150313/d9f82bdf/attachment-0002.html>


More information about the openEHR-clinical mailing list