AD-1: Street Address (ST)

Definition: This component specifies the street or mailing address of a person or institution. When referencing an institution, this first component is used to specify the institution name. When used in connection with a person, this component specifies the first line of the address.

AD-2: Other Designation (ST)

Definition: This component specifies the second line of address. In general, it qualifies address. Examples: Suite 555 or Fourth Floor. When referencing an institution, this component specifies the street address.

AD-3: City (ST)

Definition: This component specifies the city, district or place where the addressee is located depending upon the national convention for formatting addresses for postal usage.

AD-4: State or Province (ST)

Definition: This component specifies the state or province where the addressee is located. State or province should be represented by the official postal service codes for that country.

AD-5: Zip or Postal Code (ST)

Definition: This component specifies the zip or postal code where the addressee is located. Zip or postal codes should be represented by the official codes for that country. In the US, the zip code takes the form 99999[-9999], while the Canadian postal code takes the form A9A9A9 and the Australian Postcode takes the form 9999.

AD-6: Country (ID)

Definition: This component specifies the country where the addressee is located. HL7 specifies that the 3-character (alphabetic) form of ISO 3166 be used for the country code. Refer to HL7 Table 0399 - Country Code in Chapter 2C, Code Tables, for valid values.

AD-7: Address Type (ID)

Definition: This component specifies the kind or type of address. Refer to HL7 Table 0190 - Address Type in Chapter 2C, Code Tables, for valid values.

AD-8: Other Geographic Designation (ST)

Definition: This component specifies any other geographic designation that may be necessary. It includes county, bioregion, SMSA, etc.

AUI-1: Authorization Number (ST)

Definition: Identifier assigned to the authorization.

AUI-2: Date (DT)

Definition: Date of authorization.

AUI-3: Source (ST)

Definition: Source of authorization.

CCD-1: Invocation Event (ID)

Definition: Specifies the code for the event precipitating/triggering the charge activity. Refer to HL7 Table 0100 - Invocation event for valid values.

CCD-2: Date/time (DTM)

Definition: The second component is used to express the exact time to charge for the ordered service; it is used only when the CCD.1 value is T. When used, it is expressed as a DTM data type.

CCP-1: Channel Calibration Sensitivity Correction Factor (NM)

Definition: This component defines a correction factor for channel sensitivity, which may be derived from the last calibration procedure performed. The actual channel sensitivity is the nominal channel sensitivity given in the previous component multiplied by the unitless correction factor.

CCP-2: Channel Calibration Baseline (NM)

Definition: This component defines the actual channel baseline (the data value which corresponds to a nominal input signal of zero). The actual baseline may differ from the ideal because of a dc offset in the amplifier connected to the ADC. The actual baseline values for all channels (which need not be integers) may be determined at the time of calibration as the average digitized values obtained when a zero input signal is connected to each channel.

CCP-3: Channel Calibration Time Skew (NM)

Definition: This component defines the time difference between the nominal sampling (digitization) time (which would be the same for all channels) and the actual sampling time of the channel, in seconds (or fractions thereof). This value will differ from zero when all channels in the montage are not sampled simultaneously, as occurs in systems, which sample successive channels at regular time intervals. This value may be determined from a calibration procedure in which an identical time-varying signal is applied to all channels and interchannel time differences are estimated, or more commonly it may be taken from the manufacturer’s specifications for the digitizing system used. For example, for a system which samples successive channels at regular time intervals t, the time skew of channel number n would be (n-1)t. The actual time of sampling (digitization) of sample number m of channel number n in such a system would be R + (m-1)/f + (n-1)t, where R is the reference time at the start of the epoch and f is the channel sampling frequency (t < 1/f).

CD-1: Channel Identifier (WVI)

Definition: This component specifies the number and name of the recording channel where waveform data is transmitted.

CD-2: Waveform Source (WVS)

Definition: This component identifies the source of the waveform connected to the channel. Two names may be specified if it is necessary to individually identify the two inputs for a waveform. Only one name need be specified if the channel is connected to a single input. For example, in EKG recordings typically only one name is used (such as I or II); in electroencephalography, two names are typically used, one for each input of the differential amplifier (such as F3 and C3).

CD-3: Channel Sensitivity and Units (CSU)

Definition: This component defines the channel sensitivity (gain) and the units in which it is measured.

CD-4: Channel Calibration Parameters (CCP)

Definition: This component identifies the corrections to channel sensitivity, the baseline, and the channel time skew.

CD-5: Channel Sampling Frequency (NM)

Definition: This component defines the sampling frequency in hertz of the channel, that is, the reciprocal of the time in seconds between successive samples

CD-6: Minimum and Maximum Data Values (NR)

Definition: This component defines the minimum and maximum data values which can occur in this channel in the digital waveform data, that is, the range of the ADC. , and also specifies whether or not non-integral data values may occur in this channel in the waveform data. If the minimum and maximum values are both integers (or not present), only integral data values may be used in this channel. If either the minimum or the maximum value contains a decimal point, then non-integral as well as integral data values may be used in this channel. For an n-bit signed ADC, the nominal baseline B = 0, and the minimum (L) and maximum (H) values may be calculated as follows:

L = -2n-1

H = 2n-1 - 1

For an unsigned n-bit ADC, the minimum value L = 0, and the nominal baseline value (B) and maximum value (H) may be calculated from the formulas,

B = 2n-1

H = 2n - 1

The actual signal amplitude A (for differentially amplified potential measurements, the potential at electrode number one minus that at electrode number two) may be calculated from the value D (range L to H) in the waveform data using the actual baseline value B and the nominal sensitivity S and actual sensitivity correction factor C by the formula,

A = SC(D-B)

CF-1: Identifier (ST)

Definition: Sequence of characters (the code) that uniquely identifies the item being referenced by the <text>. Different coding schemes will have different elements here.

CF-2: Formatted Text (FT)

Definition: Name or description of the item in question with the addition of embedded formatting instructions.

CF-3: Name of Coding System (ID)

Definition: Contains the name of the coding system employed.

Refer to HL7 Table 0396 - Coding System in Chapter 2C, Code Tables, for valid values.

As of v2.7 this component is required when CF.1 is populated and CF.14 is not populated. Both CF.3 and CF.14 may be populated. Receivers should not identify a code based on its position within the tuples (Identifier, Alternate Identifier, or Second Alternate Identifier) or position within a repeating field. Instead, the receiver should always examine the coding system as specified in CF.3 and/orCF.14, the Coding System component or the Coding System OID, for the tuple.

CF-4: Alternate Identifier (ST)

Definition: A sequence of characters that uniquely identifies an alternate code. Analogous to CF-1 Identifier.

Usage Notes: The Alternate Identifier is used to represent the local or user seen code as described. If present, it obeys the same rules of use and interpretation as described for component 1. If both are present, the identifiers in component 4 and component 1 should have exactly the same meaning, i.e., they should be exact synonyms.

CF-5: Alternate Formatted Text (FT)

Definition: Name or description of the alternate identifier in question with the addition of embedded formatting instructions. Analogous to CF.2 Formatted Text.

CF-6: Name of Alternate Coding System (ID)

Definition: Contains the name of the coding system employed for the alternate identifier. Analogous to CF.3 Name of Coding System.

Refer to HL7 Table 0396 - Coding System in Chapter 2C, Code Tables, for valid values.

As of v2.7 this component is required when CF.4 is populated andCF.17 is not populated. Both CF.6 and CF.17 may be populated. Receivers should not identify a code based on its position within the tuples (Identifier, Alternate Identifier, or Second Alternate Identifier) or position within a repeating field. Instead, the receiver should always examine the coding ystem as specified inCF.6 and/or CF.17, the Coding System component or the Coding System OID, for the tuple.

CF-7: Coding System Version ID (ST)

