[Insight-users] DICOM 2 tags

[Luis Ibanez]

Hi Amit,

The full list of DICOM tags that the Dicom2 reader is parsing
is available in the file:

Insight/Utilities/DICOMParser/DICOMParser.cxx

In line 418 you will find the following:

  DicomRecord dicom_tags[] = {
{0x0002, 0x0002, DICOMParser::VR_UI}, // Media storage SOP class uid
{0x0002, 0x0003, DICOMParser::VR_UI}, // Media storage SOP inst uid
{0x0002, 0x0010, DICOMParser::VR_UI}, // Transfer syntax uid
{0x0002, 0x0012, DICOMParser::VR_UI}, // Implementation class uid
{0x0008, 0x0018, DICOMParser::VR_UI}, // Image UID
{0x0008, 0x0020, DICOMParser::VR_DA}, // Series date
{0x0008, 0x0030, DICOMParser::VR_TM}, // Series time
{0x0008, 0x0060, DICOMParser::VR_SH}, // Modality
{0x0008, 0x0070, DICOMParser::VR_SH}, // Manufacturer
{0x0008, 0x1060, DICOMParser::VR_SH}, // Physician
{0x0018, 0x0050, DICOMParser::VR_FL}, // slice thickness
{0x0018, 0x0060, DICOMParser::VR_FL}, // kV
{0x0018, 0x0088, DICOMParser::VR_FL}, // slice spacing
{0x0018, 0x1100, DICOMParser::VR_SH}, // Recon diameter
{0x0018, 0x1151, DICOMParser::VR_FL}, // mA
{0x0018, 0x1210, DICOMParser::VR_SH}, // Recon kernel
{0x0020, 0x000d, DICOMParser::VR_UI}, // Study UID
{0x0020, 0x000e, DICOMParser::VR_UI}, // Series UID
{0x0020, 0x0013, DICOMParser::VR_IS}, // Image number
{0x0020, 0x0032, DICOMParser::VR_SH}, // Patient position
{0x0020, 0x0037, DICOMParser::VR_SH}, // Patient position cosines
{0x0028, 0x0010, DICOMParser::VR_US}, // Num rows
{0x0028, 0x0011, DICOMParser::VR_US}, // Num cols
{0x0028, 0x0030, DICOMParser::VR_FL}, // pixel spacing
{0x0028, 0x0100, DICOMParser::VR_US}, // Bits allocated
{0x0028, 0x0120, DICOMParser::VR_UL}, // pixel padding
{0x0028, 0x1052, DICOMParser::VR_FL}, // pixel offset
{0x7FE0, 0x0010, DICOMParser::VR_OW}   // pixel data



Regards,


    Luis



----------------------

amit sinha wrote:
> 
> Dear luis,
>    Thanks for your help.But i have another question about dicom2 class.
> Tell me whether the tags (0x0028,0x0008)&(0x0028,0x0009) have been 
> implemented or not as we came to know about  this while looking at the 
> header info using EZdicom .
> These tags are used for no of slices in 3D data.
> Amit Sinha
> 
>