How does the SCU receive dcm images from Dicom Server with C-GET?

I've seen the official pynetdicom documentation but I've not got the proper event handlers (for the SCU) on receiving images.

First I've created the required .dcm files Dataset and used the C-GET command, which should actually give me the .dcm files but also I've not specified where my images are to be stored on the SCU. Do I need to use the C-MOVE command to actually get images or my code is incomplete (in a sense that no event handlers are specified for SCU onReceiveStore)?

from pydicom.dataset import Dataset
import pydicom

from pynetdicom import (
    AE, evt, build_role,

from pynetdicom.sop_class import (

ae = AE()


role = build_role(CTImageStorage, scp_role=True)

ds = Dataset()
ds.QueryRetrieveLevel = 'SERIES'
ds.PatientID = '0009703828'
ds.StudyInstanceUID = ''
ds.SeriesInstanceUID = ''

assoc = ae.associate('', 5678)

if assoc.is_established:

responses = assoc.send_c_get(ds, PatientRootQueryRetrieveInformationModelGet)
for (status,dataset) in responses:
    if status:
        print('C-GET query status: 0x{0:04x}'.format(status.Status))
        # If the status is 'Pending' then `identifier` is the C-GET response
        if status.Status in (0x0000, 0x1022):
            print('Connection timed out, was aborted or received invalid response') 

    print('Association rejected, aborted or never connected')

I expected the .dcm be sent from the DICOM server (i.e ConQuest server in my case) ,but I'm only receving the DICOM tag confirming that this Dataset (given as a query to the ConQuest Server) is present! I want to know exactly how do I receive the images on my SCU using this Application Entity (ae)

This is the response from the ConQuest Server

[CONQUESTSRV1] UPACS THREAD 11: STARTED AT: Fri Oct 25 06:56:23 2019
[CONQUESTSRV1]  Calling Application Title : "PYNETDICOM      "
[CONQUESTSRV1]  Called Application Title : "ANY-SCP         "
[CONQUESTSRV1]  Application Context : "1.2.840.10008.", PDU length: 16382
[CONQUESTSRV1]  Presentation Context 0 "1.2.840.10008." 1
[CONQUESTSRV1]  Presentation Context 1 "1.2.840.10008." 1
[CONQUESTSRV1] Number of images to send: 2
[CONQUESTSRV1] Sending file : c:\users\sagar\onedrive\desktop\dicomserver1419d1\data\0009703828\
[CONQUESTSRV1] [recompress]: recompressed with mode = un (strip=1)
[CONQUESTSRV1] C-Get (PatientRoot)
[CONQUESTSRV1] UPACS THREAD 11: ENDED AT: Fri Oct 25 06:56:23 2019

The ConQuest Server is sending the file but the SCU is unable to receive it!

findscu: DICOM query (C-FIND) SCU, peer hostname of DICOM peer port tcp/ip port number of peer dcmfile-in --max-​pdu [n]umber of bytes: integer (4096..131072) set max receive pdu to n This call queries a worklist server at host caesar for any planned procedures If multiple query files are provided, findscu will send multiple C-FIND requests to the SCP. The application contains the DICOM, HL7 services and interfaces that are required to provide storage, retrieval, and workflow to a healthcare environment. dcm4chee is pre-packaged and deployed within the JBoss application server.

Both C-GET and C-MOVE will cause the SCP to send back to your device a C-STORE command containing the dataset.

The difference between C-GET and C-MOVE is that C-MOVE will try to open a connection back to your device (which has to act also as an SCP to receive the C-STORE) while C-GET will send the C-STORE on the same connection negotiated by your device.

The response for the C-GET and C-MOVE contains just the status of the operation.

movescu: DICOM retrieve (C-MOVE) SCU, It will accept associations for the purpose of receiving images sent as a result of the The C-MOVE operation actually performs an image copy (no images will be of DICOM peer port tcp/ip port number of peer dcmfile-in DICOM query file(s) while movescu is playing the role of the storage server (i. e. the –port is used)  Take a look at the DICOM standard part 4, Annex C (and C.4.3.1 in particular for C-GET) which explains in more detail what the dataset used to match against should look like. There's not much testing of the assoc.send_c_get() / send_c_find() / send_c_move() parts of the code at the moment so if you run into anything strange don't hesitate to

You need to bind a callable handler function to evt.EVT_C_STORE as shown in this example.

Tool to execute a DICOM Query/Retrieve operation, --image C-FIND Query on Image Info. --key %d For example to send a C-ECHO to server using port 104, use: $ gdcmscu gdcmscu --store 104 myfile1.dcm myfile2.dcm myfile3.dcm . One should pay attention that gdcmscu --find and findscu are not completely equivalent. OsiriX HD supports DICOM C-Store SCU protocol. That means you can send DICOM images stored on your OsiriX HD database to any DICOM nodes, including another OsiriX HD iOS device, OsiriX for macOS, a DICOM viewer, or a PACS server. To send an entire DICOM series, simply display it in the Viewer.

How to Query PACS and get Images related to patients, How does the SCU receive dcm images from Dicom Server with C-GET? I've seen the official pynetdicom documentation but I've not got the proper event  Don't use DICOM reserved port 11112 for PDUDecoderTest to avoid conflict with running DICOM server applications #595 movescu: --cancel-after , --release-eager #596 getscu: --cancel-after #597

REQ: Download a DICOM from a Remote PACS · Issue #1 · pydicom , All I need to do is get a group of images related to a patient. Here are the And of course setup right config of DICOM server (i'm using Conquest for testing). Sign in to reply 2 wait for the PACS send the images to Local(using c-store scu) 3 handle the The images will be received at OnCStoreRequest at CStoreSCP file. Onis delivers the next evolution of DICOM Viewer/Server within a single integrated framework for the PC. Onis is a true end-to-end solution that includes advanced interactive annotations, Multi-planar reconstruction, 3D volume rendering, 'On-demand' access, DICOM networking, reporting, albums and access to images, annotations and reports from any location.

Storage Service Examples, scaramallion added documentation and removed C-GET labels on Apr 27, 2018 order to handle datasets received as a result of the C-GET Query/Retrieve request. error: the following arguments are required: peer, port, dcmfile-in server on which I can test code and download the images using pynetdicom. Server-client apps that can access DCM4CHEE Dicom images using WADO. The client has an image viewer that is capable of render 2D, 3D and MPR images from DICOM datasets. Based on DCM4CHE and ImageJ. Download Turyon Client and Server (View all files)