Template  CNE - Coded with no exceptions

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.

The descriptive or textual name of the identifier, e.g., myocardial infarction or X-ray impression. Its data type is string (ST). 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.

Each coding system is assigned a unique identifier. This component will serve to identify the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. Each system has a unique identifier.

Refer to HL7 Table 0396 in section 2.17.5 for valid values. The table includes ASTM E1238-94, Diagnostic, procedure, observation, drug ID, health outcomes, and other coding systems.

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 Coding system must either be present and have a value from the set of allowed coding systems or if not present it will be interpreted to have the same meaning as if it had been valued with the code meaning "HL7 coding system". Refer to HL7 Table 0396 in section 2.17.5 for valid values.

Analogous to "Identifier" in component 1.

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.

The descriptive or textual name of the alternate identifier. Analogous to "Text" in component 2. See usage notes in section introduction for further description.

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

Identifies the coding scheme being used in the alternate identifier component. Analogous to "Name of Coding System" in component 3. Refer to HL7 Table 0396 in section 2.17.5 for valid values.

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

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

The version ID for the coding system identified by component 6. It belongs conceptually to the group of Alternate components (see note 2.A.6.6) and appears here only for reasons of backward compatibility.

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