organize fails on some bad dicom

[pieper]

This message shows up in the debug console when dropping data exported from ITK (CreateADicomSeries module in Slicer). Probably an unescaped character or something.

Uncaught Error: Invalid XML:


258
00\01
1.2.840.10008.5.1.4.1.1.2
1.2.826.0.1.3680043.2.1125.1.59359411652205962355962884364659604
1.2.840.10008.1.2
1.2.826.0.1.3680043.2.1143.107.104.103.115.2.0.17.111.124.113
GDCM 2.0.17
GDCM/ITK 4.6.0


ORIGINAL\PRIMARY\AXIAL
1.2.840.10008.5.1.4.1.1.2
1.2.826.0.1.3680043.2.1125.1.59359411652205962355962884364659604
20090219
010100.000000
1
MR
Unknown manufacturer
Unknown
MR
head
Unknown model
2766852498
LUNG3-72
20060101
010100.000000
M
None
1.3
HFS
1.2.826.0.1.3680043.2.1125.1.34493480437392627366231424368094418
1.2.826.0.1.3680043.2.1125.1.37921084629263350765371580798490328
SLICER10001
1
61
8.64517-133.929\116.786
0\1\0\0\0-1
1.2.826.0.1.3680043.2.1125.1.33360776706425990252973269286741708
SN
1
MONOCHROME2
256
256
1\1
16
16
15
1
84
169
0
1
None
=./uploadedFile.dcm.0.raw

[pieper]

The text above is xml that is mis-interpreted as markdown. Edit the comment to see the original xml.

[bebbi]

can you add the dcmdump of the file?

[bebbi]

Funnily, I just stumbled over the same problem with a ten year old file. There, a newline inside a comment field likely was the issue:

(0010,21b0) LT [MS
] # 4, 1 AdditionalPatientHistory