HL7 Terminology (THO)
6.0.0 - Publication
HL7 Terminology (THO)
6.0.0 - Publication
This page is part of the HL7 Terminology (v6.0.0: Release) based on FHIR (HL7® FHIR® Standard) v5.0.0. This is the current published version in its permanent home (it will always be available at this URL). For a full list of available versions, see the Directory of published versions
| Retired as of 2019-03-20 |
<CodeSystem xmlns="http://hl7.org/fhir">
<id value="v3-MDFAttributeType"/>
<language value="en"/>
<text>
<status value="generated"/>
<div xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"><p class="res-header-id"><b>Generated Narrative: CodeSystem v3-MDFAttributeType</b></p><a name="v3-MDFAttributeType"> </a><a name="hcv3-MDFAttributeType"> </a><a name="v3-MDFAttributeType-en-US"> </a><div style="display: inline-block; background-color: #d9e0e7; padding: 6px; margin: 4px; border: 1px solid #8da1b4; border-radius: 5px; line-height: 60%"><p style="margin-bottom: 0px">Language: en</p></div><p><b>Properties</b></p><p><b>This code system defines the following properties for its concepts</b></p><table class="grid"><tr><td><b>Name</b></td><td><b>Code</b></td><td><b>URI</b></td><td><b>Type</b></td><td><b>Description</b></td></tr><tr><td>Specializes</td><td>Specializes</td><td/><td>Coding</td><td>The child code is a more narrow version of the concept represented by the parent code. I.e. Every child concept is also a valid parent concept. Used to allow determination of subsumption. Must be transitive, irreflexive, antisymmetric.</td></tr><tr><td>Generalizes</td><td>Generalizes</td><td/><td>Coding</td><td>Inverse of Specializes. Only included as a derived relationship.</td></tr><tr><td>internalId</td><td>internalId</td><td>http://terminology.hl7.org/CodeSystem/utg-concept-properties#v3-internal-id</td><td>code</td><td>The internal identifier for the concept in the HL7 Access database repository.</td></tr><tr><td>Status</td><td>status</td><td>http://hl7.org/fhir/concept-properties#status</td><td>code</td><td>Designation of a concept's state. Normally is not populated unless the state is retired.</td></tr></table><p><b>Concepts</b></p><p>This case-sensitive code system <code>http://terminology.hl7.org/CodeSystem/v3-MDFAttributeType</code> defines the following codes in a Is-A hierarchy:</p><table class="codes"><tr><td style="white-space:nowrap"><b>Code</b></td><td><b>Display</b></td><td><b>Definition</b></td><td><b>internalId</b></td><td><b>Status</b></td></tr><tr><td style="white-space:nowrap">ADDR<a name="v3-MDFAttributeType-ADDR"> </a></td><td>Address</td><td>For attributes representing the location at which an organization, person, or item may be found or reached.</td><td>10046</td><td>active</td></tr><tr><td style="white-space:nowrap">CD<a name="v3-MDFAttributeType-CD"> </a></td><td>Code</td><td>For attributes representing some concept. Note that names of individual things are not considered concepts.</td><td>10047</td><td>active</td></tr><tr><td style="white-space:nowrap">COM<a name="v3-MDFAttributeType-COM"> </a></td><td>Communication Address</td><td>For attributes representing communication addresses, such as telephones, fax, pagers, e-mail, Web-sites and other devices and their respective protocols. See also PHON.</td><td>10048</td><td>active</td></tr><tr><td style="white-space:nowrap">DESC<a name="v3-MDFAttributeType-DESC"> </a></td><td>Description</td><td>For attributes representing a statement used to describe something.</td><td>10049</td><td>active</td></tr><tr><td style="white-space:nowrap">DTTM<a name="v3-MDFAttributeType-DTTM"> </a></td><td>Date and Time</td><td>For attributes representing a point in time at which an event happened or will happen. Levels of precision and variation are part of this concept and should usually not be specified in separate attributes.</td><td>10050</td><td>active</td></tr><tr><td style="white-space:nowrap">EXPR<a name="v3-MDFAttributeType-EXPR"> </a></td><td>Formal Expression</td><td>For attributes representing formalized text that is to be evaluated primarily by computes. An attribute named "constraint\_text" is most likely such a formal expression and should be renamed to "constraint\_expr".</td><td>10051</td><td>active</td></tr><tr><td style="white-space:nowrap">FRC<a name="v3-MDFAttributeType-FRC"> </a></td><td>Fraction</td><td>For attributes that represent a fraction or proportion. The former attribute type PCT for "percentage" is superceded by FRC and is no longer permitted. See also QTY.</td><td>10052</td><td>active</td></tr><tr><td style="white-space:nowrap">ID<a name="v3-MDFAttributeType-ID"> </a></td><td>Identifier</td><td>For attributes that serve to identify some instance of an information model class. Note that real world Identifiers (e.g., SSN) exist not as attributes but as an association to a special information model class. The attribute type "id" without a prefix is reserved to be the main instance identifier of the class.</td><td>10053</td><td>active</td></tr><tr><td style="white-space:nowrap">IND<a name="v3-MDFAttributeType-IND"> </a></td><td>Indicator</td><td>For attributes representing a specific condition as true or false.</td><td>10054</td><td>active</td></tr><tr><td style="white-space:nowrap">NBR<a name="v3-MDFAttributeType-NBR"> </a></td><td>Number</td><td>For attributes representing dimensionless numbers. Note that there is a big conceptual difference between integer numbers and floating point numbers. See also QTY.</td><td>10055</td><td>active</td></tr><tr><td style="white-space:nowrap">NM<a name="v3-MDFAttributeType-NM"> </a></td><td>Name</td><td>For attributes that represent a name by which an instance of the class is known.</td><td>10056</td><td>active</td></tr><tr><td style="white-space:nowrap">PHON<a name="v3-MDFAttributeType-PHON"> </a></td><td>Phone</td><td>For attributes representing telephone number of a telecommunication device. See also COM.</td><td>10057</td><td>active</td></tr><tr><td style="white-space:nowrap">QTY<a name="v3-MDFAttributeType-QTY"> </a></td><td>Quantity</td><td>For attributes representing a quantity. The nature of the quantity must be further specified through the choice of data type and through additional constraints. For physical quantities (including elapsed time) the PQ data type must be used. For monetary amounts the MO data type must be used. Parallel unit attributes are not permitted in these cases. Counted objects are not physical quantities and the count nouns are not units of measure.</td><td>10058</td><td>active</td></tr><tr><td style="white-space:nowrap">TIME<a name="v3-MDFAttributeType-TIME"> </a></td><td>General Timing</td><td>A range of time between a start and an end time having a duration. The range may be infinite or undefined on either side.</td><td>10060</td><td>active</td></tr><tr><td style="white-space:nowrap">TMR<a name="v3-MDFAttributeType-TMR"> </a></td><td>Time Range</td><td>A range of time between a start and an end time having a duration. The range may be infinite or undefined on either side.</td><td>10059</td><td>active</td></tr><tr><td style="white-space:nowrap">TXT<a name="v3-MDFAttributeType-TXT"> </a></td><td>Text</td><td>For attributes representing non-descriptive, non-naming text not targeted to human interpretation. Formal expressions evaluated by computers should use the EXPR attribute type instead.</td><td>10061</td><td>active</td></tr><tr><td style="white-space:nowrap">VALUE<a name="v3-MDFAttributeType-VALUE"> </a></td><td>Value</td><td>For an attribute (e.g., Observation.value) that represents a value whose data type is determined dynamically and is not predefined by the static class diagram.</td><td>10062</td><td>active</td></tr></table></div>
</text>
<url value="http://terminology.hl7.org/CodeSystem/v3-MDFAttributeType"/>
<identifier>
<system value="urn:ietf:rfc:3986"/>
<value value="urn:oid:2.16.840.1.113883.5.74"/>
</identifier>
<version value="2.0.1"/>
<name value="MDFAttributeType"/>
<title value="MDFAttributeType"/>
<status value="retired"/>
<experimental value="false"/>
<date value="2019-03-20"/>
<publisher value="Health Level 7"/>
<contact>
<name value="Health Level Seven"/>
</contact>
<description
value="**Deprecation Comment:** Deprecated as per 11/2008 Harmonization cleanup; internal and obsolete HL7 usage, no longer used."/>
<caseSensitive value="true"/>
<hierarchyMeaning value="is-a"/>
<content value="complete"/>
<property>
<extension
url="http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-symmetry">
<valueCode value="antisymmetric"/>
</extension>
<extension
url="http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-transitivity">
<valueCode value="transitive"/>
</extension>
<extension
url="http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-reflexivity">
<valueCode value="irreflexive"/>
</extension>
<extension
url="http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-isNavigable">
<valueBoolean value="true"/>
</extension>
<extension
url="http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-relationshipKind">
<valueCode value="Specializes"/>
</extension>
<extension
url="http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-inverseName">
<valueString value="Generalizes"/>
</extension>
<code value="Specializes"/>
<description
value="The child code is a more narrow version of the concept represented by the parent code. I.e. Every child concept is also a valid parent concept. Used to allow determination of subsumption. Must be transitive, irreflexive, antisymmetric."/>
<type value="Coding"/>
</property>
<property>
<extension
url="http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-symmetry">
<valueCode value="antisymmetric"/>
</extension>
<extension
url="http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-transitivity">
<valueCode value="transitive"/>
</extension>
<extension
url="http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-reflexivity">
<valueCode value="irreflexive"/>
</extension>
<extension
url="http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-isNavigable">
<valueBoolean value="true"/>
</extension>
<extension
url="http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-relationshipKind">
<valueCode value="Generalizes"/>
</extension>
<extension
url="http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-inverseName">
<valueString value="Specializes"/>
</extension>
<code value="Generalizes"/>
<description
value="Inverse of Specializes. Only included as a derived relationship."/>
<type value="Coding"/>
</property>
<property>
<code value="internalId"/>
<uri
value="http://terminology.hl7.org/CodeSystem/utg-concept-properties#v3-internal-id"/>
<description
value="The internal identifier for the concept in the HL7 Access database repository."/>
<type value="code"/>
</property>
<property>
<code value="status"/>
<uri value="http://hl7.org/fhir/concept-properties#status"/>
<description
value="Designation of a concept's state. Normally is not populated unless the state is retired."/>
<type value="code"/>
</property>
<concept>
<code value="ADDR"/>
<display value="Address"/>
<definition
value="For attributes representing the location at which an organization, person, or item may be found or reached."/>
<property>
<code value="status"/>
<valueCode value="active"/>
</property>
<property>
<code value="internalId"/>
<valueCode value="10046"/>
</property>
</concept>
<concept>
<code value="CD"/>
<display value="Code"/>
<definition
value="For attributes representing some concept. Note that names of individual things are not considered concepts."/>
<property>
<code value="status"/>
<valueCode value="active"/>
</property>
<property>
<code value="internalId"/>
<valueCode value="10047"/>
</property>
</concept>
<concept>
<code value="COM"/>
<display value="Communication Address"/>
<definition
value="For attributes representing communication addresses, such as telephones, fax, pagers, e-mail, Web-sites and other devices and their respective protocols. See also PHON."/>
<property>
<code value="status"/>
<valueCode value="active"/>
</property>
<property>
<code value="internalId"/>
<valueCode value="10048"/>
</property>
</concept>
<concept>
<code value="DESC"/>
<display value="Description"/>
<definition
value="For attributes representing a statement used to describe something."/>
<property>
<code value="status"/>
<valueCode value="active"/>
</property>
<property>
<code value="internalId"/>
<valueCode value="10049"/>
</property>
</concept>
<concept>
<code value="DTTM"/>
<display value="Date and Time"/>
<definition
value="For attributes representing a point in time at which an event happened or will happen. Levels of precision and variation are part of this concept and should usually not be specified in separate attributes."/>
<property>
<code value="status"/>
<valueCode value="active"/>
</property>
<property>
<code value="internalId"/>
<valueCode value="10050"/>
</property>
</concept>
<concept>
<code value="EXPR"/>
<display value="Formal Expression"/>
<definition
value="For attributes representing formalized text that is to be evaluated primarily by computes. An attribute named "constraint\_text" is most likely such a formal expression and should be renamed to "constraint\_expr"."/>
<property>
<code value="status"/>
<valueCode value="active"/>
</property>
<property>
<code value="internalId"/>
<valueCode value="10051"/>
</property>
</concept>
<concept>
<code value="FRC"/>
<display value="Fraction"/>
<definition
value="For attributes that represent a fraction or proportion. The former attribute type PCT for "percentage" is superceded by FRC and is no longer permitted. See also QTY."/>
<property>
<code value="status"/>
<valueCode value="active"/>
</property>
<property>
<code value="internalId"/>
<valueCode value="10052"/>
</property>
</concept>
<concept>
<code value="ID"/>
<display value="Identifier"/>
<definition
value="For attributes that serve to identify some instance of an information model class. Note that real world Identifiers (e.g., SSN) exist not as attributes but as an association to a special information model class. The attribute type "id" without a prefix is reserved to be the main instance identifier of the class."/>
<property>
<code value="status"/>
<valueCode value="active"/>
</property>
<property>
<code value="internalId"/>
<valueCode value="10053"/>
</property>
</concept>
<concept>
<code value="IND"/>
<display value="Indicator"/>
<definition
value="For attributes representing a specific condition as true or false."/>
<property>
<code value="status"/>
<valueCode value="active"/>
</property>
<property>
<code value="internalId"/>
<valueCode value="10054"/>
</property>
</concept>
<concept>
<code value="NBR"/>
<display value="Number"/>
<definition
value="For attributes representing dimensionless numbers. Note that there is a big conceptual difference between integer numbers and floating point numbers. See also QTY."/>
<property>
<code value="status"/>
<valueCode value="active"/>
</property>
<property>
<code value="internalId"/>
<valueCode value="10055"/>
</property>
</concept>
<concept>
<code value="NM"/>
<display value="Name"/>
<definition
value="For attributes that represent a name by which an instance of the class is known."/>
<property>
<code value="status"/>
<valueCode value="active"/>
</property>
<property>
<code value="internalId"/>
<valueCode value="10056"/>
</property>
</concept>
<concept>
<code value="PHON"/>
<display value="Phone"/>
<definition
value="For attributes representing telephone number of a telecommunication device. See also COM."/>
<property>
<code value="status"/>
<valueCode value="active"/>
</property>
<property>
<code value="internalId"/>
<valueCode value="10057"/>
</property>
</concept>
<concept>
<code value="QTY"/>
<display value="Quantity"/>
<definition
value="For attributes representing a quantity. The nature of the quantity must be further specified through the choice of data type and through additional constraints. For physical quantities (including elapsed time) the PQ data type must be used. For monetary amounts the MO data type must be used. Parallel unit attributes are not permitted in these cases. Counted objects are not physical quantities and the count nouns are not units of measure."/>
<property>
<code value="status"/>
<valueCode value="active"/>
</property>
<property>
<code value="internalId"/>
<valueCode value="10058"/>
</property>
</concept>
<concept>
<code value="TIME"/>
<display value="General Timing"/>
<definition
value="A range of time between a start and an end time having a duration. The range may be infinite or undefined on either side."/>
<property>
<code value="status"/>
<valueCode value="active"/>
</property>
<property>
<code value="internalId"/>
<valueCode value="10060"/>
</property>
</concept>
<concept>
<code value="TMR"/>
<display value="Time Range"/>
<definition
value="A range of time between a start and an end time having a duration. The range may be infinite or undefined on either side."/>
<property>
<code value="status"/>
<valueCode value="active"/>
</property>
<property>
<code value="internalId"/>
<valueCode value="10059"/>
</property>
</concept>
<concept>
<code value="TXT"/>
<display value="Text"/>
<definition
value="For attributes representing non-descriptive, non-naming text not targeted to human interpretation. Formal expressions evaluated by computers should use the EXPR attribute type instead."/>
<property>
<code value="status"/>
<valueCode value="active"/>
</property>
<property>
<code value="internalId"/>
<valueCode value="10061"/>
</property>
</concept>
<concept>
<code value="VALUE"/>
<display value="Value"/>
<definition
value="For an attribute (e.g., Observation.value) that represents a value whose data type is determined dynamically and is not predefined by the static class diagram."/>
<property>
<code value="status"/>
<valueCode value="active"/>
</property>
<property>
<code value="internalId"/>
<valueCode value="10062"/>
</property>
</concept>
</CodeSystem>
IG © 2020+ HL7 International - Vocabulary Work Group. Package hl7.terminology#6.0.0 based on FHIR 5.0.0. Generated 2024-07-14
Links: Table of Contents |
QA Report
| Version History 
|
|
Propose a change