HL7 CNE Coded with No Exceptions
HL7 datatype components CNE components from HL7 v2.5.1 Hide components
These are the generated components for the version selected at the top of the page. The article stays practical, and this panel follows the chosen HL7 version.
Components
| Pos | Component | Name | Type | Table | Description |
|---|---|---|---|---|---|
| 1 | CNE.1 | Identifier | ST | Identifier; Type ST. | |
| 2 | CNE.2 | Text | ST | Text; Type ST. | |
| 3 | CNE.3 | Name of Coding System | ID | 0396 | Name of Coding System; Type ID; HL7 table 0396. |
| 4 | CNE.4 | Alternate Identifier | ST | Alternate Identifier; Type ST. | |
| 5 | CNE.5 | Alternate Text | ST | Alternate Text; Type ST. | |
| 6 | CNE.6 | Name of Alternate Coding System | ID | 0396 | Name of Alternate Coding System; Type ID; HL7 table 0396. |
| 7 | CNE.7 | Coding System Version ID | ST | Coding System Version ID; Type ST. | |
| 8 | CNE.8 | Alternate Coding System Version ID | ST | Alternate Coding System Version ID; Type ST. | |
| 9 | CNE.9 | Original Text | ST | Original Text; Type ST. |
CNE is the strict coded datatype: coded with no exceptions. Use it when the sender must choose from the allowed table or value set. If the real-world value is outside the table, the mapping needs to be fixed rather than quietly inventing a local code.
In this guide, CNE appears in OCD, OSP, UVC, BPX.11, BPX.12, BPX.6 and related fields. That used-by list is a good reality check: the datatype is only half the story, and the field that uses it tells you the workflow.
The component panel above is expanded by default because most datatype pages are used as quick lookup pages. Start there for the exact HL7 v2.5.1 shape, then use the notes below for the practical gotchas.
CNE-1 to CNE-9: Component Quick Read
The generated component panel above is the formal quick lookup. The short version is below so you can scan the shape without counting carets by eye.
The table-backed components here are CNE-3, CNE-6. Keep those values to the table or value set your implementation guide names, especially when the field is crossing organization boundaries.
- CNE-1 Identifier - Identifier. Type ST.
- CNE-2 Text - Text. Type ST.
- CNE-3 Name of Coding System - Name of Coding System. Type ID. Table 0396.
- CNE-4 Alternate Identifier - Alternate Identifier. Type ST.
- CNE-5 Alternate Text - Alternate Text. Type ST.
- CNE-6 Name of Alternate Coding System - Name of Alternate Coding System. Type ID. Table 0396.
- CNE-7 Coding System Version ID - Coding System Version ID. Type ST.
- CNE-8 Alternate Coding System Version ID - Alternate Coding System Version ID. Type ST.
- CNE-9 Original Text - Original Text. Type ST.
Practical Notes
The common trap is treating CNE as friendly display text. It is a code. The receiving system usually keys off the value and table, so keep the local description, screen label, and mapped code separate in your interface design.
In HL7 Soup Web, click a field that uses CNE and the interpretation view will show which component you are sitting in and where that value lives in the raw message. That is especially handy with compact datatypes because one missing caret can move every value after it.
Official and Reference Notes
For formal reference, compare the generated HL7 v2.5.1 panel above with the HL7 v2.5.1 datatype list and the HL7 Terminology data type code system. Local implementation guides can narrow allowed values, tables, and component usage.