Table 1: Overview of HL7 version 3 data types Name Symbol Description Defines the basic properties of every data value. This is an abstract type, meaning that no value can be just a data value without belonging to any concrete type. Every concrete type is a specialization of this general abstract DataValue type. DataValue ANY Boolean BL BL stands for the values of two-valued logic. A BL value can be either true or false, or, as any other value may be NULL. BN constrains the boolean type so that the value may not BooleanNonNull BN be NULL. This type is created for use within the data types specification where it is not appropriate for a null value to be used Data that is primarily intended for human interpretation or for further machine processing outside the scope of HL7. This includes unformatted or formatted written language, multimedia data, or structured information in as defined by a different standard (e.g., XML-signatures.) Instead of the data itself, an ED may contain only a reference (see TEL.) Note that ST is a specialization of the ED where the mediaType is fixed to text/plain. The character string data type stands for text data, primarily intended for machine processing (e.g., sorting, querying, indexing, etc.) Used for names, symbols, and formal expressions. A CD represents any kind of concept usually by giving a code defined in a code system. A CD can contain the original text or phrase that served as the basis of the coding and one or more translations into different coding systems. A CD can also contain qualifiers to describe, e.g., the concept of a \"left foot\" as a postcoordinated term built from the primary code \"FOOT\" and the qualifier \"LEFT\". In cases of an exceptional value, the CD need not contain a code but only the original text describing that concept. Coded data in its simplest form, where only the code is not predetermined. The code system and code system version are fixed by the context in which the CS value occurs. CS is used for coded attributes that have a Encapsulated Data ED Character String ST Concept Descriptor CD Coded Simple Value CS Table 1: Overview of HL7 version 3 data types Name Symbol Description single HL7-defined value set. Coded data, where the coding system from which the code comes is ordered. CO adds semantics related to ordering so that models that make use of such domains may introduce model elements that involve statements about the order of the terms in a domain. Coded data that consists of a coded value and, optionally, coded value(s) from other coding systems that identify the same concept. Used when alternative codes may exist. A character string that optionally may have a code attached. The text must always be present if a code is present. The code is often a local code. An identifier that uniquely identifies a thing or object. Examples are object identifier for HL7 RIM objects, medical record number, order id, service catalog item id, Vehicle Identification Number (VIN), etc. Instance identifiers are defined based on ISO object identifiers. A telephone number (voice or fax), e-mail address, or other locator for a resource mediated by telecommunication equipment. The address is specified as a Universal Resource Locator (URL) qualified by time specification and use codes that help in deciding which address to use for a given time and purpose. Mailing and home or office addresses. A sequence of address parts, such as street or post office Box, city, postal code, country, etc. A name for a person, organization, place or thing. A sequence of name parts, such as given name or family name, prefix, suffix, etc. Examples for entity name values are \"Jim Bob Walton, Jr.\Inc.\\"Lake Tahoe\etc. An entity name may be as simple as a character string or may consist of several entity name parts, such as, \"Jim\\"Bob\\"Walton\and \"Jr.\\"Health Level Seven\" and \"Inc.\A restriction of entity name that is effectively a simple string used for a simple name for things and places. Coded Ordinal CO Coded With Equivalents CE Character String with Code SC Instance Identifier II Telecommunication Address TEL Postal Address AD Entity Name EN Trivial Name TN Table 1: Overview of HL7 version 3 data types Name Symbol Description An EN used when the named Entity is a Person. A sequence of name parts, such as given name or family name, prefix, suffix, etc. A name part is a restriction of entity name part that only allows those entity name parts qualifiers applicable to person names. Since the structure of entity name is mostly determined by the requirements of person name, the restriction is very minor. An EN used when the named Entity is an Organization. A sequence of name parts. Integer numbers (-1,0,1,2, 100, 3398129, etc.) are precise numbers that are results of counting and enumerating. Integer numbers are discrete, the set of integers is infinite but countable. No arbitrary limit is imposed on the range of integer numbers. Two NULL flavors are defined for the positive and negative infinity. Fractional numbers. Typically used whenever quantities are measured, estimated, or computed from other real numbers. The typical representation is decimal, where the number of significant decimal digits is known as the precision. A quantity constructed as the quotient of a numerator quantity divided by a denominator quantity. Common factors in the numerator and denominator are not automatically cancelled out. The RTO data type supports titers (e.g., \"1:128\") and other quantities produced by laboratories that truly represent ratios. Ratios are not simply \"structured numerics\pressure measurements (e.g. \"120/60\") are not ratios. In many cases the REAL should be used instead of the RTO. A dimensioned quantity expressing the result of measuring. An MO is a quantity expressing the amount of money in some currency. Currencies are the units in which monetary amounts are denominated in different economic regions. While the monetary amount is a single kind of quantity (money) the exchange rates between the different units are variable. This is the principle difference between PQ and MO, and the reason why currency Person Name PN Organization Name ON Integer Number INT Real Number REAL Ratio RTO Physical Quantity PQ Monetary Amount MO Table 1: Overview of HL7 version 3 data types Name Symbol Description units are not physical units. Point in Time TS A quantity specifying a point on the axis of natural time. A point in time is most often represented as a calendar expression. A value that contains other distinct values in no particular order. A value that contains other discrete (but not necessarily distinct) values in a defined sequence. An unordered collection of values, where each value can be contained more than once in the collection. A set of consecutive values of an ordered base data type. A set of data values that have a valid-time property and thus conform to the HXIT type. The history information is not limited to the past; expected future values can also appear. A generic data type extension used to specify a probability expressing the information producer's belief that the given value holds. An interval of time that recurs periodically. PIVL has two properties, phase and period. phase specifies the \"interval prototype\" that is repeated every .. Specifies a periodic interval of time where the recurrence is based on activities of daily living or other important events that are time-related but not fully determined by time. A
, specifying the timing of events and actions and the cyclical validity-patterns that may exist for certain kinds of information, such as phone numbers (evening, daytime), addresses (so called \"snowbirds,\" residing closer to the equator during winter and farther from the equator during summer) and office hours. A generic data type extension specifying uncertainty of quantitative data using a distribution function and its parameters. Aside from the specific parameters of the distribution, a mean (expected value) and standard deviation is always given to help maintain a minimum Set Sequence Bag Interval SET LIST BAG IVL History HIST Uncertain Value - Probabilistic Periodic Interval of Time UVP PIVL Event-Related Periodic EIVL Interval of Time General Timing Specification GTS Parametric Probability PPD Distribution Table 1: Overview of HL7 version 3 data types Name Symbol Description layer of interoperability if receiving applications cannot deal with a certain probability distribution.