One of our clients is sending us a study which should have the tag 0002,0016. He even sent us a screenshot showing the tag is present. However, when I check the study, I can’t find it.
I checked with
Orthanc Explorer
/instances/{uuid}/metadata API
/instances/{uuid}/header API
but I’m unable to find that tag.
An old conversation on this forum makes me believe that Orthanc does something with it.
The problem is that the mode sends the tag “0002,0016” with the source AET, but after that study is sent to Orthanc this tag no longer exists.
Does Orthanc remove that tag or transform it into something else? The previous quote seems to say that the tag becomes the AET.
Orthanc does not modify or delete DICOM tags on its own.
For instance, here is a sample DICOM instance on our demo server, where you can see that both tags (0002,0016) SourceApplicationEntityTitle and (0008,0070) Manufacturer are present: Link to the DICOM instance.
This behavior most probably results from the configuration of your DICOM SCU. If this is not the case, you will have to provide a minimal working example for the Orthanc community to independently reproduce your issue.
Almost all our studies have the (0008,0070) Manufacturer tag, it’s only those from one client which never have it. Which seems to indicate that it’s specific to that client, not to us. I was more concerned about (0002,0016) SourceApplicationEntityTitle which I don’t remember seeing in the wild.
You mean like a block of code running on all C-MOVE events on the client software? In the same way we hook to the StableStudy event with Orthanc?