Hoylen Sue wrote:
It is not necessary for openEHR to specify the encoding
format (UTF-8, UTF-16, etc).
Since openEHR does not dictate an implementation or
transport format, it does not need to -- and should not --
specify the character encoding format.
Just saying text will be using the Unicode
It is not necessary for openEHR to specify the encoding
format (UTF-8, UTF-16, etc).
Since openEHR does not dictate an implementation or
transport format, it does not need to -- and should not --
specify the character encoding format.
Just saying text will be using the Unicode character set
I agree. :-)
GF
-- private --
Gerard Freriks, arts
Huigsloterdijk 378
2158 LR Buitenkaag
The Netherlands
+31 252 544896
+31 654 792800
On 19 Mar 2004, at 15:36, Thomas Beale wrote:
ENTRY class has
- a mandatory language attribute
- a mandatory character encoding attribute (says which
On Thu, 2004-03-18 at 00:51, gfrer wrote:
Hi,
Anamnesis in psychiatry:
italicAnd then the disturbed patient said: Merdre. [Translation:
shit]
/italic
Family history:
italicMy father was diagnosed as suffering from: Engelse ziekte
[Translation: Rickets dissease]
Tim Churches wrote:
Yes, I thought of examples which were similar to these. And it is not
just a matter of the recording health professional not knowing what
Engelse ziekte means, and thus having to record to verbatim and
untranslated - many diagnoses have no equivalent in other
Hi,
The examples I provided were those that I could think of.
The real question to be asked is:
Why would we want to record the 'language' of a text fragment?
The only correct answer will be:
Because of computational reasons.
In the light of this there is no real use case for this attribute in
gfrer wrote:
Hi,
The examples I provided were those that I could think of.
The real question to be asked is:
Why would we want to record the 'language' of a text fragment?
The only correct answer will be:
Because of computational reasons.
In the light of this there is no real use case
Getting in late on comments but.
On Sat, 2004-03-06 at 14:57, Thomas Beale wrote:
some higher level class - e.g. COMPOSITION, since almost all the time it
is the same on DV_TEXT items in a given EHR. We don't think it should be
that high, since language cannot be guaranteed the same
Tom,
I have pondered the same issue before. I think it unlikely that language
would change inside an entry, but I did think of the possibility of
medicines, e.g. chinese medicines, or part thereof, being described by
specificly foreign names.
cheers,
eric
[ btw, you may wish to check your
Hi,
Anamnesis in psychiatry:
And then the disturbed patient said: Merdre. [Translation: shit]
Family history:
My father was diagnosed as suffering from: Engelse ziekte
[Translation: Rickets dissease]
Codingsystems
ICPC-1 Dutch version.
Code: R05.
Displayed text: Hoest
Added translation: Cough
A couple of technical questions prior to declaring the 0.9 baseline in
openEHR:
One of the major openEHR implementors here in Australia has suggested
moving the attributes 'language' and 'charset' in the class DV_TEXT to
some higher level class - e.g. COMPOSITION, since almost all the time it
11 matches
Mail list logo
