Clinical Document Architecture with Australian Schema
1.0.0 - current Australia flag

Clinical Document Architecture with Australian Schema - Local Development build (v1.0.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions

Logical Model: CR - Detailed Descriptions

Active as of 2024-08-29

Definitions for the CR logical model.

Guidance on how to interpret the contents of this table can be found here

0. CR
Definition

A concept qualifier code with optionally named role. Both qualifier role and value codes must be defined by the coding system. For example, if SNOMED RT defines a concept "leg", a role relation "has-laterality", and another concept "left", the concept role relation allows to add the qualifier "has-laterality: left" to a primary code "leg" to construct the meaning "left leg".

Control1..*
Logical ContainerADHA ClinicalDocument (CDA Class)
XML FormatIn the XML format, this property has the namespace urn:hl7-org:v3.
Invariantsvalue-null-cr: Must contain value or nullFlavor. If nullFlavor is present, name and value must not be present. ((value.exists() or nullFlavor.exists()) and (nullFlavor.exists() implies (name | value).empty()))
2. CR.inverted
Definition

Indicates if the sense of the role name is inverted. This can be used in cases where the underlying code system defines inversion but does not provide reciprocal pairs of role names. By default, inverted is false.

Control0..1
Typeboolean(bn: BooleanNonNull)
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
XML FormatIn the XML format, this property is represented as an attribute.
LabelInversion Indicator
4. CR.name
Definition

Specifies the manner in which the concept role value contributes to the meaning of a code phrase. For example, if SNOMED RT defines a concept "leg", a role relation "has-laterality", and another concept "left", the concept role relation allows to add the qualifier "has-laterality: left" to a primary code "leg" to construct the meaning "left leg". In this example "has-laterality" is the CR.name.

Control0..1
Typehttp://hl7.org/cda/stds/core/StructureDefinition/CV
LabelName
6. CR.value
Definition

The concept that modifies the primary code of a code phrase through the role relation. For example, if SNOMED RT defines a concept "leg", a role relation "has-laterality", and another concept "left", the concept role relation allows adding the qualifier "has-laterality: left" to a primary code "leg" to construct the meaning "left leg". In this example "left" is the CR.value.

Control0..1
Typehttp://hl7.org/cda/stds/core/StructureDefinition/CD
LabelValue

Guidance on how to interpret the contents of this table can be found here

0. CR
Definition

A concept qualifier code with optionally named role. Both qualifier role and value codes must be defined by the coding system. For example, if SNOMED RT defines a concept "leg", a role relation "has-laterality", and another concept "left", the concept role relation allows to add the qualifier "has-laterality: left" to a primary code "leg" to construct the meaning "left leg".


Base definition for all types defined in FHIR type system.

ShortBase for all types and resources
Control10..*
Is Modifierfalse
Logical ContainerADHA ClinicalDocument (CDA Class)
XML FormatIn the XML format, this property has the namespace urn:hl7-org:v3.
Invariantsvalue-null-cr: Must contain value or nullFlavor. If nullFlavor is present, name and value must not be present. ((value.exists() or nullFlavor.exists()) and (nullFlavor.exists() implies (name | value).empty()))
2. CR.inverted
Definition

Indicates if the sense of the role name is inverted. This can be used in cases where the underlying code system defines inversion but does not provide reciprocal pairs of role names. By default, inverted is false.

Control0..1
Typeboolean(bn: BooleanNonNull)
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
XML FormatIn the XML format, this property is represented as an attribute.
LabelInversion Indicator
4. CR.name
Definition

Specifies the manner in which the concept role value contributes to the meaning of a code phrase. For example, if SNOMED RT defines a concept "leg", a role relation "has-laterality", and another concept "left", the concept role relation allows to add the qualifier "has-laterality: left" to a primary code "leg" to construct the meaning "left leg". In this example "has-laterality" is the CR.name.

Control0..1
Typehttp://hl7.org/cda/stds/core/StructureDefinition/CV
LabelName
6. CR.value
Definition

The concept that modifies the primary code of a code phrase through the role relation. For example, if SNOMED RT defines a concept "leg", a role relation "has-laterality", and another concept "left", the concept role relation allows adding the qualifier "has-laterality: left" to a primary code "leg" to construct the meaning "left leg". In this example "left" is the CR.value.

Control0..1
Typehttp://hl7.org/cda/stds/core/StructureDefinition/CD
LabelValue

Guidance on how to interpret the contents of this table can be found here

0. CR
Definition

A concept qualifier code with optionally named role. Both qualifier role and value codes must be defined by the coding system. For example, if SNOMED RT defines a concept "leg", a role relation "has-laterality", and another concept "left", the concept role relation allows to add the qualifier "has-laterality: left" to a primary code "leg" to construct the meaning "left leg".

ShortBase for all types and resources
Control1..*
Is Modifierfalse
Logical ContainerADHA ClinicalDocument (CDA Class)
XML FormatIn the XML format, this property has the namespace urn:hl7-org:v3.
Invariantsvalue-null-cr: Must contain value or nullFlavor. If nullFlavor is present, name and value must not be present. ((value.exists() or nullFlavor.exists()) and (nullFlavor.exists() implies (name | value).empty()))
2. CR.nullFlavor
Definition

If a value is an exceptional value (NULL-value), this specifies in what way and why proper information is missing.

Control0..1
BindingThe codes SHALL be taken from CDANullFlavor
(required to http://hl7.org/cda/stds/core/ValueSet/CDANullFlavor)
Typecode(cs: Coded Simple Value)
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
XML FormatIn the XML format, this property is represented as an attribute.
LabelExceptional Value Detail
4. CR.inverted
Definition

Indicates if the sense of the role name is inverted. This can be used in cases where the underlying code system defines inversion but does not provide reciprocal pairs of role names. By default, inverted is false.

Control0..1
Typeboolean(bn: BooleanNonNull)
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
XML FormatIn the XML format, this property is represented as an attribute.
LabelInversion Indicator
6. CR.name
Definition

Specifies the manner in which the concept role value contributes to the meaning of a code phrase. For example, if SNOMED RT defines a concept "leg", a role relation "has-laterality", and another concept "left", the concept role relation allows to add the qualifier "has-laterality: left" to a primary code "leg" to construct the meaning "left leg". In this example "has-laterality" is the CR.name.

Control0..1
Typehttp://hl7.org/cda/stds/core/StructureDefinition/CV
LabelName
8. CR.value
Definition

The concept that modifies the primary code of a code phrase through the role relation. For example, if SNOMED RT defines a concept "leg", a role relation "has-laterality", and another concept "left", the concept role relation allows adding the qualifier "has-laterality: left" to a primary code "leg" to construct the meaning "left leg". In this example "left" is the CR.value.

Control0..1
Typehttp://hl7.org/cda/stds/core/StructureDefinition/CD
LabelValue