Sam Heard wrote:

>Dear All
>
>There has been an intense discussion - mainly Tom Beale and Matthew Darlison
>going on off line. I want to share some of my views with others on the
>approach to terminologies. I will deal with them one at a time.
>
>1. Language and terminologies.
>
>It is clear that we need to know what language we are working in to ensure
>that the rubric or phrase returned by the terminology service is
>appropriate. I have proposed in our GEHR work that this is kept at the level
>of a transaction (a transaction can only be in one language). The issue is
>that some words in different languages are lexically identical but their
>meaning is different. SO - if we allow different language rubrics in the
>same transaction - we will get an error one day as someone will read
>something erroneous.
>
I don't think we can do this - 1 Tx should = 1 language.

> For this reason - safety - I propose that transactions
>are consistent in language. I am sure that it has huge pragmatic advantages
>as well. A transaction in a language different from that of the workspace
>can be displayed in a different format and possibly be translated (as
>required).
>
>If people accept this - and I will need a lot of persuading that it is not a
>sensible restriction - it follows that terminology references - called
>coordinated terms in the present model though I do not believe they have a
>rubric so it may not be the best name - do not need a language associated
>with them. This can be drawn from the present transaction, workspace or
>whatever.
>
well except that we have designed the data types to be usable in many 
circumstances - not just in the EHR or in Transactions. The equivalent 
semantic we could use instead is to allow COORDINATED_TERM to have a 
language, and to force all coordinated terms in a TRANSACTION to have 
the same language.

>2. Terminology ID and versions
>
>When sharing the EHR we will need to keep tight control over the expression
>of the terminology in use. For this reason I would favour that we work with
>HL7 & CEN to have a table of terminologies used in openEHR and that versions
>of different terminologies are given different IDs. 
>
agree


- thomas beale




-
If you have any questions about using this list,
please send a message to d.lloyd at openehr.org

Reply via email to