Yet another broken DICOM file - DICOM

This is a discussion on Yet another broken DICOM file - DICOM ; I was recently informed that people are starting to do multi-frame CT Image Storage...well using 'CT Image Storage' as SOP Class http://www.creatis.insa-lyon.fr/~jpr...multiframe.dcm This file is totally broken, it contains a random number of 0 after the Pixel Data element ... ...

+ Reply to Thread
Results 1 to 2 of 2

Thread: Yet another broken DICOM file

  1. Yet another broken DICOM file

    I was recently informed that people are starting to do multi-frame CT
    Image Storage...well using 'CT Image Storage' as SOP Class

    http://www.creatis.insa-lyon.fr/~jpr...multiframe.dcm

    This file is totally broken, it contains a random number of 0 after
    the Pixel Data element ... sigh

    -Mathieu

  2. Re: Yet another broken DICOM file

    Hi Mathieu

    There are a lot of other problems with this SCANCO micro-CT file:

    % dciodvfy CT_Image_Storage_multiframe.dcm
    Error - Invalid Value Representation - Pixel Data - VR = OB, Explicit VR, Bits Allocated = 16 exceeds 8
    Error - Tags out of order - trailing garbage, wrong transfer syntax, or not valid DICOM
    Error - Illegal root for UID - "0.2.16.756.5.23.2.1.3303.7.9.20080522150000.2696.0" in (0x0002,0x0003) Media Storage SOP Instance UID
    Error - Illegal root for UID - "0.2.16.756.5.23.2.2.3303.7.9" in (0x0002,0x0012) Implementation Class UID
    Error - Illegal root for UID - "0.2.16.756.5.23.2.1.3303.7.9.20080522150000.2696.0" in (0x0008,0x0018) SOP Instance UID
    Error - Illegal root for UID - "0.2.16.756.5.23.2.3.3303.7.9" in (0x0020,0x000d) Study Instance UID
    Error - Illegal root for UID - "0.2.16.756.5.23.2.4.3303.7.9" in (0x0020,0x000e) Series Instance UID
    Error - Illegal root for UID - "0.2.16.756.5.23.2.5.3303.7.9" in (0x0020,0x0052) Frame of Reference UID
    Warning - Missing attribute or value that would be needed to build DICOMDIR - Study Date
    Warning - Missing attribute or value that would be needed to build DICOMDIR - Study Time
    Warning - Missing attribute or value that would be needed to build DICOMDIR - Study ID
    Error - Value invalid for this VR - (0x0008,0x103e) LO Series Description LO [0] = - Length invalid for this VR = 128, expected <= 64
    Warning - Value dubious for this VR - (0x0010,0x0010) PN Patient's Name PN [0] = - Retired Person Name form
    Error - Dicom dataset contains invalid data values for Value Representations
    Warning - Retired attribute - (0x0008,0x0000) UL Group Length
    Warning - Retired attribute - (0x0010,0x0000) UL Group Length
    Warning - Retired attribute - (0x0018,0x0000) UL Group Length
    Warning - Retired attribute - (0x0020,0x0000) UL Group Length
    Warning - Retired attribute - (0x0028,0x0000) UL Group Length
    Warning - Dicom dataset contains retired attributes
    CTImage
    Error - Missing attribute Type 2C Conditional Element= Module=
    Warning - Value is zero for value 1 of attribute
    Error - Unrecognized enumerated value <0x6e> for value 1 of attribute
    Warning - Attribute is not present in standard DICOM IOD - (0x0028,0x0008) IS Number of Frames
    Warning - Attribute is not present in standard DICOM IOD - (0x0028,0x0009) AT Frame Increment Pointer
    Warning - Dicom dataset contains attributes not present in standard DICOM IOD - this is a Standard Extended SOP Class

    David

    Mathieu Malaterre wrote:
    > I was recently informed that people are starting to do multi-frame CT
    > Image Storage...well using 'CT Image Storage' as SOP Class
    >
    > http://www.creatis.insa-lyon.fr/~jpr...multiframe.dcm
    >
    > This file is totally broken, it contains a random number of 0 after
    > the Pixel Data element ... sigh
    >
    > -Mathieu


+ Reply to Thread