There are 2 parts in this post:
- Problem with DICOM overlay tags in ExtraMainDicomTags mode
- Question / clarification about ExtraMainDicomTags
I’m using ohif/app:v3.7.0 and jodogne/orthanc-python:1.12.2 together.
1. Problem with DICOM overlay tags in ExtraMainDicomTags mode
In order to view a DICOM overlay image, the viewer needs certain overlay tags.
Orthanc doesn’t seem to allow arbitrary tags in ExtraMainDicomTags.
Putting for example 60003000 under the Instance array (or any other) doesn’t seem to affect it.
Actually I think it parses it as 0000,0000 because when I also add another
tag that the viewer would need for overlay data, 7FE00010 for example, then Orthanc throws such an error:
E0211 06:52:15.027992 MAIN PluginsManager.cpp:153] A main DICOM Tag has been defined multiple times for the same resource level: 0000,0000 is already defined
If only one of them is added, no extra tags show up in the series metadata or /series/{id} responses. If both of them are added, I think both are parsed as 0000,0000 and Orthanc complains that I added
0000,0000 twice.
Are there some constraints on the tags that can be added?
2. Question / clarification about ExtraMainDicomTags
As I understand from the docs, MainDicomTags and ExtraMainDicomTags have 2 main uses as far as HTTP endpoints are concerned:
- the REST API endpoints of Orthanc (/studies/{id}, /series{id}, …), where it affects the
.MainDicomTagsentry of the response object - the DICOMweb metadata endpoints (which OHIF uses), where it affects the set of tags in the response
Now I’m not really sure how the DICOMweb endpoints are affected because those
don’t differentiate between Study, Patient, Series or Instance level tags, they just return
a set of tags so I never really know under which section I should add a certain tag in order to affect the DICOMweb responses.
My assumption is that Orthanc merges the whole ExtraMainDicomTags list for the DICOMweb endpoints and tries to add all of them to the responses, is this true?