Re: Should ATTESTATION.reason datatype really be DV_TEXT or ratherDV_COD
The latter...you are not forced to have every entry in the languahge of
the composition.
Sam
Sam Heard via Blackberry
CEO
Ocean Informatics
+61417838808
-----Original Message-----
From: Peter Gummer <peter.gummer@oceaninformatics.com>
Date: Fri, 5 Mar 2010 11:19:24
To: For openEHR technical discussions<openehr-technical@chime.ucl.ac.uk>
Subject: Re: Should ATTESTATION.reason datatype really be DV_TEXT or
rather
DV_CODED_TEXT (or perhaps CODE_PHRASE)?
Thomas Beale wrote:
>>>> Are end users really supposed to see the DV_TEXT.value
>>>> of those? ...
>>> ... we historically decided that it was always better
>>> to have the original text of any coded element, in the original
>>> language.
>> When you say "in the original language", do you mean the original
>> language of the archetype, or do you mean the original language that
>> the user saw on the screen when the data was committed?
>
> it is the latter - the archetype's original language is irrelevant -
> we are only interested in the locale language of the committing
> user, which could easily be different.
That makes sense.
On committing the contribution, is there validation of the
DV_CODED_TEXT.value to ensure that it is the same text as the value
defined for the committing user's language, for that code in that
terminology?
- Peter Gummer
_______________________________________________
openEHR-technical mailing list
openEHR-technical@openehr.org
http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical
_______________________________________________
openEHR-technical mailing list
openEHR-technical@openehr.org
http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical