Grahame Grieve wrote:

> This question is regarding Section 3.1 in the Support Package.
> I am using v0.9 

We should note that this is the draft document on the draft page 
http://www.deepthought.com.au/health/openEHR/openEHR.html

> The terminology definitions feel a little incomplete.
> The lists of strings given are reasonable, but the
> way the namespaces(?) are used seems a little slippery, 

I agree. E.g. "ISO:639-1:1998" - I have not found a standardised way to 
refer to "639-1" (ISO's own id for this standard) which includes both 
the string "ISO" (so we know where it's from) and some version number or 
year, whcih is commonly used to refer to versions in standards. In the 
terminology id section (same spec) you will see that terminologies are 
referred to using the syntax

name "(" version ")"

e.g. "SNOMED-CT(2003)"

At the moment there appears to be no normative specification for this 
either. THe HL7 list of terminology ids is missing numerous ones, and 
also does not include versions - well, some yes, like major release of 
ICD, and some no (version is included in the CD types - however, this is 
useless when just needing to identify a terminology, since version can 
change a lot of things).

In any case, we should adjust the constant definitions to conform to the 
terminology id syntax...

> and there is no consistency with regard to versioning
> in the list. Am I looking for too much from these
> definitions? 

well, the problem is that there is no consistency to identifying 
versions of terminologies out there in the real world. Some people call 
ICD9 and ICD10 different terminologies, some just different versions 
(even though there have been interior releases of each); what is 
ICD10CM? How are versions of SNOMED-CT identified? As far as we know, 
there is no current standard for this, even though there are obsolete 
CEN and ISO standards. I believe the real reason is that producers of 
terminologies do not obey well-known rules for change management, at 
least not the same rules!

> I would propose UCUM for Terminology_id_Units_of_measure_properties. 

UCUM is used for atomic properties in the Data Types specification i.e. 
the names of the properties measured by all the atomic units. But it 
does not include the property names of compound units, e..g 
"acceleration" is the property measured by the unit "m.s^-2".

- thomas


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

Reply via email to