Allow term codes to be used in openEHR path predicate shortcuts


Currently the Architecture Overview describes some shortcuts for predicates in openEHR paths, for example [at0001] is short for [@archetype_node_id = 'at0001']. Another shortcut allows name values to be expressed viz: [at0001, "sitting"] is short for [@archetype_node_id = "at0001" AND name/value = "sitting"]. A further shortcut that is commonly needed is if the name attribute is a coded text rather than just a string. The proposed idea is: [at0001, at0003], [at0001, snomed::10294055] etc.

This change is needed to support shorter paths in openEHR for data where the name field is coded rather than free text.


Ian McNicoll
February 2, 2021, 8:32 AM

My mistake - .oet not .opt

Ian McNicoll
February 8, 2021, 3:40 AM

Can we agree/ make it clear that anything between pipe symbols is ‘informational’ and not intended as a constraint?

Thomas Beale
February 8, 2021, 5:06 AM

yes, I think that should be taken as a global rule in fact. We really should document that in a few places…. you heard it here first

Sebastian Iancu
February 13, 2021, 7:14 AM

, , can you check my last changes on this proposal above?

ref: see the 4th bullet-para from

Thomas Beale
13 hours ago

Yep this looks right to me:


Thomas Beale

Raised By

Chunlan Ma


Affects versions