The Demo site for our new HL7 Version 2+ (plus) Standard
visit the hl7 website

Draft Website - For Review Purposes Only

ED - encapsulated data

HL7 Component Table - ED - encapsulated data
Seq# Description Implement Flags Cardinality Length C.LEN Vocabulary Data Type
ED
1 Source Application [0..1]     HD
2 Type of Data SHALL [0..1] [4..11]     0834 ID
3 Data Subtype [0..1]     0291 ID
4 Encoding SHALL [0..1] [1..6]     0299 ID
5 Data [0..1]     TX

Components: <Source Application (HD)> & <Type of Data (ID)> & <Data Subtype (ID)> & <Encoding (ID)> & <Data (TX)>

Subcomponents for Source Application (HD): <Namespace ID (IS)> ^ <Universal ID (ST)> ^ <Universal ID Type (ID)>

Definition: This data type transmits encapsulated data from a source system to a destination system. It contains the identity of the source system, the type of data, the encoding method of the data, and the data itself. This data type is similar to the RP (reference pointer) data type of Section 2.A.65, "RP - reference pointer," except that instead of pointing to the data on another system, it contains the data which is to be sent to that system.

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".