Problems with private elements

[Wonko]

I am having trouble adding lots of private elements to my dictionary.

These are some lines from my private.dic:

Code: Select all

(7fe3,"SIEMENS MED",3f)	ox	IconProjectionPixelData	1
(7fe3,"SIEMENS MED",7f)	ox	IconProjectionPixelData	1
(7fe3,"SIEMENS MED",bf)	ox	IconProjectionPixelData	1
(7fe3,"SIEMENS MED",ff)	ox	IconProjectionPixelData	1

Using dcmdump, I see that elements 103f, 107f, 10bf and 10ff of group 7fe3 are identified correctly, but all higher elements like 113f, 117f and so on are not. The reservation context seems okay to me:

Code: Select all

(7fe3,0010) LO [SIEMENS MED]                            #  12, 1 PrivateCreator
(7fe3,0011) LO [SIEMENS MED]                            #  12, 1 PrivateCreator
(7fe3,0012) LO [SIEMENS MED]                            #  12, 1 PrivateCreator
... and so on

Am I doing something wrong? I also tried to specify the elements directly:

Code: Select all

(7fe3,"SIEMENS MED",103f)	ox	IconProjectionPixelData	1
(7fe3,"SIEMENS MED",107f)	ox	IconProjectionPixelData	1
(7fe3,"SIEMENS MED",10bf)	ox	IconProjectionPixelData	1
(7fe3,"SIEMENS MED",10ff)	ox	IconProjectionPixelData	1
(7fe3,"SIEMENS MED",113f)	ox	IconProjectionPixelData	1
(7fe3,"SIEMENS MED",117f)	ox	IconProjectionPixelData	1
...

But again, elements > 0x10ff are not being recognized.

Then I tried with the format as in dicom.dic, like this:

Code: Select all

(7fe3,103f)	ox	IconProjectionPixelData	1 foo

These element is not being recognized at all. I first thought this is because private elements with odd group number are not allowed there, but it works fine for another element:

Code: Select all

(0019,0004)	CS	IconUnits	1 foo

The input file is not in correct DICOM format, I get warnings of elements not being in ascending tag order. But the reservation elements appear before the corresponding elements, so this should not be the problem.

Any idea what I am doing wrong?

[Marco Eichelberg]

I would suggest that you run the file through dcmconv once to sort out the problems with tags not in ascending order. If the reservation elements then still appear with correct content, the dictionary should also correctly identify attributes in (7fe3,11xx). Directly putting attributes like (7fe3,103f) or (0019,0004) into the dictionary will not work because for odd groups attributes with element tag >= 0x1000 will only be looked up relative to the reservation element name. (0019,0004) only works because this is not a valid private attribute, actually not a valid tag at all since private attributes cannot use (gggg,eeee) with eeee > 0 and eeee < 0x10.

[Wonko]

Thanks, good idea! I didn't think about that. After some experimenting with the options it seems that using +te seems to do the trick.

Thanks again for the fast response!