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.

Author: Dora Arashijar
Country: Ethiopia
Language: English (Spanish)
Genre: Spiritual
Published (Last): 14 January 2012
Pages: 155
PDF File Size: 7.94 Mb
ePub File Size: 1.54 Mb
ISBN: 943-1-17712-882-7
Downloads: 9126
Price: Free* [*Free Regsitration Required]
Uploader: Vudobei

The time the document content creation was started. One could distinguish four stages in the creation of the Encapsulated Document Object, identified by the following Attributes:.

A sequence that identifies the set of Instances that were used to derive the encapsulated document. Identical format and restrictions as in reference pointer see Section 2. Latest posts by Dave Shaver see all.


The value shall be unique within a series. No Baseline CID is defined. Displayable ASCII characters which constitute the data to be sent from source application to destination application. Review these prior blog postings for details: One or more Items are permitted in this sequence. Additional classifications of the document, beyond the title represented in Concept Name Code Sequence. The complexity of each solution varies wildly based on the vendors involved.

The date and time that the original generation of the data in the document started. Unique identifier of the Encappsulated.


A de-identified document may use the value NO. A number that identifies this SOP Instance. Note One could enncapsulated four stages in the creation of the Encapsulated Document Object, identified by the following Attributes: A unique name that identifies the system which was the source of the data. Home Data Type ED – encapsulated data. Series Description Code Sequence.

A coded representation of the document title. This can be expressed as “encode”, “escape”, “parse”, “de-escape” or “decode”. Only a single Item is permitted in this sequence. This data type is similar to the RP reference pointer data type of Section 2.

Concept Name Code Sequence. Content Date2 The date the document content creation was started. A number that identifies the Series.

PDF Attachment in HL7 Message

Image Laterality3 Laterality of the possibly paired body part that is the subject of the encapsulated document. Rendering of the original documentation into the format that will be encapsulated, e.

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?

The title of the document. Encapsulated Document Series Module Attributes. Attested to signed by a Verifying Observer or Legal Authenticator named in the document, who is accountable for its content.

Encapulated these prior blog postings for details:. Acquisition DateTime ,A 2 The date and time that the original generation of the data in the document started.


Rather, the focus should be on how the PDF file will be delivered to and from the source and destination application and how the target application will display the document. Zero or one Item shall be included in this sequence.

Description of the Series. The characters are limited to enapsulated legal characters of the ST data type, as defined in Section 2. One or more items are permitted in this sequence. Identical to “type of data” component in the reference encapwulated RP data type. On the receiving application, the data field must be de-escaped after being parsed out of the message before being decoded.

Encapsulated Document Module Attributes. How will the source application provide the PDF file and how will the destination application s receive the data? Dave has more than 20 years experience in enxapsulated, consulting, and software development.

R right L left U unpaired B both left and right. Indicates whether or not the encapsulated document contains sufficient burned in annotation to identify the patient and date the data was acquired.

Author: admin