Gdcm DICOM v3.0 conformance summary

Introduction

This section is an abbreviated DICOM conformance statement for gdcm.
It specifies the compliance of gdcm to file reading/writing support to the dicom base standard part 5.
Gdcm does not contain or support any of the DICOM services such as Storage, Query/Retrieve, Print, Verification...

Supported transfer syntaxes

The Transfer Syntax UID is in the file's DICOM Tag field (0002,0010).
Uncompressed Transfer Syntax Description
1.2.840.10008.1.2 Little endian, implicit value representation
1.2.840.10008.1.2.1 Little endian, explicit value representation
1.2.840.10008.1.2.2 Big endian
RLE Transfer Syntax
1.2.840.10008.1.2.5 Run Length Encoding, Lossless
JPEG Transfer Syntax
1.2.840.10008.1.2.4.50 Jpeg laseline (Process 1)
1.2.840.10008.1.2.4.51 Jpeg extended (Process 2 & 4)
1.2.840.10008.1.2.4.57 Jpeg lossless, non-hierarchical (process 14)
1.2.840.10008.1.2.4.70 Jpeg lossless, hierarchical, first-order prediction (process 14, selection value 1)

Supported "Photometric Interpretation" pixel format

The Photometric Interpretation UID is in the file's DICOM Tag field (0028,0004).
Photometric Interpretation" pixel format Description
MONOCHROME1
MONOCHROME2
PALETTE COLOR color image description
RGB color image description
YBR_FULL color image description
YBR_FULL_422 color image description

Note on odd length data elements

The Dicom Standard PS 3.5 (Data Structures and Encoding) specifies that the data element values which make up a DICOM data stream must be padded to an even length.
Gdcm will tolerate an incorrectly formed odd length data field while reading (thus not enforcing the standard).
But gdcm will allways enforce the standard while writing.

Note on undefined Value Representations

If gdcm encounters an undefined VR (either because in a private group, or because it corresponds to an undocumented public dictionary entry when in implicit VR) while reading a file, it will set that data element's VR to be UN (unknown).

Note on retired and private data elements

Certain data elements are no longer supported under the v3.0 of the DICOM standard but persist as retired element. Gdcm will consider those elements as standard data element, except that the tag name will be postfixed with the "(RET)" string.

UNSupported transfer syntaxes

The Transfer Syntax UID is in the file's DICOM Tag field (0002,0010).
Jpeg UNSUPPORTED Transfer Syntax Description
1.2.840.10008.1.2.4.52 JPEG Extended (Process 3 & 5)
1.2.840.10008.1.2.4.53 JPEG Spectral Selection, Non-Hierarchical (Process 6 & 8)
1.2.840.10008.1.2.4.54 JPEG Spectral Selection, Non-Hierarchical (Process 7 & 9)
1.2.840.10008.1.2.4.55 JPEG Full Progression, Non-Hierarchical (Process 10 & 12)
1.2.840.10008.1.2.4.56 JPEG Full Progression, Non-Hierarchical (Process 11 & 13)
1.2.840.10008.1.2.4.58 JPEG Lossless, Non-Hierarchical (Process 15)
1.2.840.10008.1.2.4.59 JPEG Extended, Hierarchical (Process 16 & 18)
1.2.840.10008.1.2.4.60 JPEG Extended, Hierarchical (Process 17 & 19)
1.2.840.10008.1.2.4.61 JPEG Spectral Selection, Hierarchical (Process 20 & 22)
1.2.840.10008.1.2.4.62 JPEG Spectral Selection, Hierarchical (Process 21 & 23)
1.2.840.10008.1.2.4.63 JPEG Full Progression, Hierarchical (Process 24 & 26)
1.2.840.10008.1.2.4.64 JPEG Full Progression, Hierarchical (Process 25 & 27)
1.2.840.10008.1.2.4.65 JPEG Lossless, Hierarchical (Process 28)
1.2.840.10008.1.2.4.66 JPEG Lossless, Hierarchical (Process 29)