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):||2 April 2007|
|PDF File Size:||3.67 Mb|
|ePub File Size:||19.18 Mb|
|Price:||Free* [*Free Regsitration Required]|
R right L left U unpaired B both left and right.
This data type transmits encapsulated data from a source system to a destination system. The following two tabs change content below.
It is expected that applications will ensure consistency in a manner appropriate to the application. Review these prior blog postings encapsullated details:. Zero or one Item shall be included in this sequence. The characters are limited to the hk7 characters of the ST data type, as defined in Section 2.
If the encoding component see Section 2. Latest posts by Dave Shaver see all.
One or more Items shall be included in this Sequence. Refer to HL7 Table – Encoding for valid values. Sequence that contains attributes from the Imaging Service Request. The date and time that the original generation of the data in the document started.
ED – Encapsulated Data (HL7 v)
No Baseline CID is defined. The key question is not what the HL7 standard says about document encoding or even what the interface engine can do with the document. Concept Name Code Sequence.
Indicates whether or not the image contains sufficiently recognizable visual features to allow the image or a reconstruction from a set of images to identify the encapeulated.
It contains the identity of the source system, the type of data, the encoding method of the data, and the data itself. A de-identified document may use the value NO.
If the encoding component ED. Home Encaapsulated Type ED – encapsulated data. The date the document content creation was started. Creation of the original documentation of the data collection, identified by Content Dateand Content TimeContent Time2 The time the document content creation was started.
Only a single Item is permitted in this sequence.
PDF Attachment in HL7 Message
Identical format and restrictions as in reference pointer see Section 2. Description of the Series. How will the source application provide the PDF encapsulatee and how will the destination application s receive the data?
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 ecapsulated one ED summaryhow will the receiving application know onto which tab of the patient chart the document should flow?
Image Laterality3 Laterality of the possibly paired body part that is the subject of the encapsulated document. Encapsulated Document Module Attributes.
Identical to “subtype” component in the reference pointer RP data type. Attested to signed by a Verifying Observer or Legal Authenticator named in the document, who is accountable for its content.
HL7 – REFACTORED
Encapsulated Document Series Module Attributes. A unique name that identifies the system which was the source of the data. A number that identifies this SOP Instance. Identical to “type of data” component in the reference pointer RP data type. A coded representation of the document title. Displayable ASCII characters which constitute the data to be sent from source application to destination application. MIME Types of subcomponents of the encapsulated document.
Acquisition DateTime ,A 2 The date and time that the original generation of the data in the document started.