Hi Ian, I guess this topic is not of great interest at the
moment L
It’s be great to have feedback though...Perhaps I’ll discuss this
offline.
Cheers,
-koray
From: openehr-technical-bounces@openehr.org
[mailto:openehr-technical-bounces@openehr.org] On Behalf Of Ian McNicoll
Sent: Monday, 17 May 2010 11:18 p.m.
To: For openEHR clinical discussions; For openEHR technical discussions
Subject: Governance of terminology lists
In a separate thread Koray
suggested:
"... do you think it would also be a good time to discuss the cases where
some custom defined/non included units need to be added for some properties in
DV_QUANTITY. You may remember our discussions around 'French' as Gauge unit -
which is not allowed currently. Although this may safely be added to
terminology I think many more will follow when people really get into niche
highly structured clinical modelling."
which raises a more general issue of governance arrangements for the openEHR
terminology and associated Amount properties terminology. There has been some
discussion, and I think consensus about using the Java implementation
terminology definitions as the source of truth, but the issue remains as to how
changes to these definitions and the properties definitions are to be managed,
including translation.
We need to have clear lines of communication and responsibility for acting on
requests to update these terminologies. A number of possibilities exist but I
wonder if this might not be usefully carried out within CKM, which has high
visibility, and mechanisms for editorial control and review. Request's like
Koray's will be reasonably common - we need to establish a reliable mechanism
for handling these, and changes to UCUM etc
I would be interested in other suggestions - the 'delivery' mechanism wiki, svn
, CKM etc is less important than the governance / review process behind it. I
also feel this is primarily a technical activity but will probably need somre
clinical input as a sanity check.
We also need to think about these issues in relation to possible alignment with
IHTSDO e.g should we start to think about using SNOMED-like primary technical
representations.
Regards,
Ian
Dr Ian McNicoll
office / fax +44(0)141 560 4657
mobile +44 (0)775 209 7859
skype ianmcnicoll
ian.mcnicoll@oceaninformatics.com
ian@mcmi.co.uk
Clinical Analyst Ocean Informatics openEHR Archetype Editorial Group
Member BCS Primary Health Care SG Group www.phcsg.org
/ BCS Health Scotland