HL7 Segment Reference: Encapsulated Data (Wrong Segment). Everything you need to know about HL7. ORU, HL7 Unsolicited Laboratory Observation Message As an alternative SYSTEM also has the capability to send the encapsulated thumbnail image in the . Transmitting Images of Documents in HL7 Attachments .. image is sent, OBX-2 must contain the value ED which stands for encapsulated data.
|Published (Last):||9 August 2012|
|PDF File Size:||7.64 Mb|
|ePub File Size:||11.94 Mb|
|Price:||Free* [*Free Regsitration Required]|
The characters are limited to the legal characters of the ST data type, as defined in Section 2.
PDF Attachment in HL7 Message
Rendering of the original documentation into the format that will be encapsulated, e. Referenced Performed Procedure Step Sequence.
Only a single Item is permitted in this sequence. For example, the Patient ID in an encapsulated CDA document may be that of a different institution, which originated the document, and it may be appropriate for the DICOM attribute value to be different.
If the encoding component ED. A coded description of the Series. Concept Name Code Sequence. A de-identified document may use the value NO. A unique name that identifies the system which was the source of the data.
Content Date2 The date the document content creation was started. MIME Types of subcomponents of the encapsulated document. It contains the identity of the source system, the type of data, the encoding method of the data, and the data itself.
The date the document content creation was started. Description of the conditions under which the Series was performed.
The type of encoding used to represent successive octets of binary data as displayable ASCII characters. Displayable ASCII characters which constitute the data to be sent from source application to destination application.
This data type transmits encapsulated data from a source system to a destination system.
Identical to “type of data” component in the reference pointer RP data type. A sequence that identifies the set of Instances that were used to derive the encapsulated document.
ED – Encapsulated Data (HL7 v)
Indicates whether the Encapsulated Document is Verified. Sequence that contains attributes from the Imaging Service Request. Laterality of the possibly paired body part that is the subject of the encapsulated document. A number that identifies the Series. For example, if you send two PDF files one pathology report and one ED summaryhow will the receiving application know onto which tab of the patient chart the document should flow?
Review these prior blog postings for details:. The complexity of each solution varies wildly based on the vendors involved. This data type is similar to the RP reference pointer data type of Section 2. The second question to answer: Document Class Code Sequence. Equivalent to HL7 v2. Additional classifications of the document, beyond the title represented in Concept Name Code Sequence.
The modality appropriate for the encapsulated document. This can be expressed as “encode”, “escape”, “parse”, “de-escape” or “decode”.
Image Laterality3 Laterality of the possibly paired body part that is the subject of the encapsulated document. One or more items are permitted in this sequence. It is expected that applications will ensure consistency in a manner appropriate to the application. Review these prior blog postings for details: