Multiple translators

Thomas Beale thomas.beale at oceaninformatics.com
Tue Mar 17 06:52:37 EDT 2015


Right - exactly. Ideally, we need people who are developing archetypes 
and think there are limitations to say what they are. It isn't that hard 
to add more comprehensive meta-data to an archetype for translations, 
other_contributors etc. Of course, we don't want to go overboard - using 
links / addresses to other resources is good too.

Once changes are agreed, they can be put in ADL 2, and the ADL Workbench 
and other tools can fairly easily upgrade the existing archetypes into 
new structures.

- thomas

On 17/03/2015 10:32, Sebastian Garde wrote:
>
>
> On 17.03.2015 11:25, Thomas Beale wrote:
>> On 17/03/2015 10:17, Bakke, Silje Ljosland wrote:
>>>
>>> For now, the other_details attribute within TRANSLATION_DETAILS 
>>> should do the trick. The main issue is to keep the different 
>>> translators separated, which this seems to do:
>>>
>>> other_details =<
>>>
>>> ["secondary_translators"] = <"Ian McNicoll, freshEHR, UK", 
>>> "Sebastian Garde, Ocean Informatics, DE">
>>>
>>> >
>>>
>>> The main issue is probably getting support for this in the tooling 
>>> (ie Archetype Editor and the CKM)?
>>>
>>
>> If I add the equivalent of this to ADL/AOM 2, will it be enough for 
>> the future?
>>
> There is also an older related issue on the specs tracker
> https://openehr.atlassian.net/browse/SPECPR-24
> This issue highlights some potential problems as well, but doesn't 
> have a clear solution yet.
>
> I believe it should be considered at the same time.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openehr.org/pipermail/openehr-clinical_lists.openehr.org/attachments/20150317/0a0092b0/attachment-0002.html>


More information about the openEHR-clinical mailing list