DICOM @ OFFIS

dcm2xml is not capable of converting an xml file back to dicom

Hi Michael,

thank you for your quick reply. The error message you get on the server side might be related to our problem (Currently, I can not see what is exactly going on on the server side). If I find out more, I will post it here as well.

Best regards

Markus

Hi all, I have encountered the same or a similar problem sending images to a diagnostic workstation with storescu, but I was sure, it could not be an error in the toolkit (until now :-( ). The error occurs with v3.53 and 3.54 of dcmtk. I have modified DcmTCPConnection::write: int iRet = send(getSock...

Hi John, I' not sure, but it looks as if exception handling is disabled for at least one of your projects. Most likely, the problem is in CMakeLists.txt. Make sure, that the /EHsc option is set in CMAKE_CXX_FLAGS for all configurations (Debug, Release, ...) If you do not use Exception handling, disa...

Hi John,

you need to add the dcmtk libraries (in this case: dcmdata and ofstd) to your project's linker options (Project properties -> Linker -> Input -> Additional Dependencies)

HTH

Markus

Hi, as Marco stated above, you have to query down from the patient to the instance (image-) level. However, there is a good chance that your DICOM archive will accept and answer a query correctly that contains all the attributes in one dataset, e.g. (0008,0052) CS [IMAGE] # QueryRetrieveLevel (0010,...

Referring to DICOM, Part 4 C.3.3 Patient/Study Only Query/Retrieve Information Model The Patient/Study Only Query/Retrieve Information Model is identical to the Patient Root except the series and composite object instance levels are not supported. Note: Even though this model does not include the co...

I have encountered exactly that problem with a specific PACS some months ago. I do not want to name the vendor here (but the logfile looks quite similar). The problem was caused by a bug in the server and is well-known at the vendor's site. A patch should be available.

Best regards

Markus

I have another question about the DataSetType (0x0000, 0x0800). We are currently testing our dcmtk-based PACS application against products by other vendors. We had a problem with the JDicom Query/Retrieve SCU and found out, that it processes our responses properly, if we set the DataSetType in the C...