I have to develop a SCU (Service Class User) application for querying PACS and retrieve the DICOM images.
Should I use C-GET or C-MOVE DICOM protocol to retrieve the images?
The C-MOVE operation allows an application entity to instruct another application entity to transfer stored SOP Instances to another application entity using the C-STORE operation.
C-STORE. The most basic DICOM operation, otherwise known as “DICOM Push” allows an SCU to send a Composite Instance to an SCP. For instance, it is used to send images from a modality to PACS or create the delivery mechanism for C-MOVE.
Devices may be Service Class Provider (SCP) only, like a workstation in a physician's home that only receives images. Or they may have both User and Provider roles, such as an archive that can send as well as receive images. The User (SCU) typically initiates the communication, or sets up the Association.
DICOM Query/Retrieve allows for querying a database from an archive, workstation, or other device for the information it has available. It also allows for the retrieval ("pull") of those objects, such as images.
You can use either, but the preferred is C-Move.
The point is not only about security, but about implementation.
In C-MOVE, the SCP list the supported transfer syntaxes for each image matching the previous query. Then the SCU agree with any.
On the other side, in the C-GET, the SCU list its supporting transfer syntaxes before any query is made, and the SCP has to pick any and compromise to send whatever the SCU ask for in that format.
So, the C-GET implementation for PACS is harder and more complex since it has to be able to encode anything to anything. While in the C-MOVE is the client who has to be able to decode and show anything which is much easier...
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With