Package : datatypes
XML Type : CR
Comments : 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".
Parent : ANY
| Name |
Type |
cardinality |
Comment |
name
Element
: name
|
CV
|
0...1 |
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. |
value
Element
: value
|
CD
|
0...1 |
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. |
inverted
Attribute
: inverted
|
Boolean
|
0...1 |
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. |
<xs:complexType
xmlns:xs="http://www.w3.org/2001/XMLSchema" name="CR">
<xs:annotation>
<xs:documentation>
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".
</xs:documentation>
<xs:appinfo>
<sch:pattern
xmlns:sch="http://www.ascc.net/xml/schematron" name="validate CR">
<sch:rule abstract="true" id="rule-CR">
<sch:report test="(value or @nullFlavor) and not(@nullFlavor and node())">
<p>
A value component is required or else the
code role is NULL.
</p>
</sch:report>
</sch:rule>
</sch:pattern>
</xs:appinfo>
</xs:annotation>
<xs:complexContent>
<xs:extension base="ANY">
<xs:sequence>
<xs:element maxOccurs="1" minOccurs="0" name="name" type="CV">
<xs:annotation>
<xs:documentation>
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.
</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element maxOccurs="1" minOccurs="0" name="value" type="CD">
<xs:annotation>
<xs:documentation>
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.
</xs:documentation>
</xs:annotation>
</xs:element>
</xs:sequence>
<xs:attribute default="false" name="inverted" type="bn" use="optional">
<xs:annotation>
<xs:documentation>
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.
</xs:documentation>
</xs:annotation>
</xs:attribute>
</xs:extension>
</xs:complexContent>
</xs:complexType>
