HL7 ED Encapsulated Data
HL7 datatype components ED 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 | ED.1 | Source Application | HD | Source Application; Type HD. | |
| 2 | ED.2 | Type of Data | ID | 0191 | Type of Data; Type ID; HL7 table 0191. |
| 3 | ED.3 | Data Subtype | ID | 0291 | Data Subtype; Type ID; HL7 table 0291. |
| 4 | ED.4 | Encoding | ID | 0299 | Encoding; Type ID; HL7 table 0299. |
| 5 | ED.5 | Data | TX | Data; Type TX. |
ED carries encapsulated data such as a document, image, signature, or other payload. It is for payloads that travel inside the message, so the metadata around the data is just as important as the data itself.
In this guide, ED appears in CER.6. 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.
ED-1 to ED-5: 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 ED-2, ED-3, ED-4. Keep those values to the table or value set your implementation guide names, especially when the field is crossing organization boundaries.
- ED-1 Source Application - Source Application. Type HD.
- ED-2 Type of Data - Type of Data. Type ID. Table 0191.
- ED-3 Data Subtype - Data Subtype. Type ID. Table 0291.
- ED-4 Encoding - Encoding. Type ID. Table 0299.
- ED-5 Data - Data. Type TX.
Practical Notes
Text still has to survive HL7 delimiters. If the source value can contain |, ^, ~, &, or a backslash, encode it before putting it into the message. Integration Soup and the HL7 parser helpers include HL7Encode and HL7Decode for that exact kind of cleanup.
In HL7 Soup Web, click a field that uses ED 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.