Tags

Google Groups archive
1

Hi guys!

this is our environment:
OS: Ubuntu 20.04
Dicom Server: Orthanc 1.11
DB: PostgreSQL 13.3
Plugins: S3-storage , PostgreSQL 4.0, Dicom-web 1.8

We need to add these two tags 0032,4000 ; 4008,0212 in the ExtraMainDicomTags section, when I do the query with Osirix it will look for those tags in the studies inside the buckets3 and it makes the query too slow.
We added the tag 0032,400 to the ExtraMainDicomTags section but it is ignoring it. On the other hand, the tag 4008,0212 when we add it to the Configuration.json does not allow us to start Orthanc

W0606 14:33:40.656021 main.cpp:2006] Orthanc version: 1.11.0
W0606 14:33:40.656423 OrthancConfiguration.cpp:56] Reading the configuration from: “./Configuration.json”
W0606 14:33:40.708493 FromDcmtkBridge.cpp:380] Loading external DICOM dictionary: “/usr/share/libdcmtk12/dicom.dic”
W0606 14:33:40.745118 FromDcmtkBridge.cpp:380] Loading external DICOM dictionary: “/usr/share/libdcmtk12/private.dic”
E0606 14:33:40.777990 main.cpp:2063] Uncaught exception, stopping now: [Unknown DICOM tag] (code 27)
W0606 14:33:40.778134 main.cpp:2094] Orthanc has stopped

Thanks!

2

To add more information on this issue:

This is our actual Configuration properties:

“ExtraMainDicomTags” : {
“Instance” : [
“Rows”,
“Columns”,
“ImageType”,
“SOPClassUID”,
“ContentDate”,
“ContentTime”,
“FrameOfReferenceUID”,
“PixelSpacing”,
“SpecificCharacterSet”,
“BitsAllocated”,
“BitsStored”,
“TransferSyntaxUID”,
“StudyComments”,
“Timezone​ffset​FomUTC”
],
“Series” : [
“TimezoneOffsetFromUTC”,
“PerformedProcedureStepStartDate”,
"StudyComments",
“PerformedProcedureStepStartTime”
],
“Study”: [
“TimezoneOffsetFromUTC”,
“StudyComments”,
“PerformingPhysicianName”,
“TransferSyntaxUID”
//“InterpretationStatusID”
],
“Patient”: [
“StudyComments”
]
},

“Warnings” : {
“W001_TagsBeingReadFromStorage”: true,
“W002_InconsistentDicomTagsInDb”: true
},

We added “StudyComments” on each type, because even that we add it, it is still looking for it:

I0606 20:34:36.233253 PluginsManager.cpp:161] (plugins) [S3] GET: 2a9e8d23-5d91-4001-b486-d217284476b8
I0606 20:34:36.263545 PluginsManager.cpp:161] (plugins) [S3] GET 2a9e8d23-5d91-4001-b486-d217284476b8 finished in 30288us
W0606 20:34:36.292462 ServerContext.cpp:2424] W001: Accessing Dicom tags from storage when accessing study : 0032,4000;4008,0212

Apart from that, DICOM tag “InterpretationStatusID” 4008,0212 is not being supported by Orthanc, when we add it orthanc does not start and it shows the error presented before ([Unknown DICOM tag]), i dont know if its easy to add it somehow (we cannot add it to the “Dictionary” property because its not an odd number, we tried that unsuccessfully)

Thanks

3

Hi,

InterpretationStatusID is retired therefore, its alias has changed to RETIRED_InterpretationStatusID: https://github.com/DCMTK/dcmtk/blob/master/dcmdata/data/dicom.dic#L4981.
You may use 4008,0212 instead of its alias.

For the StudyComments, can you identify which request Osirix is performing at the time you observe the issue ?

Best regards,

Alain.

4

https://github.com/DCMTK/dcmtk/blob/master/dcmdata/data/dicom.dic#L4771 StudyComments seems to be retired as well. You should use its numerical IDs as well.

HTH

Alain.

5

Thanks for the clarification on the alias! We didn’t know we could use the hex numbers instead of aliases.

Regarding your other question, this is the query being run by osirix (we tcpdumped the query):

GET /dicom-web/studies?StudyDate=20220525-&includefield=00080020&includefield=00080030&includefield=00080050&includefield=00080061&includefield=00080080&includefield=00080090&includefield=00081030&includefield=00081050&includefield=00100010&includefield=00100020&includefield=00100030&includefield=00100040&includefield=0020000D&includefield=00200010&includefield=00201208&includefield=00324000&includefield=40080212&includefield=00020010

It matches Orthanc logs though

I0606 20:34:31.314133 PluginsManager.cpp:161] (plugins) Body of the call from QIDO-RS to /tools/find: {
“Expand” : true,
“Full” : true,
“Level” : “Study”,
“Limit” : 0,
“Query” :
{
“0008,0020” : “20220606-”
},
“RequestedTags” :
[
“0002,0010”,
“0008,0020”,
“0008,0030”,
“0008,0050”,
“0008,0056”,
“0008,0061”,
“0008,0080”,
“0008,0090”,
“0008,0201”,
“0008,1030”,
“0008,1050”,
“0010,0010”,
“0010,0020”,
“0010,0030”,
“0010,0040”,
“0020,000d”,
“0020,0010”,
“0020,1206”,
“0020,1208”,
“0032,4000”,
“4008,0212”
],
“Since” : 0
}

6

Thanks again. We will be setting this up tonight after hours and I will let you know if that works.

7

It worked. Thank you very much for your quick response.

Regards.-