Hi all,

Any thoughts on the possibility of using the SNOMED approach to term rubrics
(i.e 403234567|Some SNOMED term|)  to make the human identification of
atNodes and archetypeIDs easier in documentation and AQL statements
i.e. node_identifier|rubric|?

The rubric aspect is purely for human identification and would be completely
ignored by any processing. The text would be assumed to be from the native
archetype language but could be in any language.

e.g.

openEHR-EHR-ACTION.procedure-unassisted_oxygen_delivery.v1|Unassisted oxygen
delivery|]/description[at0001]/items[at0002.1|Intervention|]

This makes AQL statements and other openEHR path based documentation much
easier to understand without the use of name/value constraints, which are
often unnecessary or indeed incorrect, particularly in a multi-lingual
environment but name/value could still be used where appropriate

e.g.

 openEHR-EHR-ACTION.procedure-unassisted_oxygen_delivery.v1|Unassisted
oxygen delivery| and name/value = 'Current
oxygen']/description[at0001]|Tree|/items[at0002.1|Intervention|]

 Would it even be useful as a documentation convention even if not supported
in current systems?

Ian

Dr Ian McNicoll
office +44 (0)1536 414994
fax +44 (0)1536 516317
mobile +44 (0)775 209 7859
skype ianmcnicoll
ian.mcnicoll at oceaninformatics.com

Clinical analyst, Ocean Informatics, UK
openEHR Clinical Knowledge Editor www.openehr.org/knowledge
Honorary Senior Research Associate, CHIME, UCL
BCS Primary Health Care  www.phcsg.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20110328/e296255b/attachment.html>

Reply via email to