I’d like the ability to add additional tags to be parsed by the Orthanc server upon reception of a DICOM instance. The way I’m accomplishing this is compiling after adding it to OrthancFramework/Sources/DicomFormat/DicomMap.cpp:
This method requires me to maintain a separate repo branch and rebase when there are Orthanc codebase updates, which makes it not ideal (from my perspective). Is there a better way to accomplish this? I would be able to develop a plugin for it if it’s something that’s available to the plugin API/extensibility.
Customizing the Dicom Tags that are stored in Database is something I’m going to work on very soon (in March-April). I still have to figure out how I will implement this but I’ll take your message into account when designing the feature.
I really look forward to the addition of that feature – thanks for providing an update! I have several additional DICOM patient tags that I add to that source file currently. That feature will definitely be a big help for me to have.
I’m confused as to how this is being implemented. I have ExtraMainDicomTags properly configured but I don’t know how to get access to the data.
My goal is to get access to additional patient tags upon every new patient/study pushed over through C-Store. I’m using the HTTP server RESTful API to query the studies and patients. I’m not showing any of the new data in the PatientMainDicomTags object returned by this API. I cannot figure out how to get access to any of the additional patient information.
Note that the ExtraMainDicomTags are added to the DB only for images that have been uploaded/received after you have set the configuration. You may use the Housekeeper plugin in order to reprocess older images.
You may also check that your configuration is taken into account correctly → this can be done by checking the /system route that now shows the list of indexed tags for each resource.
Then, the ExtraMainDicomTags shall be listed as any other MainDicomTags in the /patients/{id} route.
I’m not getting anything in the /system route that would indicate that the extra tags have been loaded. What should I see there? Here’s what my Orthanc.log is showing:
It seems to be accepting my extradicomtags.json file which I pasted in my previous message in this thread. However, my system route is outputting the following:
When I add the patient tags to OrthancFramework/Sources/DicomFormat/DicomMap.cpp and OrthancFramework/Sources/DicomFormat/DicomTag.h I do get the results that I need. However, it has been a hassle to maintain my fork of Orthanc, so I’d much rather use the config method. Additionally, do you know as if the addition patient tags will also appear in the /studies/{id} route inside the returned PatientMainDicomTags object or will they only appear in the /patients/{id} route once this is functioning properly through the config?