Definition: This component carries the version for the coding system identified by components 1-3. If CF.3 is populated with a value other than HL7nnnn or is of table type user-defined, version ID must be valued with an actual version ID. If CF.3 is populated with a value of HL7nnnn and nnnn is of table type HL7, version ID may have an actual value or it may be absent. If version ID is absent, it will be interpreted to have the same value as the HL7 version number in the message header.

CF-8: Alternate Coding System Version ID (ST)

Definition: This component carries the version for the coding system identified by components 4-6. Analogous To CF.7 Coding System Version ID.

CF-9: Original Text (ST)

Definition: The text as seen and/or selected by the user who entered the data. Original text can be used in a structured user interface to capture what the user saw as a representation of the code on the data input screen, or in a situation where the user dictates or directly enters text, it is the text entered or uttered by the user. In a situation where the code is assigned sometime after the text was entered, original text is the text or phrase used as the basis for assigning the code.

CF-10: Second Alternate Identifier (ST)

Definition: A sequence of characters that uniquely identifies an alternate code. Analogous to CF.1 Identifier.

CF-11: Second Alternate Formatted Text (FT)

Definition: The descriptive or textual name of the Second Alternate Identifier. Analogous to CF.2 Formatted Text.

CF-12: Name of Second Alternate Coding System (ID)

Definition: Identifies the coding scheme being used in the Second Alternate Identifier component. Analogous to CF. Name of Coding System.

This component is required when CF.10 is populated and CF.20 is not populated. Both CF.10 and CF.20 may be populated. Receivers should not identify a code based on its position within the tuples (Identifier, Alternate Identifier, or Second Alternate Identifier) or position within a repeating field. Instead, the receiver should always examine the coding ystem as specified in CF.12 and/or CF.20 the Coding System component or the Coding System OID for the tuple.

CF-13: Second Alternate Coding System Version ID (ST)

Definition: This component carries the version for the coding system identified by components 10-12. Analogous To CF.7 Coding System Version ID.

CF-14: Coding System OID (ST)

Definition: This component contains the ISO Object Identifier (OID) for the coding system or value set named in CNE.3. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used.

This component is required when CF.1 is populated and CF.3 is not populated. Both CF.3 and CF.14 may be populated.

CF-15: Value Set OID (ST)

Definition: This component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.1 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields.

CF-16: Value Set Version ID (DTM)

Definition: This component carries the version for the value set identified by CF.15. The version is a date. The date is the date/time that the value set being used was published.

Value set version ID is required if CF.15 is populated.

CF-17: Alternate Coding System OID (ST)

Definition: This component contains the ISO Object Identifier (OID) for the coding system or value set named in CF.6. Analogous To CF.14 Coding System OID.

The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used.

This component is required when CF.4 is populated and CF.6 is not populated. Both CF.6 and CF.17 may be populated.

CF-18: Alternate Value Set OID (ST)

Definition: This component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CF.4 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used.

A value set may or need not be present irrespective of other fields.

CF-19: Alternate Value Set Version ID (DTM)

Definition: This component carries the version for the value set identified by CF.18. The version is a date. The date is the date/time that the value set being used was published.

Value set version ID is required if CF.18 is populated.

CF-20: Second Alternate Coding System OID (ST)

Definition: This component contains the ISO Object Identifier (OID) for the coding system or value set named in CF.12. Analogous To CF.14 Coding System OID.

The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used.

This component is required when CF.10 is populated and CF.12 is not populated. Both CF.12 and CF.20 may be populated.

CF-21: Second Alternate Value Set OID (ST)

Definition: This component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CF.10 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used.

A value set may or need not be present irrespective of other fields.

CF-22: Second Alternate Value Set Version ID (DTM)

Definition: This component carries the version for the value set identified by CF.21. The version is a date. The date is the date/time that the value set being used was published.

Value set version ID is required if CF.21 is populated.

CNE-1: Identifier (ST)

Definition: The first component contains the sequence of characters (the code) that uniquely identifies the item being referenced by the CNE.2. Different coding schemes will have different elements here.

Usage Note: The identifier is required and must be a valid code.

CNE-2: Text (ST)

Definition: The second component contains the descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. This is the corresponding text assigned by the coding system to the identifier.

Usage Note: Text description of code is optional but its use should be encouraged since it makes messages easier to review for accuracy, especially during interface testing and debugging.

CNE-3: Name of Coding System (ID)

Definition: The third component contains the code for the name of the coding system from which the value in CNE.1 is obtained.Refer to HL7 Table 0396 - Coding Systems in Chapter 2C, Code Tables, for valid values. Each coding system is assigned a unique identifier.

As of v2.7 this component is required when CNE.1 is populated and CNE.14 is not populated. Both CNE.3 and CNE.14 may be populated. Receivers should not identify a code based on its position within the tuples (Identifier, Alternate Identifier, or Second Alternate Identifier) or position within a repeating field. Instead, the receiver should always examine the codingSystem as specified in CNE.3 and/or CNE.14 the Coding System component or the Coding System OID for the tuple.The combination of the identifier and name of coding system represent a unique concept for a data item.

Some organizations that publish code sets author more than one. The coding system, then, to be unique, is a concatenation of the name of the coding authority organization and the name of its code set or table. When an HL7 table is used for a CNE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number. Similarly, ISO tables will be named ISOnnnn, where nnnn is the ISO table number.

Usage Note: The following statement is retained for backward compatibility as of v2.7. Best practice would recommend that this component always be populated. However, if the field narrative explicitly states "Refer to HL7 Table nnnn for valid values”, and, if the sending and receiving systems are HL7 compliant, the coding system would be known from the standard. This would be similar to a field with an ID data type, except that there is a second triplet in which to express an alternate code.

CNE-4: Alternate Identifier (ST)

Definition: A sequence of characters that uniquely identifies an alternate code. Analogous to CNE.1 Identifier.

Usage Notes: The Alternate Identifier is used to represent the local or user seen code as described. If present, it obeys the same rules of use and interpretation as described for component 1. If both are present, the identifiers in component 4 and component 1 should have exactly the same meaning, i.e., they should be exact synonyms.

CNE-5: Alternate Text (ST)

Definition: The descriptive or textual name of the alternate identifier. Analogous to CNE.2 Text.

Usage Notes: If present, CNE.5 obeys the same rules of use and interpretation as described for CNE.2.

CNE-6: Name of Alternate Coding System (ID)

Definition: Identifies the coding scheme being used in the alternate identifier component. Analogous to CNE.3 Name of Coding System. Refer to HL7 Table 0396 - Coding Systems in Chapter 2C, Code Tables, for valid values.

As of v2.7 this component is required when CNE.4 is populated and CNE.17 is not populated. Both CNE.6 and CNE.17 may be populated. Receivers should not identify a code based on its position within the tuples (Identifier, Alternate Identifier, or Second Alternate Identifier) or position within a repeating field. Instead, the receiver should always examine the codingSystem as specified in CNE.6 and/or CNE.17, the "Coding System" component or the "Coding System OID", for the tuple.

Usage Notes: If present, CNE.6 obeys the same rules of use and interpretation as described for CNE.3.

CNE-7: Coding System Version ID (ST)

Definition: the version ID for the coding system identified by CNE.3. It belongs conceptually to components 1-3 and appears here only for reasons of backward compatibility.

Usage Note: If the coding system is any system other than an "HL7 coding system," version ID must be valued with an actual version ID. If the coding system is "HL7 coding system," version ID may have an actual value or it may be absent. If version ID is absent, it will be interpreted to have the same value as the HL7 version number in the message header. Text description of code is optional but its use should be encouraged since it makes messages easier to review for accuracy, especially during interface testing and debugging.

CNE-8: Alternate Coding System Version ID (ST)

Definition: the version ID for the coding system identified by CNE.6. It belongs conceptually to the group of Alternate components (see note 2.A.1) and appears here only for reasons of backward compatibility. Analogous to CNE.7 Coding System Version ID.

