Dear ImageJ mailing list,
I am a medical physicist working in a hospital based imaging department (nuclear medicine). I am trying to export/save an image in DICOM format so that our DICOM workstations and our hospital PACS system can load the image. I have had limited success with the Tudor DICOM plugin and the "IFTM Institut fur Telematik in der Medizin" DICOM import/export plugin. The Tudor DICOM plugin is almost perfect. The only problem is that the "Transfer Syntax UID:" (DICOM Tag 0002,0010) is incompatible with our DICOM workstations. The Tudor plugin saves the images as "1.2.840.10008.1.2.2" (Explicit VR Big Endian) whereas our workstations only accept "1.2.840.10008.1.2" (Implicit VR Endian). This is very frustrating! Is anybody aware of a plugin that will change the Transfer Syntax UID and save back as DICOM? If the authors of the Tudor DICOM plugin are reading, is there a previous version that will save with "Transfer Syntax UID 1.2.840.10008.1.2" (Implicit VR Endian)? Is there a modification I can make to the plugin to make this change (with your permission, of course)? The "IFTM Institut fur Telematik in der Medizin" DICOM import/export plugin has a different problem. The "Transfer Syntax UID:" is correct i.e. "1.2.840.10008.1.2" (Implicit VR Endian). However, the patient demographics are lost in the DICOM export process. Our hospital DICOM workstations therefore allow me to import the DICOM file but I must then manually edit the patient demographics (which is not a great idea from a data quality point of view). Any help or advice on or off list would be greatly appreciated. I would also be very interested in hearing from medical professionals who have had similar problems/experiences with these plugins. Thank you, Greg [hidden email] -- ImageJ mailing list: http://imagej.nih.gov/ij/list.html |
Dear Greg,
The Exporter Code of the Tudor DICOM Plugin is not directly written by me and not tested very well. It might be enough to change the private String transferSyntax = UID.ExplicitVRBigEndian; in the lu.tudor.santec.dicom.exporter.DicomExporter class to export the images as ImplicitVR. If you although want to change to LittleEndian i thing there needs to be a change in dumping the pixels: DicomOutputStream dos = new DicomOutputStream(bos); FileInfo fi = ip.getFileInfo(); Object pixels = fi.pixels; ImageWriter iw = new ImageWriter(fi); .... // write the pixel data iw.write(dos); .... you can find the sourcecode of our tools at: http://santec.tudor.lu/project/dicom/download Best Regards Johannes Hermen ----------------------------------------------------------------- Johannes Hermen - Ingenieur de Recherche [hidden email] ----------------------------------------------------------------- CRP Henri Tudor http://www.santec.tudor.lu 29, Avenue John F. Kennedy L-1855 Luxembourg ----------------------------------------------------------------- From: Gregory James <[hidden email]> To: <[hidden email]>, Date: 18.10.2013 12:29 Subject: Tudor DICOM Plugin Sent by: ImageJ Interest Group <[hidden email]> Dear ImageJ mailing list, I am a medical physicist working in a hospital based imaging department (nuclear medicine). I am trying to export/save an image in DICOM format so that our DICOM workstations and our hospital PACS system can load the image. I have had limited success with the Tudor DICOM plugin and the "IFTM Institut fur Telematik in der Medizin" DICOM import/export plugin. The Tudor DICOM plugin is almost perfect. The only problem is that the "Transfer Syntax UID:" (DICOM Tag 0002,0010) is incompatible with our DICOM workstations. The Tudor plugin saves the images as "1.2.840.10008.1.2.2" (Explicit VR Big Endian) whereas our workstations only accept "1.2.840.10008.1.2" (Implicit VR Endian). This is very frustrating! Is anybody aware of a plugin that will change the Transfer Syntax UID and save back as DICOM? If the authors of the Tudor DICOM plugin are reading, is there a previous version that will save with "Transfer Syntax UID 1.2.840.10008.1.2" (Implicit VR Endian)? Is there a modification I can make to the plugin to make this change (with your permission, of course)? The "IFTM Institut fur Telematik in der Medizin" DICOM import/export plugin has a different problem. The "Transfer Syntax UID:" is correct i.e. "1.2.840.10008.1.2" (Implicit VR Endian). However, the patient demographics are lost in the DICOM export process. Our hospital DICOM workstations therefore allow me to import the DICOM file but I must then manually edit the patient demographics (which is not a great idea from a data quality point of view). Any help or advice on or off list would be greatly appreciated. I would also be very interested in hearing from medical professionals who have had similar problems/experiences with these plugins. Thank you, Greg [hidden email] -- ImageJ mailing list: http://imagej.nih.gov/ij/list.html -- ImageJ mailing list: http://imagej.nih.gov/ij/list.html |
Free forum by Nabble | Edit this page |