[Debian-med-packaging] Bug#675448: dcmtk: dcmdjpeg does not set (0028, 2114) LossyImageCompressionMethod when decompressing lossy compressed DICOM file

[Mathieu Malaterre]

tags 675448 confirmed
tags 675448 upstream
thanks

On Fri, Jun 1, 2012 at 2:46 PM, OFFIS DICOM Team <dicom at offis.de> wrote:
> Hi Mathieu,
>
>> dcmdjpeg does not currently properly support lossy compressed DICOM file.
>> It decompress them as lossless file, lossing the lossy information from
>> the original file. Eg:
>
> [...]
>>
>> Where DCMTK_JPEGExt_12Bits.dcm can be found at:
>>
>> http://gdcm.git.sourceforge.net/git/gitweb.cgi?p=gdcm/gdcmData;a=history;f=DCMTK_JPEGExt_12Bits.dcm;h=a38d4be8214fc72c76f4a6051f314e466ffbdcc5;hb=HEAD
>
>
> could you be more specific, i.e. where exactly is the problem? Ah ok, you
> are probably referring to the subject of your email, right? Lossy Image
> Compression Method, Lossy Image Compression and other data elements should
> already be present in the compressed image. IMHO, this is nothing that
> _necessarily_ has to be added by a decompressor.

I am pretty sure this should be required. This breaks all assumptions
in say a clinical trial and you received a disguised lossy mamography
declared as little endian without LossyImageCompressionMethod
attribute.

> Anyway, we already have a corresponding entry (#307) in our internal list of
> things to do - this one has been added about 3 years ago. Thanks for the
> reminder!

Great !

-M