Usage Notes: If present, CNE.8 obeys the same rules of use and interpretation as described for CNE.7.

CNE-9: Original Text (ST)

Definition: The text as seen and/or selected by the user who entered the data. Original text can be used in a structured user interface to capture what the user saw as a representation of the code on the data input screen, or in a situation where the user dictates or directly enters text, it is the text entered or uttered by the user. In a situation where the code is assigned sometime after the text was entered, original text is the text or phrase used as the basis for assigning the code.

CNE-10: Second Alternate Identifier (ST)

Definition: A sequence of characters that uniquely identifies a second alternate code. Analogous to CN-1 Identifier.

CNE-11: Second Alternate Text (ST)

Definition: The descriptive or textual name of the Second Alternate Identifier. Analogous to CNE.2 Text.

CNE-12: Name of Second Alternate Coding System (ID)

Definition: Identifies the coding scheme being used in the Second Alternate Identifier component. Analogous to CNE.3 Name of Coding System. Refer to HL7 Table 0396 - Coding Systems in Chapter 2C, Code Tables, for valid values.

As of v2.7 this component is required when CNE.10 is populated and CNE.20 is not populated. Both CNE.12 and CNE.20 may be populated. Receivers should not identify a code based on its position within the tuples (Identifier, Alternate Identifier, or Second Alternate Identifier) or position within a repeating field. Instead, the receiver should always examine the codingSystem as specified in CNE.12 and/or CNE.20, the "Coding System" component or the "Coding System OID", for the tuple.

CNE-13: Second Alternate Coding System Version ID (ST)

Definition: This component carries the version for the coding system identified by components 10-12. Analogous to CNE.7 Coding System Version ID.

CNE-14: Coding System OID (ST)

Definition: This component contains the ISO Object Identifier (OID) for the coding system or value set named in CNE.3. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used.

This component is required when CNE.1 is populated and CNE.3 is not populated. Both CNE.3 and CNE.14 may be populated.

CNE-15: Value Set OID (ST)

Definition: This component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CNE.1 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used.

A value set may or need not be present irrespective of other fields.

CNE-16: Value Set Version ID (DTM)

Definition: This component carries the version for the value set identified by CNE.15. The version is a date. The date is the date/time that the value set being used was published.

Value set version ID is required if CNE.15 is populated.

CNE-17: Alternate Coding System OID (ST)

Definition: This component contains the ISO Object Identifier (OID) for the coding system or value set named in CNE.6. Analogous to CNE.14 OID for Coding System.

The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used.

This component is required when CNE.4 is populated and CNE.6 is not populated. Both CNE.6 and CNE.17 may be populated.

CNE-18: Alternate Value Set OID (ST)

Definition: This component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CNE.4 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used.

A value set may or need not be present irrespective of other fields.

CNE-19: Alternate Value Set Version ID (DTM)

Definition: This component carries the version for the value set identified by CNE.18. The version is a date. The date is the date/time that the value set being used was published.

Value set version ID is required if CNE.18 is populated.

CNE-20: Second Alternate Coding System OID (ST)

Definition: This component contains the ISO Object Identifier (OID) from which the value in CNE.12 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined numbers, the OID registered in the HL7 OID registry should be used.

This component is required when CNE.4 is populated and neither CNE.6 nor CNE.18 is populated. In short either the CNE.6 or the CNE.14 or CNE.17 must be populated when CNE.4 is populated.

CNE-21: Second Alternate Value Set OID (ST)

Definition: This component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CNE.10 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields.

CNE-22: Second Alternate Value Set Version ID (DTM)

Definition: This component carries the version for the value set identified by CNE.21. The version is a date. The date is the date/time that the value set being used was published.

Value set version ID is required if CNE.21 is populated.

CNN-1: ID Number (ST)

Coded ID according to a user-defined table. If the first component is present, either CNN.8 or CNN.9, or both CNN.10 and CNN.11, must be valued.

CNN-2: Family Name (ST)

This component contains the person's family name in a string format.

CNN-3: Given Name (ST)

Used to specify a first name.

CNN-4: Second and Further Given Names or Initials Thereof (ST)

CNN-5: Suffix (ST)

Used to specify a name suffix (e.g., Jr. or III).

CNN-6: Prefix (ST)

Used to specify a name prefix (e.g., Dr.).

CNN-7: Degree (IS)

Used to specify an educational degree (e.g., MD). Refer to User-defined Table 0360 – Degree/license/certificate in Chapter 2C, Code Tables, for suggested values.

CNN-8: Source Table (IS)

Refer to User-defined Table 0297 - CN ID source in Chapter 2C, Code Tables, for suggested values. Used to delineate the first component. If component 1 is valued, either CNN.8 or CNN.9, or both CNN.10 and CNN.11, must be valued.

CNN-9: Assigning Authority - Namespace ID (IS)

See section, 2.A.14.4, "Assigning Authority (HD)" for definition. Refer to User-defined Table 0363 – Assigning Authority in Chapter 2C, Code Tables, for suggested values. Assigning Authority is normally expressed as an HD data type, but has been flattened to 3 components here (CNN.9, CNN.10 and CNN.11) in this data type so that it may be fully expressed. Also note that if additional components are added to the HD data type in the future, adjustment will need to be made accordingly to this data type.

If component 1 is valued, either CNN.8 or CNN.9, or both CNN.10 and CNN.11, must be valued.

CNN-10: Assigning Authority - Universal ID (ST)

See section, 2.A.14.4, "Assigning Authority (HD)" for definition.

If CNN.11 is valued, this component must be valued. If component 1 is valued, either CNN.8 or CNN.9, or both CNN.10 and CNN.11, must be valued.

CNN-11: Assigning Authority - Universal ID Type (ID)

See section, 2.A.14.4, "Assigning Authority (HD)" for definition. If this component is a known UID refer to HL7 Table 0301 - Universal ID type in Chapter 2C, Code Tables, for valid values.

If CNN.10 is valued, this component must be valued. If component 1 is valued, either CNN.8 or CNN.9, or both CNN.10 and CNN.11, must be valued.

CP-1: Price (MO)

Definition: The only required component; usually containing a decimal point.

CP-2: Price Type (ID)

Definition: A coded value, data type ID. Refer to HL7 Table 0205 – Price Type in Chapter 2C, Code Tables, for valid values.

CP-3: From Value (NM)

Definition: The number specifying the lower limit or boundary of the range. This component, together with the CP.4 component, specifies the "price range". The range can be defined as either time or quantity. For example, the range can indicate that the first 10 minutes of the procedure has one price. Another repetition of the data type can use the range to specify that the following 10 to 60 minutes of the procedure is charged at another price per; a final repetition can specify that the final 60 to N minutes of the procedure at a third price.

CP-4: To Value (NM)

Definition: The number specifying the high limit or boundary of the range.

CP-5: Range Units (CWE)

