dcm image can not be open while dcmdump works well

All other questions regarding DCMTK

Moderator: Moderator Team

Post Reply
Message
Author
Ricky Yang
Posts: 8
Joined: Thu, 2020-08-06, 07:28

dcm image can not be open while dcmdump works well

#1 Post by Ricky Yang » Tue, 2021-02-23, 03:17

Hello Engineer,

I have one dcm file which can not be opened and viewed, I use dcmdump to dump the tags, it looks good in the text.
Can you help check why it can not be opened or viewed?

I have sent the file to dicom@offis.de by email. Please check the original file and I appreciate your time and help!

Thank you!


Dcmdump file text:

# Dicom-File-Format

# Dicom-Meta-Information-Header
# Used TransferSyntax: Little Endian Explicit
(0002,0000) UL 200 # 4, 1 FileMetaInformationGroupLength
(0002,0001) OB 00\01 # 2, 1 FileMetaInformationVersion
(0002,0002) UI =UltrasoundMultiframeImageStorage # 28, 1 MediaStorageSOPClassUID
(0002,0003) UI [2.16.124.113577.1.1015010190.20210222.152647.2927.10] # 52, 1 MediaStorageSOPInstanceUID
(0002,0010) UI =JPEG2000LosslessOnly # 22, 1 TransferSyntaxUID
(0002,0012) UI [1.2.276.0.7230010.3.0.3.6.1] # 28, 1 ImplementationClassUID
(0002,0013) SH [OFFIS_DCMTK_361] # 16, 1 ImplementationVersionName

