oship-dev team mailing list archive

[Tim Cook <timothywayne.cook@xxxxxxxxx>]

On Tue, 2009-03-24 at 07:29 -0300, Sergio Miranda Freire wrote:
> Hi Tim,
...
> The problem you pose now is beyond the scope of the rm specification. In the
> datatypes.text package there are classes that allow one to store for one
> entry into a specific terminology the terminology Id (with its version), the
> code and its rubric, and eventually a one to many mapping from this
> terminology to others. So could you give reasons why we need to keep several
> versions of a terminological system in OSHIP?

Certainly.  Over time, terminologies change (and sometimes very badly)
if you look at ICD over the years there are codes that mean one thing in
one version and something else in another.  If you record real patient
data at a point in time then you need to be able to look at the
terminology and medical knowledge "at that point in time".  This is not
only crucial to medico-legal issues but to research as well.

The one-to-one mapping should be TO A SPECIFIC VERSION we have had and
still have ongoing discussions about this on the various openEHR lists.

Cheers,
Tim


-- 
Timothy Cook, MSc
Health Informatics Research & Development Services
LinkedIn Profile:http://www.linkedin.com/in/timothywaynecook 
Skype ID == timothy.cook 
**************************************************************
*You may get my Public GPG key from  popular keyservers or   *
*from this link http://timothywayne.cook.googlepages.com/home*
**************************************************************

Attachment: signature.asc
Description: This is a digitally signed message part