Definition: This component describes the units associated with the range, e.g., seconds, minutes, hours, days, quantity (i.e., count). As of v2.7 the Externally-defined Unified Code for Units of Measure (UCUM) case sensitive code is the required code for units of measure. Refer to the externally-defined table "Unified Code for Units of Measure" (UCUM) [http://aurora.rg.iupui.edu/UCUM] for valid values. Local codes may be transmitted in addition to UCUM codes.

This component is required if CP.3 From Value and/or CP.4 To Value are present.

CP-6: Range Type (ID)

Definition: Refer to HL7 Table 0298 - CP Range Type for valid values.

CQ-1: Quantity (NM)

Definition: This component specifies the numeric quantity or amount of an entity.

CQ-2: Units (CWE)

Definition: This component species the units in which the quantity is expressed. As of v2.7 the externally-defined Unified Code for Units of Measure (UCUM) case sensitive code is the required code for units of measure. Refer to the external table "Unified Code for Units of Measure" (UCUM) [http://aurora.rg.iupui.edu/UCUM] for valid values. Local codes may be transmitted in addition to UCUM codes.

Refer to user-defined Table 0794 - Units in Chaper 2C, Code Tables, for valid values.

CSU-1: Channel Sensitivity (NM)

Definition: This component transmits the nominal value that corresponds to one unit in the waveform data, that is, the effective resolution of the least significant bit of the ADC, and the polarity of the channel.

CSU-2: Unit of Measure Identifier (ST)

Definition: The unit designation for the channel sensitivity. This field is required if the unit of measure description is not present.

CSU-3: Unit of Measure Description (ST)

Definition: The full text name of the unit of measure identifier. This field is required if the unit of measure identifier is not present.

CSU-4: Unit of Measure Coding System (ID)

Definition: Specifies the designated system of units. Refer to HL7 Table 0396 – Coding System in Chapter 2C, Code Tables, for valid values. This component is required if the CSU.2 Unit of Measure Identifier is present.

Both CSU.4 and CSU.15 may be populated. Receivers should not identify a code based on its position within the tuples (Identifier, Alternate Identifier, or Second Alternate Identifier) or position within a repeating field. Instead, the receiver should always examine the codingSystem as specified in CSU.4 and/or CSU.15, the "Coding System" component or the "Coding System OID" for the tuple.

CSU-5: Alternate Unit of Measure Identifier (ST)

Definition: A sequence of characters that uniquely identifies an alternate units designation for the channel sensitivity. Analogous to CSU.2 Unit of Measure Identifier.

Usage Notes: The Alternate Identifier is used to represent the local or user seen code as described. If present, it obeys the same rules of use and interpretation as described for component 1. If both are present, the identifiers in component 4 and component 1 should have exactly the same meaning, i.e., they should be exact synonyms.

CSU-6: Alternate Unit of Measure Description (ST)

Definition: The full text name of the alternate unit of measure identifier. Analogous to CSU.3 Unit of Measure Description.

CSU-7: Alternate Unit of Measure Coding System (ID)

Definition: Specifies the coding system for the alternate unit of measure. Refer to HL7 Table 0396 – Coding System in Chapter 2C, section "Coding System Table" for valid values. Analogous to CSU.4 Unit of Measure Coding System.

This field is required if the CSU.5 Alternate Unit of Measure Identifier is present. Both CSU.7 and CSU.18 may be populated. Receivers should not identify a code based on its position within the tuples (Identifier, Alternate Identifier, or Second Alternate Identifier) or position within a repeating field. Instead, the receiver should always examine the codingSystem as specified in CSU.7 and/or CSU.18, the "Coding System" component or the "Coding System OID" for the tuple.

CSU-8: Unit of Measure Coding System Version ID (ST)

Definition: This component carries the version for the coding system identified by components 2-4. If CSU.4 is populated with a value other than HL7nnnn or is of table type user-defined, version ID must be valued with an actual version ID. If CSU.4 is populated with a value of HL7nnnn and nnnn is of table type HL7, version ID may have an actual value or it may be absent. If version ID is absent, it will be interpreted to have the same value as the HL7 version number in the message header.

CSU-9: Alternate Unit of Measure Coding System Version ID (ST)

Definition: This component carries the version for the coding system identified by components 5-7. Analogous to CSU.8 Unit of Measure Coding System Version ID.

CSU-10: Original Text (ST)

Definition: The text as seen and/or selected by the user who entered the data. Original text can be used in a structured user interface to capture what the user saw as a representation of the code on the data input screen, or in a situation where the user dictates or directly enters text, it is the text entered or uttered by the user. In a situation where the code is assigned sometime after the text was entered, original text is the text or phrase used as the basis for assigning the code.

CSU-11: Second Alternate Unit of Measure Identifier (ST)

Definition: A sequence of characters that uniquely identifies a second alternate units designation for the channel sensitivity. Analogous to CSU.2 Unit of Measure Identifier.

CSU-12: Second Alternate Unit of Measure Text (ST)

Definition: The descriptive or textual name of the second alternate identifier. Analogous to CSU.3 Unit of Measure Description.

CSU-13: Name of Second Alternate Unit of Measure Coding System (ID)

Definition: Specifies the coding system for the second alternate unit of measure. Analogous to CSU.4 Unit of Measure Coding System. Refer to HL7 Table 0396 – Coding System in Chapter 2C, Code Tables, for valid values.

This component is required when CSU.11 is populated. Both CSU.13 and CSU.21 may be populated. Receivers should not identify a code based on its position within the tuples (Identifier, Alternate Identifier, or Second Alternate Identifier) or position within a repeating field. Instead, the receiver should always examine the codingSystem as specified in CSU.13 and/or CSU.21 the Coding System component or the Coding System OID for the tuple.

CSU-14: Second Alternate Unit of Measure Coding System Version ID (ST)

Definition: This component carries the version for the coding system identified by components 11-13. Analogous to CSU.8 Unit of Measure Coding System Version ID.

CSU-15: Unit of Measure Coding System OID (ST)

Definition: This component contains the ISO Object Identifier (OID) for the coding system or value set named in CSU.4. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used.

This component is required when CSU.2 is populated and CSU.4 is not populated. Both CSU.4 and CSU.15 may be populated.

CSU-16: Unit of Measure Value Set OID (ST)

Definition: This component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CSU.2 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used.

A value set may or need not be present irrespective of other fields.

CSU-17: Unit of Measure Value Set Version ID (DTM)

Definition: This component carries the version for the value set identified by CSU.16. The version is a date. The date is the date/time that the value set being used was published.

Value set version ID is required if CSU.16 is populated.

CSU-18: Alternate Unit of Measure Coding System OID (ST)

Definition: This component contains the ISO Object Identifier (OID) for the coding system or value set named in CSU.7. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used.

This component is required when CSU.5 is populated and CSU.7 is not populated. Both CSU.7 and CSU.18 may be populated.

CSU-19: Alternate Unit of Measure Value Set OID (ST)

Definition: This component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CSU.5 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used.

A value set may or need not be present irrespective of other fields. .

CSU-20: Alternate Unit of Measure Value Set Version ID (DTM)

Definition: This component carries the version for the value set identified by CSU.19. The version is a date. The date is the date/time that the value set being used was published.

Value set version ID is required if CSU.19 is populated.

CSU-21: Alternate Unit of Measure Coding System OID (ST)

Definition: This component contains the ISO Object Identifier (OID) for the coding system or value set named in CSU.13. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used.

This component is required when CSU.11 is populated and CSU.13 is not populated. Both CSU.13 and CSU.21 may be populated.

CSU-22: Alternate Unit of Measure Value Set OID (ST)

Definition: This component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CSU.11 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used.

A value set may or need not be present irrespective of other fields.

CSU-23: Alternate Unit of Measure Value Set Version ID (ST)

Definition: This component carries the version for the value set identified by CSU.22. The version is a date. The date is the date/time that the value set being used was published.

Value set version ID is required if CSU.22 is populated.

CWE-1: Identifier (ST)

Definition: The first component contains the sequence of characters (the code) that uniquely identifies the item being referenced by the CWE.2. Different coding schemes will have different elements here.

In the context of “Data Missing”, described above in the Usage Note, refer to HL7 Table 0353 – CWE Statuses for valid values.

HL7 Table 0353 - CWE statuses

Refer to section 2.5.5.5 in Chapter 2, Control, for some discussion on the length of this component.

CWE-2: Text (ST)

Definition: The second component contains the descriptive or textual name of the identifier, e.g., "myocardial infarction" or "X-ray impression".

CWE-3: Name of Coding System (ID)

Definition: The third component contains the code for the name of the coding system from which the value in CWE.1 is obtained. Each coding system is assigned a unique identifier. As of v2.7 this component is required when CWE.1 is populated and CWE.14 is not populated. Both CWE.3 and CWE.14 may be populated. Receivers should not identify a code based on its position within the tuples (Identifier, Alternate Identifier, or Second Alternate Identifier) or position within a repeating field. Instead, the receiver should always examine the codingSystem as specified in CWE.3 and/or CWE.14, the "Coding System" component or the "Coding System OID" for the tuple.

Refer to HL7 Table 0396 – Coding System in Chapter 2C, section "Coding System Table" for valid values.

Refer to section 2.A.8.3, "Name of Coding System (ID)" for a discussion of coding system conventions.

CWE-4: Alternate Identifier (ST)

Definition: A sequence of characters that uniquely identifies an alternate code. Analogous to CWE.1- Identifier.

Usage Notes: The Alternate Identifier is used to represent the local or user seen code as described. If present, it obeys the same rules of use and interpretation as described for component 1. If both are present, the identifiers in component 4 and component 1 should have exactly the same meaning, i.e., they should be exact synonyms.

CWE-5: Alternate Text (ST)

Definition: The descriptive or textual name of the alternate identifier. Analogous to CWE.2 - Text. See usage note in section introduction.

CWE-6: Name of Alternate Coding System (ID)

Definition: Identifies the coding scheme being used in the alternate identifier component. Analogous to CWE.3 - Name of Coding System. See usage note in section introduction.

As of v2.7 this component is required when CWE.4 is populated and CWE.17 is not populated. Both CWE.6 and CWE.17 may be populated. Receivers should not identify a code based on its position within the tuples (Identifier, Alternate Identifier, or Second Alternate Identifier) or position within a repeating field. Instead, the receiver should always examine the coding System as specified in CWE.6 and/or CWE.17, the "Coding System" component or the "Coding System OID", for the tuple.

CWE-7: Coding System Version ID (ST)

Definition: This component carries the version for the coding system identified by components 1-3. If CWE.3 is populated with a value other than HL7nnnn or is of table type user-defined, version ID must be valued with an actual version ID. If CWE.3 is populated with a value of HL7nnnn and nnnn is of table type HL7, version ID may have an actual value or it may be absent. If version ID is absent, it will be interpreted to have the same value as the HL7 version number in the message header.

CWE-8: Alternate Coding System Version ID (ST)

Definition: This component carries the version for the coding system identified by components 4-6. Analogous To CWE.7 - Coding System Version ID.

CWE-9: Original Text (ST)

Definition: The text as seen and/or selected by the user who entered the data. Original text can be used in a structured user interface to capture what the user saw as a representation of the code on the data input screen, or in a situation where the user dictates or directly enters text, it is the text entered or uttered by the user. In a situation where the code is assigned sometime after the text was entered, original text is the text or phrase used as the basis for assigning the code.

CWE-10: Second Alternate Identifier (ST)

Definition: A sequence of characters that uniquely identifies a second alternate code. Analogous to CWE.1- Identifier.

CWE-11: Second Alternate Text (ST)

Definition: The descriptive or textual name of the alternate identifier. Analogous to CWE.2 - Text. See usage note in section introduction.

CWE-12: Name of Second Alternate Coding System (ID)

Definition: Identifies the coding scheme being used in the alternate identifier component. Analogous to CWE.3 Name of Coding System. See usage note in section introduction.

As of v2.7 this component is required when CWE.10 is populated and CWE.20 is not populated. Both CWE.6 and CWE.17 may be populated. Receivers should not identify a code based on its position within the tuples (Identifier, Alternate Identifier, or Second Alternate Identifier) or position within a repeating field. Instead, the receiver should always examine the coding System as specified in CWE.12 and/or CWE.20, the "Coding System" component or the "Coding System OID", for the tuple.

CWE-13: Second Alternate Coding System Version ID (ST)

Definition: This component carries the version for the coding system identified by components 10-12. Analogous to CWE.7 - Coding System Version ID.

CWE-14: Coding System OID (ST)

Definition: This component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.3. The value for this component for an HL7 or User Defined table SHALL be the value published for the code system OID for the table in Chapter 2C Code Tables. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used.

This component is required when CWE.1 is populated and CWE.3 is not populated. Both CWE.3 and CWE.14 may be populated.

CWE-15: Value Set OID (ST)

Definition: This component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.1 is obtained. The value for this component is identified for each of the HL7 Tables that have values published in Chapter 2C Code Tables. For externally defined value sets, the OID registered in the HL7 OID registry and/or published in an HL7 balloted Implementation Guide SHALL be used.

A value set may or need not be present irrespective of other fields.

CWE-16: Value Set Version ID (DTM)

Definition: This component carries the version for the value set identified by CWE.15. The version is a date. The date is the date/time that the value set being used was published.

Value set version ID is required if CWE.15 is populated.

CWE-17: Alternate Coding System OID (ST)

Definition: This component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.6. Analogous to CWE.14 Coding System OID.

The value for this component for an HL7 or User Defined table SHALL be the value published for the code system OID for the table in Chapter 2C Code Tables. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used.

This component is required when CWE.4 is populated and CWE.6 is not populated. Both CWE.6 and CWE.17 may be populated.

CWE-18: Alternate Value Set OID (ST)

Definition: This component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.4 is obtained. The value for this component is identified for each of the HL7 Tables that have values published in Chapter 2C Code Tables. For externally defined value sets, the OID registered in the HL7 OID registry and/or published in an HL7 balloted Implementation Guide SHALL be used. A value set may or need not be present irrespective of other fields.

CWE-19: Alternate Value Set Version ID (DTM)

Definition: This component carries the version for the value set identified by CWE.18. The version is a date. The date is the date/time that the value set being used was published.

Value set version ID is required if CWE.18 is populated.

CWE-20: Second Alternate Coding System OID (ST)

Definition: This component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.12. Analogous to CWE.14 - Coding System OID.

The value for this component for an HL7 or User Defined table SHALL be the value published for the code system OID for the table in Chapter 2C Code Tables. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used.

This component is required when CWE.10 is populated and CWE.12 is not populated. Both CWE.12 and CWE.20 may be populated.

CWE-21: Second Alternate Value Set OID (ST)

Definition: This component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.10 is obtained. The value for this component is identified for each of the HL7 Tables that have values published in Chapter 2C Code Tables. For externally defined value sets, the OID registered in the HL7 OID registry and/or published in an HL7 balloted Implementation Guide SHALL be used.

A value set may or need not be present irrespective of other fields

CWE-22: Second Alternate Value Set Version ID (DTM)

Definition: This component carries the version for the value set identified by CWE.21. The version is a date. The date is the date/time that the value set being used was published.

Value set version ID is required if CWE.21 is populated.

CX-1: ID Number (ST)

Definition: The value of the identifier itself.

CX-2: Identifier Check Digit (ST)

Definition: A digit, or digits, exclusive of the identifier in CX.1, calculated by applying an algorithm to all or some of the digits in the number, which may be used to test validity of the non-check-digit identifier.

CX-3: Check Digit Scheme (ID)

Definition: Contains the code identifying the check digit scheme employed.

Refer to HL7 Table 0061 - Check Digit Scheme for valid values.

The algorithm for calculating a Mod10 check digit is as follows:

Assume you have an identifier - 12345. Take the odd digit positions, counting from the right, i.e., 531, multiply this number by 2 to get 1062. Take the even digit positions, starting from the right (i.e., 42), prepend these to the 1062 to get 421062. Add all of these six digits together to get 15. Subtract this number from the next highest multiple of 10, i.e., 20 - 15 to get 5. The Mod10 check digit is 5. The Mod10 check digit for 401 is 0; for 9999, it’s 4; for 99999999, it’s 8.

The algorithm for calculating a Mod11 check digit is as follows:

Terms

Calculation

Example:

If the number is 1234567, then the mod 11 check digit = 4

The calculations are:

M = (7*2)+(6*3)+(5*4)+(4*5)+(3*6)+(2*7)+(1*2)

= 14 + 18 + 20 + 20 + 18 + 14 + 2

= 106

c1 = 106 mod 11

= 7

c = (11-c1) mod 10

= 4 mod 10

= 4

Other variants of these check digit algorithms exist and may be used by local bilateral site agreement.

CX-4: Assigning Authority (HD)

The assigning authority is a unique name of the system (or organization or agency or department) that creates the data. As of v2.7, CX.4 Assigning Authority is required if neither CX.9 nor CX.10 are populated. Best practice is to always send an OID in the Assigning Authority component

Refer to User-defined Table 0363 - Assigning Authority for suggested values.

The reader is referred to the CX.9 and the CX.10 if there is a need to transmit values with semantic meaning for an assigning jurisdiction or assigning department or agency in addition to, or instead of, an assigning authority. However, all 3 components may be valued. If, in so doing, it is discovered that the values in CX.9 and/or CX.10 conflict with CX.4, the user would look to the Message Profile or other implementation agreement for a statement as to which takes precedence.

CX-5: Identifier Type Code (ID)

A code corresponding to the type of identifier. As of v2.7, CX.5 Identifier Type Code is required. Refer to HL7 Table 0203 – Identifier Type for suggested values.

CX-6: Assigning Facility (HD)

Definition: The place or location identifier where the identifier was first assigned to the patient. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems.

CX-7: Effective Date (DT)

Definition: The first date, if known, on which the identifier is valid and active.

CX-8: Expiration Date (DT)

Definition: The last date, if known, on which the identifier is valid and active.

CX-9: Assigning Jurisdiction (CWE)

Definition: The geo-political body that assigned the identifier in component 1. As of v2.7, Assigning Jurisdiction is required if neither CX.4 nor CX.10 are populated.

• Refer to HL7 Table 0399 – Country Code for valid values if the administrative unit under whose jurisdiction the identifier was issued is a country.

• Refer to User-Defined Table 0347 – State/Province for suggested values if the administrative unit under whose jurisdiction the identifier was issued is a state or province. This table is country specific. In the US, postal codes may be used.

• Refer to User-defined Table –0289 County/Parish for suggested values if the administrative unit under whose jurisdiction the identifier was issued is a county or parish.

The reader is referred to the CX.4 if there is a need to transmit this information as an OID.

CX-10: Assigning Agency or Department (CWE)

Definition: The agency or department that assigned the identifier in component 1. As of v2.7, Assigning Agency or Department is required if neither CX.4 nor CX.9 are populated.

Refer to User-defined Table 0530 – Organizations, agency, department for suggested values if the administrative unit under whose jurisdiction the identifier was issued is an organization, agency or department. This is populated with site-specific assigning authorities. It also should contain national or international codes when CX.5 Identifier Type Code may be assigned by more than one authority within a governmental or organizational unit. For example, a federal government may have 2 departments that assign a military identifier, its Veterans Affairs department and its Department of Defense. It is not recommended to include values for entities such as Social Security Administration (SSA), Immigration and Naturalization Service (INS), Center for Medicare and Medicaid Services (CMS) because they are included in the identifier type table. In these cases the name of the country plus the identifier type yields the correct interpretation of the identifier in component 1. Likewise, entries like department of motor vehicles (DMV) and licensing boards are not recommended for inclusion because the combination of state and identifier type yields the correct interpretation of the identifier in component 1. This approach is not to be confused with the detailed information provided in the Chapter 15 segments that have provision for specifying the precise granting body and issuing body information needed in personnel management messages.

Example 1: <Identifier> plus <Visa> yields a unique identifier.

Example 2: <identifier> plus <state> plus <DLN> yields a unique driver’s license number.

Example 3: <identifier> plus <country> plus <INS> yields a unique immigration number.

The reader is referred to the CX.4, if there is a need to transmit this information as an OID.

CX-11: Security Check (ST)

Definition: This component is used to communicate a version code that may be assigned to the value given in CX.1 ID.

CX-12: Security Check Scheme (ID)

Definition: This component is used to transmit information intended to validate the veracity of the supplied identifier or the presenter of the identifier. For example, this component may be used to ensure that the presenter of a credit card is an authorized user of that card.

Refer to HL7 Table 0904 - Security Check Scheme for valid values.

DDI-1: Delay Days (NM)

Definition: The number of days after which the daily deductible begins.

DDI-2: Monetary Amount (MO)

Definition: The monetary amount of the deductible.

DDI-3: Number of Days (NM)

Definition: The number of days to apply the deductible. If this component is not populated, it means that the number of days is indefinite.

DIN-1: Date (DTM)

Definition: Specifies the date when a staff member became active or inactive.

DIN-2: Institution Name (CWE)

Definition: Specifies the institution where a staff member is or was active. Refer to User-Defined Table 0531 - Institution for suggested values.

DLD-1: Discharge to Location (CWE)

Definition: This component specifies the healthcare facility to which the patient was discharged. Refer to User-defined Table 0113 - Discharged to Location for suggested values.

DLD-2: Effective Date (DTM)

Definition: Specifies the date on which the patient was discharged to a healthcare facility.

DLN-1: Driver's License Number (ST)

Definition: This field contains the driver’s license number.

DLN-2: Issuing State, Province, Country (CWE)

Definition: Issuing authority for driver’s license. For state or province, refer to official postal codes for that country; for country, refer to ISO 3166 for codes. The ISO 3166 table has three separate forms of the country code: HL7 specifies that the 3-character (alphabetic) form be used for the country code. User-defined Table 0333 - Driver’s License Issuing Authority is used as the HL7 identifier for the user-defined table of values for this component.

DLN-3: Expiration Date (DT)

Definition: Expiration date (DT) for driver’s license.

DLT-1: Normal Range (NR)

Definition: Specifies the normal interval of the reference data.

DLT-2: Numeric Threshold (NM)

Definition: The numeric threshold of the change that is detected.

For example the threshold may be set to 10.

DLT-3: Change Computation (ID)

Definition: Specifies if the change is computed as a percent change or as an absolute change. Refer to HL7 Table 0523 - Computation Type for valid values.

DLT-4: Days Retained (NM)

Definition: The length of time in days that the value is retained for computing delta checks.

DR-1: Range Start Date/Time (DTM)

Definition: The first component contains the earliest date/time (time stamp) in the specified range.

DR-2: Range End Date/Time (DTM)

The second component contains the latest date/time in the specified range.

DTN-1: Day Type (CWE)

Definition: Specifies whether the days are denied, pending, or approved.

Refer to User-defined Table 0149 - Day Type for suggested values.

DTN-2: Number of Days (NM)

Definition: Specifies the number of days for which the certification is valid.

ED-1: Source Application (HD)

Definition: A unique name that identifies the system which was the source of the data. Identical format and restrictions as in reference pointer (see Section 2.A.65.2, "Application ID (HD)").

ED-2: Type of Data (ID)

Definition: Identical to “type of data” component in the reference pointer (RP) data type. See Section 2.A.65.3, "Type of Data (ID)".

Refer to Imported Table 0834 – MIME Types for valid values.

ED-3: Data Subtype (ID)

Definition: Identical to “subtype” component in the reference pointer (RP) data type. See Section 2.A.65.4, "Subtype (ID)".

Refer to External Table 0291 - Subtype of Referenced Data for valid values.

ED-4: Encoding (ID)

Definition: The type of encoding used to represent successive octets of binary data as displayable ASCII characters. Refer to HL7 Table 0299 - Encoding for valid values.

ED-5: Data (TX)

Definition: Displayable ASCII characters which constitute the data to be sent from source application to destination application. The characters are limited to the legal characters of the ST data type, as defined in Section 2.A.75, "ST - string data," and, if encoded binary, are encoded according to the method of Section 2.A.24.2, "Type of Data (ID)".

If the encoding component (see Section 2.A.24.4, "Encoding (ID)") = "A" (none), then the data component must be scanned before transmission for HL7 delimiter characters, and any found must be escaped by using the HL7 escape sequences defined in Section 2.7 – "Use of escape sequences in text fields." On the receiving application, the data field must be de-escaped after being parsed.

If the encoding component ED.4 does not equal "A", then, after encoding, the (encoded) data must be scanned for HL7 delimiter characters, and any found must be escaped by using the HL7 escape sequences. Only then can the component be added to the HL7 segment/message. On the receiving application, the data field must be de-escaped after being parsed out of the message before being decoded. This can be expressed as "encode", "escape", "parse", "de-escape" or "decode".

EI-1: Entity Identifier (ST)

Definition: The first component, <entity identifier>, is usually defined to be unique within the series of identifiers created by the <assigning authority>, defined by a hierarchic designator, represented by components 2 through 4. See Section 2.A.33, "HD - hierarchic designator".

EI-2: Namespace ID (IS)

Definition: See Section 2.A.33.1, "Namespace ID (IS)" for definition. The component intentionally remains associated with the IS data type in v 2.7.

The assigning authority is a unique identifier of the system (or organization or agency or department) that creates the data. Refer to User-defined Table 0363 – Assigning Authority for suggested values.

EI-3: Universal ID (ST)

Definition: See Section 2.A.33.2, "Universal ID (ST)" for definition.

EI-4: Universal ID Type (ID)

Definition: Refer to HL7 Table 0301 - Universal ID Type for valid values. See Section 2.A.33.3, "Universal ID Type (ID)," for definition.

EIP-1: Placer Assigned Identifier (EI)

Definition: Specifies an identifier assigned to an entity by the placer system.

For example, the component might be used to convey the following:

1. placer order number of the parent order.

2. the specimen identifier as assigned by the placer.

3. a location identifier assigned (or used by) the placer.

EIP-2: Filler Assigned Identifier (EI)

Definition: Specifies an identifier assigned to an entity by the filler system.

For example, the component might convey the following:

1. filler order number of the parent order.

2. the specimen identifier as assigned by the filler.

3. a location identifier assigned (or used by) the filler.

ERL-1: Segment ID (ST)

Definition: Specifies the 3-letter name for the segment.

ERL-2: Segment Sequence (SI)

Definition: Identifies the segment occurrence within the message. The first occurrence of a segment is assigned the number of 1.

ERL-3: Field Position (SI)

Definition: Identifies the number of the field within the segment. The first field is assigned a number of 1. Field number should not be specified when referring to the entire segment. This field is conditionally required, when Component Number (ERL-5) is populated..

ERL-4: Field Repetition (SI)

Definition: Identifies the repetition number of the field. The first repetition is counted as 1. If a Field Position is specified, but Field Repetition is not, Field Repetition should be assumed to be 1. If Field Position is not specified, Field Repetition should not be specified.

ERL-5: Component Number (SI)

Definition: Identifies the number of the component within the field. The first component is assigned a number of 1. Component number should not be specified when referring to the entire field. This field is conditionally required, when Sub-Component Number (ERL-6) is populated.

ERL-6: Sub-Component Number (SI)

Definition: Identifies the number of the sub-component within the component. The first sub-component is assigned a number of 1. Sub-component number should not be specified when referring to the entire component.

FC-1: Financial Class Code (CWE)

Definition: This component contains the financial class assigned to a person. User-defined Table 0064 - Financial Class is used as the HL7 identifier for the user-defined table of values for this component.

FC-2: Effective Date (DTM)

Definition: This component contains the effective date/time of the person’s assignment to the financial class specified in the first component.

FN-1: Surname (ST)

Definition: The atomic element of the person's family name. In most Western usage, this is the person's last name.

FN-2: Own Surname Prefix (ST)

Definition: Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN).

FN-3: Own Surname (ST)

Definition: The portion of the surname (in most Western usage, the last name) that is derived from the person's own surname, as distinguished from any portion that is derived from the surname of the person's partner or spouse. This component is optional.

If the person's surname has legally changed to become (or incorporate) the surname of the person's partner or spouse, this is the person's surname immediately prior to such change. Often this is the person's "maiden name".

FN-4: Surname Prefix from Partner/Spouse (ST)

Definition: Internationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the “van” in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN).

