Generated Narrative: StructureDefinition openEHR-EHR-CLUSTER.exclusion-symptom-sign.v0 Name Flags Card. Type Description & Constraints CLUSTER 0..* CLUSTER Exclusion of a symptom or sign #xD; Slices for items 1..* ITEM Ordered list of items - `CLUSTER` or `ELEMENT` objects - under this `CLUSTER`. Slice: Unordered, Closed by profile:$this #xD; items:at0001 0..1 ELEMENT Exclusion Statement #xD; value 0..1 DV_TEXT Property representing leaf value object of `ELEMENT`. #xD; items:at0002 0..1 ELEMENT Excluded Symptom #xD; Slices for value 0..1 DATA_VALUE Property representing leaf value object of `ELEMENT`. Slice: Unordered, Closed by type:$this #xD; value:DV_TEXT 0..1 DV_TEXT Property representing leaf value object of `ELEMENT`. #xD; value:DV_CODED_TEXT 0..1 DV_CODED_TEXT Property representing leaf value object of `ELEMENT`. Binding: Excluded Symptom ValueSet (required) #xD; Documentation for this format
HL7 International / Clinical Interoperability Council
Use to record a positive statement to explicitly record that a symptom or sign was reported as not present. Use to record exlicitly that a symptom or sign was absolutely not present. If this is not absolutely required, consider use of the 'Nil significant' data element within the CLUSTER.symptom_sign archetype. This archetype has been specifically designed to be used in the 'Structured detail' SLOT within the OBSERVATION.story archetype, but can also be used within other OBSERVATION or CLUSTER archetypes, where clinically appropriate.
To record a positive statement to explicitly record that a symptom or sign was reported as not present. Misuse:
© openEHR Foundation. This work is licensed under the Creative Commons Attribution-ShareAlike 3.0 License. To view a copy of this license, visit http://creativecommons.org/licenses/by-sa/3.0/.
Statement to explicitly record that a symptom or signe was reported as not present.
links.exists() implies links.empty().not()
Archetyped valid must satisfy exclusive conditions
is_archetype_root() xor archetype_details .empty()
Archetype node id valid must not be empty
Runtime name of this fragment, used to build runtime paths.
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.
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 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.
Ordered list of items - `CLUSTER` or `ELEMENT` objects - under this `CLUSTER`.
A statement about the exclusion of known symptoms in the health record.
Flavour of null value, e.g. `253|unknown|`, `271|no information|`, `272|masked|`, and `273|not applicable|`.
Property representing leaf value object of `ELEMENT`.
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.
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.
Identification of the specific symptom to which the Exclusion Statement applies.