Retrieve instances via DIMSE C-MOVE
Pull a study from an archive that only knows how to send it back to you.
Desktop app only, 1.6.0 or newerdcmage pro
Problem
Plenty of archives do not answer a C-GET. The retrieval service they offer is C-MOVE, which does not return the instances on the association that asked for them: the archive opens a second association back to a destination AE title it has been configured to resolve, and stores the instances there. So the workstation has to be that destination (it has to listen) and an application that refuses to listen simply cannot read a study off such an archive.
Steps
-
Pick the retrieval service when you connect. A DIMSE connection defaults to C-GET, which needs nothing open on your machine. Choose C-MOVE and the form asks for the one thing the archive needs from you: the port it should send to. It also names the calling AE title the archive must be configured to route there, because that is the value it will address the callback to.
-
Open a study from the search results. Each instance is retrieved by sending a C-MOVE and accepting the archive’s callback. The port opens for that retrieval and closes with it. There is no service left running between studies, and none at all if you use C-GET.
-
Work in the ordinary editor. The instances arrive as the same Part 10 files a C-GET produces, so the tag editor, the undo timeline, the viewport tools, and the provenance badge behave exactly as they do for any other study.
The listener accepts the same compressed formats a C-GET asks for, plus a few more, so a study the archive stores compressed arrives as it was stored.
What the listener will accept
Only the archive you connected to, and only what you asked for. DICOM’s credential is the AE title, and both directions of it were agreed when you connected: the callback has to be addressed to this application’s calling AE title and has to introduce itself as the archive’s called AE title, or it is refused during negotiation, before it can send a byte. An instance that arrives under a SOP Instance UID other than the one requested is acknowledged (an archive that gets no response counts the whole retrieval failed) and then discarded rather than passed on as the study you asked for.
One retrieval holds the port at a time. The archive was configured to send to a single number, so two retrievals at once would be two binds of one address; they queue instead.
What this is not
It is not an inbound service. There is nothing to send a study to when no retrieval is in flight, and nothing that accepts a study nobody asked for.
Result
A study on an archive that offers only C-MOVE opens in the normal editing workspace, and the port that made it possible was open for the seconds the transfer took.