FN-5: Surname from Partner/Spouse (ST)

Definition: The portion of the person's surname (in most Western usage, the last name) that is derived from the surname of the person's partner or spouse, as distinguished from the part derived from the person's own surname. This component is optional.

If no portion of the person's surname is derived from the surname of the person's partner or spouse, this component is not valued. Otherwise, if the surname of the partner or spouse has legally changed to become (or incorporate) the person's surname, this is the surname of the partner or spouse immediately prior to such change.

HD-1: Namespace ID (IS)

Definition: The local coded item for the entity. The component intentionally remains associated with the IS data type in v 2.7.

User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component.

HD-2: Universal ID (ST)

Definition: The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component).

HD-3: Universal ID Type (ID)

Definition: The third component governs the interpretation of the second component of the HD. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type.

ICD-1: Certification Patient Type (CWE)

Definition: Specifies the category or type of patient for which this certification is requested. Refer to User-defined Table 0150 - Certification patient type for suggested values.

ICD-2: Certification Required (ID)

Definition: Specifies whether or not a certification is required. Refer to HL7 Table 0136 - Yes/no Indicator for valid values.

ICD-3: Date/Time Certification Required (DTM)

Definition: The date/time by which the certification must be obtained.

JCC-1: Job Code (CWE)

Definition: This component contains the person’s job code. User-defined Table 0327 - Job Code is used as the HL7 identifier for the user-defined table of values for this component.

