The discussion below initially took place here: https://github.com/QIICR/dcmqi/issues/348 . From @mmromero on Tue Aug 07 2018 13:03:44 GMT+0000 (UTC) Dear developers, I am trying to create the structure report of a white matter hyper-intensity lesion segmentation with your docker container but no …

From @pieper on Tue Aug 07 2018 17:01:29 GMT+0000 (UTC) Actually I think if you imported the other data and then put your volume in the subject hiearchy node with the imported data then the exported data dicom files would inherit the study information. The point about the exported dicom having a C…

From @fedorov on Tue Aug 07 2018 17:03:45 GMT+0000 (UTC) > making the modality into a command line argument would be a simple fix I don’t think it would be that simple. The tool would need to know what attributes are required by individual IODs, and be able to import those from the input reference…

From @pieper on Tue Aug 07 2018 17:07:38 GMT+0000 (UTC) That’s my point - of course it’s complicated to make everything perfect, but if all you need to do is help people in @mmromero’s situation then there may not be any better tool. Plus improving the DICOM export from Slicer, even if imperfect, …

From @fedorov on Tue Aug 07 2018 17:30:24 GMT+0000 (UTC) Yes, I completely agree. I am just wondering if there is another ready-to-go tool that could help here.

From @pieper on Tue Aug 07 2018 17:46:48 GMT+0000 (UTC) Depending on how much data there is to convert and how variable it is, one brute force method is to use dcmdump and dump2dcm along with a script that slices up the volumes and does string replaces on the dump file. Not elegant but at least yo…

From @lassoan on Tue Aug 07 2018 18:58:44 GMT+0000 (UTC) You can specify any modality when you export an image from Slicer. In the DICOM export dialog, change Modality tag in Edit DICOM tags section. In Data module, create subject and study, drag-and-drop the series (volume node) under the study, …

From @mmromero on Wed Aug 08 2018 10:38:57 GMT+0000 (UTC) Thank you @lassoan , exporting dicoms from Slicer works. I managed to generate the segmentation report. Also @pieper and @fedorov , thank you for quick answer and support.

From @pieper on Wed Aug 08 2018 12:14:14 GMT+0000 (UTC) Thanks @mmromero for reporting and following up!

From @fedorov on Wed Aug 08 2018 15:57:07 GMT+0000 (UTC) @lassoan thank you for the details! @mmromero glad the issue is resolved for you, and thank you for pointing us to the other tool you used. I was not aware of it. If/when I figure out what was the issue with the output it produces, I will s…

From @lassoan on Wed Aug 08 2018 21:49:08 GMT+0000 (UTC) You can use all Slicer features in batch mode, without GUI. If you ever need help in figuring out how to access a particular feature then ask on the Slicer forum. “nifti2dicom” has a very narrow scope - it can only export a single 3D image v…

E: PatientName (0010,0010) violates VR definition in PatientModule but actual value is correct

Support

Topic		Replies	Views
Odd DICOM import Support dicom	9	1416	July 15, 2019
Unable to load DICOM segmentation file Support segmentation , dicom	29	3157	April 6, 2021
SimpleITK WriteImage() fails silently when writing DICOM -- why? And what to do? Development dicom , python	9	2202	May 11, 2024
Exporting DICOM directory after segmenting lesion Feature requests	13	1551	December 17, 2018
Error in DICOM Exporting Support dicom	5	1329	June 3, 2018

E: PatientName (0010,0010) violates VR definition in PatientModule but actual value is correct

Related topics