#15 GDCM fails to recognize DICOM file as MR image

open
5
2012-03-15
2010-08-11
Sean McBride
No

We have a DICOM file where GDCM warns (on both Intel and PPC):

Warning: In /GDCM/Source/MediaStorageAndFileFormat/gdcmPixmapReader.cxx, line 170, function <unknow>
Attempting to read this file as a DICOM file
Desperate attempt

Warning: In /GDCM/Source/DataStructureAndEncodingDefinition/gdcmMediaStorage.cxx, line 301, function <unknow>
Does not know what: 1.2.276.0.7230010.3.1.0.1

The OFFIS folks said:

"the reason for the private DCMTK SOP class is quite simple: The data element
SOP Class UID (0008,0016) was missing in the DICOM dataset, so the DCMTK
tool that was used to create the DICOM file added the private SOP class to
the file meta information header (usually, the value is copied from the
dataset).

Looking into the file, it seems that it should be an MR image. Therefore, I
added the SOP Class UID element with the value of the MR Image Storage SOP
class (1.2.840.10008.5.1.4.1.1.4) to the file and updated the meta header
using the DCMTK tool dcmodify. Also the SOP Instance UID (0008,0018) was
missing in the original file, so I generated a new one (again, using dcmodify).

Please find enclosed the new DICOM file with the missing data elements added
to it. I think it is obvious that the original file (without SOP Class UID
and SOP Instance UID) does not conform to the requirements of the DICOM
standards. These data elements should always be present with a valid value
(called "type 1" attributes in DICOM language)!"

So this DICOM file is not conformant, but other software can display it properly.

I cannot share the DICOM file in this public bug. Contact me privately.

Discussion

    • priority: 5 --> 1
    • labels: 804608 -->
     
  • Lowering priority. I do not believe this is a bug as such, changing to feature request.

     
    • priority: 1 --> 5
    • labels: --> General (default)