JCC-2: Job Class (CWE)

Definition: This component contains the person’s employee classification. Refer to User-defined Table 0328 - Employee Classification for suggested values.

JCC-3: Job Description Text (TX)

Definition: This component contains the text of the job description. This will accommodate systems where job descriptions are not codified.

MA-1: Sample Y From Channel 1 (NM)

MA-2: Sample Y From Channel 2 (NM)

MA-3: Sample Y From Channel 3 (NM)

MA-4: Sample Y From Channel 4 (NM)

MO-1: Quantity (NM)

Definition: The first component is a quantity.

MO-2: Denomination (ID)

Definition: The second component is the denomination in which the quantity is expressed. The values for the denomination component are the three-character codes specified in ISO-4217. See Externally-defined Table 0913 – Monetary Denomination Code.

If the denomination is not specified, "MSH-17-country code", in Chapter 2, section 2.14.9.17, is used to determine the default. Example,

|99.50^USD|

where USD is the ISO 4217 code for the U.S. American dollar.

MOC-1: Monetary Amount (MO)

Definition: The amount and denomination of money associated with the charge code.

MOC-2: Charge Code (CWE)

Definition: The code identifying the charge to the ordering entity for the services performed.

MOP-1: Money or Percentage Indicator (ID)

Definition: Specifies whether the amount is currency or a percentage.

