I’ve only found old questions kind of related to this so my guess is “no” but I’m trying my luck anyway and, if it is not possible, would like to request the feature if possible.
I’m currently trying to replace a hospital’s internal PACS to Orthanc. It won’t be accessible externally at all, only internally from DICOM viewers installed on several workstations. However, ideally, none of these workstations would have static IP addresses, all provided by DHCP.
Furthermore, I’d like to leave them with eFilm’s default AE Title of “AETITLE” and port 104 without changing anything. I’ve seen some paid-for DICOM servers that permit query/retrieve without needing to know about a client. If I can limit it to only the local subnet, even better but unnecessary in my case.
So, is that possible in any way or am I going to have to go through reconfiguring every single station with static IPs and unique AE Titles, add the device in the Orthanc config and restart the Orthanc service every time?
The viewer first acts as a C-MOVE SCU (client) that contacts the PACS acting as a C-MOVE SCP (server). Then, once the PACS has retrieved the images, it becomes a C-STORE SCU (client) to send the images to the viewer that now acts as a C-STORE SCP (server).
This means that, for DICOM query/retrieve to work, the PACS (i.e. the Orthanc viewer) must know the AET and IP of all the viewers in the subnet. As a consequence, it is mandatory to list every single station in the configuration file of Orthanc.
@Michael: I don’t believe that applies to clients as I had already set it to false and the comments in the configuration file reads:
Check whether the called AET corresponds to the AET of Orthanc during an incoming DICOM SCU request
My assumption is that its really just about checking the server’s AE Title. For example, if a client calls for TestPacs instead of OrthancPacs as defined in the server’s AE Title but with the correct IP/Port, it won’t care that the called AE Title is different from the server’s configured AE Title.
@Sébastien: Thanks for the swift and helpful response, as always! Do you have any idea about some sort of ETA for C-GET (weeks vs months vs years)? I have absolutely no experience with REST and many other higher priority projects on the plate so depending on your answer, I might just add a dhcp reservation to my clients and configure them that way in the Orthanc Server until C-GET is implemented.
I have one question, now that C-get is available is it possible to retrieve images just by adding it to the viewer like radiant without adding AET, port or IP to orthanc? Thank you and your team for the effort as always.
Yes, this should be possible now, by defining one single modality in the configuration option “DicomModalities”, whose AET would be shared by all the viewers (the IP and port information is ignored for C-GET SCP).
C-GET SCP support is documented in the Orthanc Book at the following location:
