DICOM @ OFFIS

I do, and just for correction, the conformance statement accepts the following Transfer Syntaxes 1.2.840.10008.1.2 Implicit VR Endian: Default Transfer Syntax for DICOM 1.2.840.10008.1.2.1 Explicit VR Little Endian 1.2.840.10008.1.2.2 Explicit VR Big Endian 1.2.840.10008.1.2.4.50 JPEG Baseline (Proc...

Thank you for the clarification and direction to the DICOM Standard, J. I did just do an attempt converting it to ILE (1.2.840.10008.1.2), converts file successfully, and is viewable in MicroDICOM, but I can't get it to store to the target still. Thank you for the suggestion, though. I'm up to try a...

Thanks again, Michael. Great thoughts. I'm attempting this process of compressing to a lossless format, but I'm unable to get the "OB" VR for PixelData when uncompressing back to Little Endian with dcmdjpeg. With the Lossless (+e1 or +el), the new image does contain OB as the VR for that t...

Thanks for the quick response, Michael. This one has me scratching my head! Running dcmcjpeg with verbose and debug on, no errors or warnings seen. We did verify the images with a couple of validators including the dciodvfy. There are some errors/warnings, but nothing different from other images tha...

Hello all. I'm having an issue storing an image to a PACs system, in which the node sending to only accepts Little endian explicit or JPEG Baseline process 1 transfer syntaxes. We currently have the images in little endian explicit, but the target PACs is not accepting it, we believe the issue to be...