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: Disho Zululmaran
Country: Georgia
Language: English (Spanish)
Genre: Life
Published (Last): 9 September 2005
Pages: 17
PDF File Size: 4.50 Mb
ePub File Size: 16.58 Mb
ISBN: 725-7-21882-316-6
Downloads: 61764
Price: Free* [*Free Regsitration Required]
Uploader: Zulushakar

The following two tabs change content below. Required if encapsulated document is a CDA document. Document Class Code Sequence.

PDF Attachment in HL7 Message

The title of the document. The date and time that the original generation of the data in the document started.

Identification of patient and date as text in an encapsulated document e. If the encoding component ED.

The type of encoding used to represent successive octets of binary data as displayable ASCII characters. R right L left U unpaired B both left and right. This can be expressed as “encode”, “escape”, “parse”, “de-escape” or “decode”.

Only a single Item is permitted in this sequence. Additional classifications of the document, beyond the title represented in Concept Name Code Sequence. Equivalent to HL7 v2. The time the document content creation was started. Encapsulated Document Module Attributes. Indicates whether or not the encapsulated document contains sufficient burned in annotation to identify the patient and date the data was acquired.


Home Data Type ED – encapsulated data.

ED – Encapsulated Data (HL7 v)

Referenced Performed Procedure Step Sequence. Acquisition DateTime ,A 2 The date and time that the original generation of the data in the document started. Content Time2 The time the document content creation was started. This data type transmits encapsulated data from a source system to a destination system. 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 encaosulated the document.

The key question is not what the HL7 standard says about document encoding or even what the interface engine can do with the document. On the receiving application, the data field must be de-escaped after being parsed out of yl7 message before being encapsulahed.

Unique identifier of the Series. This data type is similar to the RP reference pointer data type of Section 2.

Refer to HL7 Table – Encoding for valid values. Identical format and restrictions as in reference pointer see Section 2.

If the encoding component see Section 2. To begin, start with the answer to this question: The value shall be unique within a series.

Description of the Series. How will the source application provide the PDF file fncapsulated how will the destination application s receive the data? May be present otherwise. Concept Name Code Sequence. One or more Items shall be included in this Sequence. MIME Types of subcomponents of the encapsulated document.



Review these prior blog postings for details:. Note One could distinguish four stages in the creation of the Encapsulated Document Object, identified by the following Attributes: Description of the enczpsulated under nl7 the Series was performed. A sequence that identifies the set of Instances that were used to derive the encapsulated document.

Indicates whether or not the image contains sufficiently recognizable visual features to allow the image or a ebcapsulated from a set of images to identify the patient. 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.

Indicates whether the Encapsulated Document is Verified. A coded representation of the document title. Identical to “type of data” component in the reference pointer RP data type.

Dave has more than 20 years experience in training, consulting, and software development.

Attested to signed by a Verifying Observer or Legal Authenticator named in the document, who is accountable for its content. Creation of the original documentation of the data collection, identified by Content Dateand Content Time ,