Short description: OHIF viewer can’t see SOPClassUID attribute after I switched to “MainDicomTags” mode as described here: DICOMweb plugin — Orthanc Book documentation.
Long description:
After setting the above mentioned DicomWeb configurations and setting “ExtraMainDicomTags” exactly as in the sample (https://github.com/orthanc-server/orthanc-setup-samples/blob/master/docker/stone-viewer/docker-compose.yml) I noticed that the SOPClassUID (0008,0016) tag is completely missing in the instance items in the response of the /dicom-web/studies/…/series/…/metadata requests (same is true for /dicom-web/studies/…/metadata endpoint).
After lots of experiments I also checked in the DB in the maindicomtags table and there are also no entries with taggroup=8 and tagelement=16.
In my JSON configuration, just like in the linked sample, there definitely is “SOPClassUID” in the ExtraMainDicomTags.Instance array.
Please help me get an answer to these 2 questions:
- Why is SOPClassUID not there in the DB in the maindicomtags table? Shouldn’t it be?
- Why is it not served by the metadata endpoints?
Maybe I misunderstand the documentation, or maybe there is a bug somewhere.
After using these settings I expect the SOPClassUID to be stored in the DB as an extra maindicomtag and to also show up in the metadata responses.
If this is not the case, then please help me clarify what the “Instance”, “Series”, “Study”, “Patient” sections each mean under the “ExtraMainDicomTags” configuration parameter.
I’ll appreciate any help and I can post more info if needed but my hope is that it is easy to reproduce.