Refer to HL7 Table 0148 – Money or Percentage Indicator for valid values.

MOP-2: Money or Percentage Quantity (NM)

Definition: Specifies the currency or percentage quantity.

MOP-3: Monetary Denomination (ID)

Definition: the denomination in which the quantity is expressed where the amount is currency. The values for the denomination component are the three-character codes specified in ISO-4217. See Externally-defined Table 0913 – Monetary Denomination Code.

If the denomination is not specified, the context of the message or MSH-17 Country Code, in Chapter 2, section 2.14.9.17, is used to determine the default.

MSG-1: Message Code (ID)

Definition: Specifies the message type code. Refer to HL7 Table 0076– Message Type for valid values.

This table contains values such as ACK, ADT, ORM, ORU etc.

See Chapter 2, "Control", section 2.5.1, "Messages" for further discussion.

MSG-2: Trigger Event (ID)

Definition: Specifies the trigger event code. Refer to HL7 Table 0003– Event Type for valid values.

This table contains values like A01, O01, R01 etc.

See Chapter 2, "Control", section 2.3.1, "Trigger Events" for further discussion.

MSG-3: Message Structure (ID)

Definition: Specifies the abstract message structure code. Refer to HL7 Table 0354 – Message Structure for valid values.

NA-1: Value1 (NM)

