The leaf variant of ITEM, to which a DATA_VALUE instance is attached.

Runtime name of this fragment, used to build runtime paths. This is the term provided via a clinical application or batch process to name this EHR construct: its retention in the EHR faithfully preserves the original label by which this entry was known to end users.

Design-time archetype identifier of this node taken from its generating archetype; used to build archetype paths. Always in the form of an at-code, e.g. at0005. This value enables a 'standardised' name for this node to be generated, by referring to the generating archetype local terminology.

At an archetype root point, the value of this attribute is always the stringified form of the _archetype_id_ found in the _archetype_details_ object.

Optional globally unique object identifier for root points of archetyped structures.

Links to other archetyped structures (data whose root object inherits from ARCHETYPED, such as ENTRY, SECTION and so on). Links may be to structures in other compositions.

Details of archetyping used on this node.

Audit trail from non-openEHR system of original commit of information forming the content of this node, or from a conversion gateway which has synthesised this node.

Flavour of null value, e.g. 253|unknown|, 271|no information|, 272|masked|, and 273|not applicable|.

Property representing leaf value object of ELEMENT. In real data, any concrete subtype of DATA_VALUE can be used.

Optional specific reason for null value; if set, _null_flavour_ must be set. Null reason may apply only to a minority of clinical data, commonly needed in reporting contexts.

The leaf variant of ITEM, to which a DATA_VALUE instance is attached.

Flavour of null value, e.g. 253|unknown|, 271|no information|, 272|masked|, and 273|not applicable|.

Property representing leaf value object of ELEMENT. In real data, any concrete subtype of DATA_VALUE can be used.

Optional specific reason for null value; if set, _null_flavour_ must be set. Null reason may apply only to a minority of clinical data, commonly needed in reporting contexts.

The leaf variant of ITEM, to which a DATA_VALUE instance is attached.

Runtime name of this fragment, used to build runtime paths. This is the term provided via a clinical application or batch process to name this EHR construct: its retention in the EHR faithfully preserves the original label by which this entry was known to end users.

Design-time archetype identifier of this node taken from its generating archetype; used to build archetype paths. Always in the form of an at-code, e.g. at0005. This value enables a 'standardised' name for this node to be generated, by referring to the generating archetype local terminology.

At an archetype root point, the value of this attribute is always the stringified form of the _archetype_id_ found in the _archetype_details_ object.

Optional globally unique object identifier for root points of archetyped structures.

Links to other archetyped structures (data whose root object inherits from ARCHETYPED, such as ENTRY, SECTION and so on). Links may be to structures in other compositions.

Details of archetyping used on this node.

Audit trail from non-openEHR system of original commit of information forming the content of this node, or from a conversion gateway which has synthesised this node.

Flavour of null value, e.g. 253|unknown|, 271|no information|, 272|masked|, and 273|not applicable|.

Property representing leaf value object of ELEMENT. In real data, any concrete subtype of DATA_VALUE can be used.

Optional specific reason for null value; if set, _null_flavour_ must be set. Null reason may apply only to a minority of clinical data, commonly needed in reporting contexts.