HL7 Terminology
1.0.0 - Publication

This page is part of the HL7 Terminology (v1.0.0: Release) based on FHIR R4. This is the current published version. For a full list of available versions, see the Directory of published versions

MDFAttributeType

Summary

Defining URL:http://terminology.hl7.org/CodeSystem/v3-MDFAttributeType
Version:2.0.0
Name:MDFAttributeType
Title:MDFAttributeType
Status:retired
Content:All the concepts defined by the code system are included in the code system resource
Definition:

Deprecation Comment: Deprecated as per 11/2008 Harmonization cleanup; internal and obsolete HL7 usage, no longer used.

Publisher:Health Level 7
OID:2.16.840.1.113883.5.74 (for OID based terminology systems)
Content Mode:Complete
Source Resource:XML / JSON / Turtle

This Code system is referenced in the content logical definition of the following value sets:

This CodeSystem is not used here; it may be used elsewhere

MDFAttributeType

Deprecation Comment: Deprecated as per 11/2008 Harmonization cleanup; internal and obsolete HL7 usage, no longer used.

Properties

CodeURLDescriptionType
SpecializesThe 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.Coding
GeneralizesInverse of Specializes. Only included as a derived relationship.Coding
internalIdhttp://terminology.hl7.org/CodeSystem/utg-concept-properties#v3-internal-idThe internal identifier for the concept in the HL7 Access database repository.code
statushttp://hl7.org/fhir/concept-properties#statusDesignation of a concept's state. Normally is not populated unless the state is retired.code

This code system http://terminology.hl7.org/CodeSystem/v3-MDFAttributeType defines the following codes:

CodeDisplayDefinitioninternalIdstatus
ADDR AddressFor attributes representing the location at which an organization, person, or item may be found or reached.10046active
CD CodeFor attributes representing some concept. Note that names of individual things are not considered concepts.10047active
COM Communication AddressFor attributes representing communication addresses, such as telephones, fax, pagers, e-mail, Web-sites and other devices and their respective protocols. See also PHON.10048active
DESC DescriptionFor attributes representing a statement used to describe something.10049active
DTTM Date and TimeFor 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.10050active
EXPR Formal ExpressionFor 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".10051active
FRC FractionFor 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.10052active
ID IdentifierFor 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.10053active
IND IndicatorFor attributes representing a specific condition as true or false.10054active
NBR NumberFor attributes representing dimensionless numbers. Note that there is a big conceptual difference between integer numbers and floating point numbers. See also QTY.10055active
NM NameFor attributes that represent a name by which an instance of the class is known.10056active
PHON PhoneFor attributes representing telephone number of a telecommunication device. See also COM.10057active
QTY QuantityFor 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.10058active
TIME General TimingA range of time between a start and an end time having a duration. The range may be infinite or undefined on either side.10060active
TMR Time RangeA range of time between a start and an end time having a duration. The range may be infinite or undefined on either side.10059active
TXT TextFor attributes representing non-descriptive, non-naming text not targeted to human interpretation. Formal expressions evaluated by computers should use the EXPR attribute type instead.10061active
VALUE ValueFor 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.10062active

History

DateActionAuthorCustodianComment
2020-05-06reviseTed KleinVocabulary WGMigrated to the UTG maintenance environment and publishing tooling.