# Dicom-Data-Set
# Used TransferSyntax: JPEG 2000 (Lossless only)
(0008,0005) CS [ISO_IR 100] # 10, 1 SpecificCharacterSet
(0008,0008) CS [ORIGINAL\PRIMARY\] # 18, 3 ImageType
(0008,0012) DA [20210222] # 8, 1 InstanceCreationDate
(0008,0013) TM [152700] # 6, 1 InstanceCreationTime
(0008,0014) UI [2.16.124.113577.1.1015010190] # 28, 1 InstanceCreatorUID
(0008,0016) UI =UltrasoundMultiframeImageStorage # 28, 1 SOPClassUID
(0008,0018) UI [2.16.124.113577.1.1015010190.20210222.152647.2927.10] # 52, 1 SOPInstanceUID
(0008,0020) DA [20210222] # 8, 1 StudyDate
(0008,0021) DA [20210222] # 8, 1 SeriesDate
(0008,0023) DA [20210222] # 8, 1 ContentDate
(0008,0030) TM [142206] # 6, 1 StudyTime
(0008,0031) TM [142206] # 6, 1 SeriesTime
(0008,0033) TM [152647] # 6, 1 ContentTime
(0008,0050) SH (no value available) # 0, 0 AccessionNumber
(0008,0060) CS [US] # 2, 1 Modality
(0008,0070) LO [Ultrasonix Medical Corp.] # 24, 1 Manufacturer
(0008,0080) LO [Anaheim Hills Pet Clinic'] # 26, 1 InstitutionName
(0008,0090) PN (no value available) # 0, 0 ReferringPhysicianName
(0008,1010) SH [ hospital] # 10, 1 StationName
(0008,1030) LO [Dog-Small] # 10, 1 StudyDescription
(0008,103e) LO [Dog-Small] # 10, 1 SeriesDescription
(0008,1050) PN [AHPC92807] # 10, 1 PerformingPhysicianName
(0008,1070) PN [RONALD DAGGETT] # 14, 1 OperatorsName
(0008,1090) LO [SONIX] # 6, 1 ManufacturerModelName
(0008,2144) IS [12] # 2, 1 RecommendedDisplayFrameRate
(0010,0010) PN [KNEAFSEY^DAISY] # 14, 1 PatientName
(0010,0020) LO [PID_22-02-2021_14-22-06-755] # 28, 1 PatientID
(0010,0030) DA (no value available) # 0, 0 PatientBirthDate
(0010,0040) CS (no value available) # 0, 0 PatientSex
(0018,0040) IS [12] # 2, 1 CineRate
(0018,1000) LO [SXONE101501A0190] # 16, 1 DeviceSerialNumber
(0018,1020) LO [6.1.1] # 6, 1 SoftwareVersions
(0018,1063) DS [12.0] # 4, 1 FrameTime
(0018,1244) US 0 # 2, 1 PreferredPlaybackSequencing
(0018,6011) SQ (Sequence with explicit length #=1) # 140, 1 SequenceOfUltrasoundRegions
(fffe,e000) na (Item with explicit length #=11) # 132, 1 Item
(0018,6012) US 1 # 2, 1 RegionSpatialFormat
(0018,6014) US 1 # 2, 1 RegionDataType
(0018,6016) UL 2 # 4, 1 RegionFlags
(0018,6018) UL 40 # 4, 1 RegionLocationMinX0
(0018,601a) UL 65 # 4, 1 RegionLocationMinY0
(0018,601c) UL 680 # 4, 1 RegionLocationMaxX1
(0018,601e) UL 545 # 4, 1 RegionLocationMaxY1
(0018,6024) US 3 # 2, 1 PhysicalUnitsXDirection
(0018,6026) US 3 # 2, 1 PhysicalUnitsYDirection
(0018,602c) FD 0.024500000000000002 # 8, 1 PhysicalDeltaX
(0018,602e) FD 0.024500000000000002 # 8, 1 PhysicalDeltaY
(fffe,e00d) na (ItemDelimitationItem for re-encoding) # 0, 0 ItemDelimitationItem
(fffe,e0dd) na (SequenceDelimitationItem for re-encod.) # 0, 0 SequenceDelimitationItem
(0020,000d) UI [2.16.124.113577.1.1015010190.20210222.142206.2927] # 50, 1 StudyInstanceUID
(0020,000e) UI [2.16.124.113577.1.1015010190.20210222.142206.2927.1] # 52, 1 SeriesInstanceUID
(0020,0010) SH [2927] # 4, 1 StudyID
(0020,0011) IS [1] # 2, 1 SeriesNumber
(0020,0012) IS (no value available) # 0, 0 AcquisitionNumber
(0020,0013) IS [10] # 2, 1 InstanceNumber
(0020,0020) CS (no value available) # 0, 0 PatientOrientation
(0020,0060) CS (no value available) # 0, 0 Laterality
(0028,0002) US 3 # 2, 1 SamplesPerPixel
(0028,0004) CS [RGB] # 4, 1 PhotometricInterpretation
(0028,0006) US 0 # 2, 1 PlanarConfiguration
(0028,0008) IS [100] # 4, 1 NumberOfFrames
(0028,0009) AT (0018,1063)\(0000,0000) # 8, 2 FrameIncrementPointer
(0028,0010) US 600 # 2, 1 Rows
(0028,0011) US 800 # 2, 1 Columns
(0028,0100) US 8 # 2, 1 BitsAllocated
(0028,0101) US 8 # 2, 1 BitsStored
(0028,0102) US 7 # 2, 1 HighBit
(0028,0103) US 0 # 2, 1 PixelRepresentation
(0049,1050) OB 52\49\46\46\58\a8\18\00\41\56\49\20\4c\49\53\54\c0\00\00\00\68\64... # 1616384, 1 Unknown Tag & Data

Marco Eichelberg
OFFIS DICOM Team
OFFIS DICOM Team
Posts: 1292
Joined: Tue, 2004-11-02, 17:22
Location: Oldenburg, Germany
Contact:

Re: dcm image can not be open while dcmdump works well

#2 Post by Marco Eichelberg » Tue, 2021-02-23, 09:09

This is not a valid DICOM image. In every DICOM image, the image pixel data is stored in attribute (7FE0,0010) PixelData, independent of the encoding (transfer syntax) used. As you can see, in this file there is no attribute (7FE0,0010), thus it's not valid DICOM.

What the vendor has done here is the following: They seem to have removed the original pixel data, compressed it into an AVI video, and stored the AVI file as a private attribute (0049,1050).
You can see that the first four bytes of (0049,1050) are 52\49\46\46, which is "RIFF", the "magic word" used by AVI video files (and a few other file formats).
So while the file still looks like DICOM, this is actually a proprietary encoding that is not permitted in DICOM.

Post Reply

Who is online

Users browsing this forum: Bing [Bot], Google [Bot] and 1 guest