Uncompressed pixel data element in an Encapsulated format encoding valid?

[Abhijit Satpute]

We have received a Dicom image from our customer that is using Transfer Syntax as 1.2.840.10008.1.2.1 i.e. ("Explicit VR Little-endian") and it contains Pixel Data element (7FE0:0010) VR of type OB.
This Pixel Data element (7FE0:0010) contains uncompressed pixel data in an Encapsulated Format Encoding.

(For e.g. Contents of Pixel Data element (7FE0:0010)
.....Sequence Item Start Delimiter with size......uncompressed pixel data....Sequence Item End Delimeter with size
.......fe ff 00 e0 00 00 00 00 fe ff 00 e0 00 00 08 00 30 f8 30 f8 30 f8 30 f8 30 f8 30 f8 30 f8 30 f8 30 f8 30 f8 30 f8 30 f8 30 f8 30 f8 30 f8 30 f8 30 f8 30 f8 30 f8 30 f8 30 f8 30 f8 30 f8 30 f8 30 f8 30 f8 30 f8 30 f8 30 f8 30 f8 30 f8 30 f8 30 f8 30 f8 30 .........fe ff dd e0 00 00 00 00)

So the questions are as follows:
1. Can Dicom file contains uncompressed pixel data element in an Encapsulated format encoding having transfer syntax as 1.2.840.10008.1.2.1 i.e. ("Explicit VR Little-endian")?
2. Is this file valid according to Dicom Standards?

[Nano.]

Hi Abhijit,

Here is my quick response (don't fully really on it, might be wrong)

1) They shouldn't, if they have encapsulated format encoding, they should specify which one accordingly in the Transfer Syntax

2) I might say that is not valid.

I won't be surprised to find images where the case you have described actually happens.

Hope that helps. I will be interested to see what conclusion you find yourself.

Regards,

Nano.

--
You received this message because you are subscribed to the Google Groups "nanodicom" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nanodicom+...@googlegroups.com.
To post to this group, send email to nano...@googlegroups.com.
Visit this group at http://groups.google.com/group/nanodicom.
For more options, visit https://groups.google.com/groups/opt_out.