Properties This code system defines the following properties for its concepts Name Code URI Type Description Specializes Specializes Coding 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. Generalizes Generalizes Coding Inverse of Specializes. Only included as a derived relationship. internalId internalId http://terminology.hl7.org/CodeSystem/utg-concept-properties#v3-internal-id code The internal identifier for the concept in the HL7 Access database repository. status status http://hl7.org/fhir/concept-properties#status code Designation of a concept's state. Normally is not populated unless the state is retired. Concepts This case-sensitive code system http://terminology.hl7.org/CodeSystem/v3-MDFAttributeType defines the following codes in a Is-A hierarchy: Code Display Definition internalId status ADDR Address For attributes representing the location at which an organization, person, or item may be found or reached. 10046 active CD Code For attributes representing some concept. Note that names of individual things are not considered concepts. 10047 active COM Communication Address For attributes representing communication addresses, such as telephones, fax, pagers, e-mail, Web-sites and other devices and their respective protocols. See also PHON. 10048 active DESC Description For attributes representing a statement used to describe something. 10049 active DTTM Date and Time 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. 10050 active EXPR Formal Expression 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". 10051 active FRC Fraction 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. 10052 active ID Identifier 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. 10053 active IND Indicator For attributes representing a specific condition as true or false. 10054 active NBR Number For attributes representing dimensionless numbers. Note that there is a big conceptual difference between integer numbers and floating point numbers. See also QTY. 10055 active NM Name For attributes that represent a name by which an instance of the class is known. 10056 active PHON Phone For attributes representing telephone number of a telecommunication device. See also COM. 10057 active QTY Quantity 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. 10058 active TIME General Timing A range of time between a start and an end time having a duration. The range may be infinite or undefined on either side. 10060 active TMR Time Range A range of time between a start and an end time having a duration. The range may be infinite or undefined on either side. 10059 active TXT Text 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. 10061 active VALUE 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. 10062 active
**Deprecation Comment:** Deprecated as per 11/2008 Harmonization cleanup; internal and obsolete HL7 usage, no longer used.
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.
Inverse of Specializes. Only included as a derived relationship.
The internal identifier for the concept in the HL7 Access database repository.
Designation of a concept's state. Normally is not populated unless the state is retired.
For attributes representing the location at which an organization, person, or item may be found or reached.
For attributes representing some concept. Note that names of individual things are not considered concepts.
For attributes representing communication addresses, such as telephones, fax, pagers, e-mail, Web-sites and other devices and their respective protocols. See also PHON.
For attributes representing a statement used to describe something.
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.
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".
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.
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.
For attributes representing a specific condition as true or false.
For attributes representing dimensionless numbers. Note that there is a big conceptual difference between integer numbers and floating point numbers. See also QTY.
For attributes that represent a name by which an instance of the class is known.
For attributes representing telephone number of a telecommunication device. See also COM.
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.
A range of time between a start and an end time having a duration. The range may be infinite or undefined on either side.
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.
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.