DICOM @ OFFIS

It seems that you are still missing many details of the technical specification, i.e. you have to read the DICOM Standard on how WSI objects are encoded, in particular, in TILED_SPARSE mode. According to the DICOM WSI specification(https://dicom.nema.org/dicom/dicomwsi/): This is not the specificati...

The echoscu command line tool does not allow for specifying the list of proposed Presentation Contexts. Instead, when you use option -pts the list of Presentation Contexts is created from the hard-coded list of Transfer Syntaxes that can be found in the source file echoscu.cc starting with line 67 ....

Using a batch or shell script that creates the directories and calls the DCMTK tool dcmj2pnm (now known as dcm2img) appropriately should work.

I don't think that wlmscpfs does any character set conversion, so if your worklist data is encoded with UTF-8 but you tell wlmscpfs to return ISO Latin-1 to the requester... this cannot work, of course. See man page for details. Did you already try with option -csk (--keep-char-set)? And, please mak...

If you know what you are doing, you could use e.g. dump2dcm or xml2dcm to convert a textual dump / XML dump and referenced HEVC data (I guess you mean this video encoding) to binary DICOM format, and "dcmdump --write-pixel" to convert it back. Unfortunately, dcm2xml does not yet support ex...

Re. 1: DCMTK's data dictionary defines all required Attributes for the SR Content Item Value Type "TABLE". However, the dcmsr module does not yet implement support for it, as you can read in DCMTK issue #955 . The TABLE type is quite complex and so far the priority has not been that high. ...

You could e.g. check the DICOM Standard to see if there are restrictions for these Attributes regarding the underlying IOD (see PS3.3) or regarding the (compressed) Transfer Syntax (see PS3.5), hoping that the creator of the image has followed these restrictions. And, of course, you could check the ...

However, we are unsure whether the value that is incorrect here is indeed HighBit, or is it maybe BitsStored that should be edited to match HighBit + 1. I do understand your doubts. Maybe, you can derive the correct value(s) from additional information in the dataset. However, since the dataset in ...

Here it is.

Maybe, you want to try adding the process ID to the name of the logger file (using the substitution variable "${pid}"). See documentation of logger.cfg for details. P.S.: I agree that creating a new process is ugly, but this is how it works on Windows. The original implementation was done ...

The dcmodify tool (as all DCMTK command line tools) takes the character string as you specify it. So, if you want to store a value in Latin-1 (ISO 8859-1) encoding, you have to provide the correct byte sequence. Alternatively, you could change the encoding of the DICOM dataset to UTF-8 (ISO_IR 192) ...

The underlying code of the DcmDicomDir class directly works on the specified DICOMDIR file, i.e. the data structures are managed in memory but are written to file in the destructor of this class. Just let me know if having a written DICOMDIR is required for updateDicomDir to work (code seems to say ...

Of course, professional consultancy is not free of charge. But now, you seem to follow the approach I proposed in one of my first postings in this thread: create a DICOMDIR based on a particular Application Profile and then append further entries based on another Application Profile by updating the ...

Your links do not work, probably because the GitHub project is not public.

It would be nice to have someone with experience with DICOMDIRs to consult.

You could e.g. contact Marco from the OFFIS DICOM Team, Michael from Open Connections or me (Freelancer).

Are there places that describe DICOMDIR usage more clearly and with cases for situations when you need to support any transfer syntax coming in? We don't have a UI for selecting the application profiles. DICOM Media Storage Application Profiles are always related to a certain use case. They are des...