NA-2: Value2 (NM)

NA-3: Value3 (NM)

NA-4: Value4 (NM)

NDL-1: Name (CNN)

Definition: This component specifies the name of the person performing a service.

NDL-2: Start Date/Time (DTM)

Definition: This component specifies the starting date and time for when the person is performing the service.

NDL-3: End Date/Time (DTM)

Definition: This component specifies the ending date and time for when the person is performing the service.

NDL-4: Point of Care (IS)

Definition: This component specifies the code for the point where patient care is administered. It is conditional on NDL.9 – Patient Location Type (e.g., nursing unit or department or clinic). After floor, it is the most general patient location designation. Refer to User-defined Table 0302 - Point of care for suggested values.

NDL-5: Room (IS)

Definition: Patient room. After point of care, it is the most general location designation. Refer to User-defined Table 0303 - Room for suggested values.

NDL-6: Bed (IS)

Definition: This component specifies the code for the patient's bed. After room, it is the most general location designation. Refer to User-defined Table 0304 - Bed for suggested values.

NDL-7: Facility (HD)

Definition: This component is subject to site interpretation but generally describes the highest level physical designation of an institution, medical center or enterprise. It is the most general location designation.

NDL-8: Location Status (IS)

Definition: This component specifies the code for the status or availability of the location. For example, it may convey bed status. Refer to User-defined Table 0306 - Location Status for suggested values.

NDL-9: Patient Location Type (IS)

Definition: Location type is the categorization of the location defined by facility, building, floor, point of care, room or bed. Although not a required field, when used, it may be the only populated field. Usually includes values such as nursing unit, department, clinic, SNF, physician’s office. Refer to User-defined Table 0305 - Person Location Type for suggested values.

NDL-10: Building (IS)

Definition: This component specifies the code for the building where the person is located. After facility, it is the most general location designation. Refer to User-defined Table 0307 - Building for suggested values.

NDL-11: Floor (IS)

Definition: This component specifies the code for the floor where the person is located. After building, it is the most general location designation. Refer to User-defined Table 0308 - Floor for suggested values.

NR-1: Low Value (NM)

Definition: The number specifying the lower limit or boundary of the range.

NR-2: High Value (NM)

Definition: The number specifying the high limit or boundary of the range.

OCD-1: Occurrence Code (CNE)

Definition: The NUBC code for the event or occurrence relating to a bill that may affect payer processing.

Refer to HL7-defined Table 0350 – Occurrence Code for valid values.

Values for this component need to come from National Uniform Billing Committee (NUBC). No extensions are allowed.

OCD-2: Occurrence Date (DT)

Definition: The date the event, relating to a bill that may affect payer processing, occurred.

OG-1: Original Sub-Identifier (ST)

Definition: The Original Sub-Identifier component represents the original data type used in OBX-4 to enable backwards compatibility to continue use of the original format to provide OBX segment grouping.

OG-2: Group (NM)

Definition: The Group component indicates the group and its sequence within the OBR segment that the OBX segment is a part of.

OG-3: Sequence (NM)

Definition: The Sequence component indicates the sequence within the group as defined in OG-2.

OG-4: Identifier (ST)

Definition: The Identifier component enables assignment of an identifier to a result component, for example an isolate in a microbiology message. Futher guidance on how to use this field will be found in an Implementation Guide.

OSP-1: Occurrence Span Code (CNE)

Definition: The NUBC code itself that identifies an event that relates to the payment of a claim.

Refer to HL7 Table 0351 – Occurrence Span for valid values. Values for this component need to come from National Uniform Billing Committee (NUBC). No extensions are allowed.

OSP-2: Occurrence Span Start Date (DT)

Definition: The date an event started that relates to the payment of a claim.

OSP-3: Occurrence Span Stop Date (DT)

Definition: The date an event ended that relates to the payment of a claim.

PIP-1: Privilege (CWE)

Definition: Specifies the institutional privilege itself. Refer to User-defined Table 0525 – Privilege for suggested values.

PIP-2: Privilege Class (CWE)

Definition: Specifies the class category of institutional privilege. Refer to User-defined Table 0526 – Privilege Class for suggested values.

PIP-3: Expiration Date (DT)

Definition: Specifies the date the institutional privilege is/was no longer valid.

PIP-4: Activation Date (DT)

Definition: Specifies the date the institutional privilege became/becomes valid.

PIP-5: Facility (EI)

Definition: Specifies the facility in which the institutional privilege is/was valid.

PL-1: Point of Care (HD)

Definition: This component specifies the code for the point where patient care is administered. It is conditional on PL.6 Person Location Type (e.g., nursing unit or department or clinic). After floor, it is the most general patient location designation. Refer to User-defined Table 0302 - Point of Care for suggested values.

PL-2: Room (HD)

Definition: This component specifies the code for the patient's room. After point of care, it is the most general person location designation. Refer to User-defined Table 0303 - Room for suggested values.

PL-3: Bed (HD)

Definition: This component specifies the code for the patient's bed. After room, it is the most general person location designation. Refer to User-defined Table 0304 - Bed for suggested values.

PL-4: Facility (HD)

Definition: This component is subject to site interpretation but generally describes the highest level physical designation of an institution, medical center or enterprise. It is the most general person location designation.

See Section 2.A.33, “HD - hierarchic designator” for discussion of data type.

PL-5: Location Status (IS)

Definition: This component specifies the code for the status or availability of the location. For example, it may convey bed status. Refer to User-defined Table 0306 - Location Status for suggested values.

PL-6: Person Location Type (IS)

Definition: Person location type is the categorization of the person’s location defined by facility, building, floor, point of care, room or bed. Although not a required field, when used, it may be the only populated field. It usually includes values such as nursing unit, department, clinic, SNF, physician’s office. Refer to User-defined Table 0305 - Person location type for suggested values.

PL-7: Building (HD)

Definition: This component specifies the code for the building where the person is located. After facility, it is the most general person location designation. Refer to User-defined Table 0307 - Building for suggested values.

PL-8: Floor (HD)

Definition: This component specifies the code for the floor where the person is located. After building, it is the most general person location designation. Refer to User-defined Table 0308 - Floor for suggested values.

PL-9: Location Description (ST)

Definition: This component describes the location in free text.

PL-10: Comprehensive Location Identifier (EI)

Definition: The unique identifier that represents the physical location as a whole without regard for the individual components. This accommodates sites that may have a different method of defining physical units or who may code at a less granular level. For example, point of care, room, and bed may be 1 indivisible code.

PL-11: Assigning Authority for Location (HD)

Definition: The entity that creates the data for the individual physical location components. If populated, it should be the authority for all components populated. Refer to User-defined Table 0363 – Assigning Authority for suggested values for the first sub-component of the HD component, <namespace ID>.

This component makes it possible for codes to be differentiated when the field in which this data type is used repeats.

PLN-1: ID Number (ST)

Definition: Specifies the license number or other ID number such as UPIN, Medicare and Medicaid number.

PLN-2: Type of ID Number (CWE)

Definition: Specifies the type of number.

Refer to User-defined Table 0338 – Practitioner ID Number Type for suggested values.

PLN-3: State/other Qualifying Information (ST)

Definition: Specifies the state or province in which the license or ID is valid, if relevant, or other qualifying information. It is recommended that state qualifications use the abbreviations from the postal service of the country.

PLN-4: Expiration Date (DT)

Definition: Specifies the date when the license or ID is no longer valid.