How to movescu a paticular study ID

[tchiang]

I can use movescu to C-MOVE studies belonging to a particular patient:

movescu -v -P -aem TEST01 -aec D100GEPACS -k 0008,0052=PATIENT -k 0010,0020="10668966" 100.200.240.169 4100

I got error message when I use the following comman to C-MOVE a particular study ID:
movescu -v -P -aem TEST01 -aec D100GEPACS -k 0008,0052=STUDY -k 0020,0010="6031500" 100.200.240.169 4100
Requesting Association
Association Accepted (Max Send PDV: 28660)
================================
Sending query
Move SCU RQ: MsgID 1
Request:

# Dicom-Data-Set
# Used TransferSyntax: UnknownTransferSyntax
(0008,0052) CS [STUDY] # 6, 1 QueryRetrieveLevel
(0020,0010) SH [6031500] # 8, 1 StudyID
C-Move RSP: MsgID: 1 [Status=Failed: IdentifierDoesNotMatchSOPClass]
AffectedSOPClassUID: =MOVEPatientRootQueryRetrieveInformationModel
Data Set: Not Present
Status Detail:

# Dicom-Data-Set
# Used TransferSyntax: LittleEndianImplicit
(0000,0901) AT (0008,0052)\(0010,0020)\(0020,000d) # 12, 3 OffendingElement
(0000,0902) LO [MOVE_REQUEST_IMPROPERLY_FORMATED] # 32, 1 ErrorComment
Releasing Association

I changed the command as the following but still get the same error message:
movescu -v -S -aem TEST01 -aec D100GEPACS -k 0008,0052=STUDY -k 0020,0010="6031500" 100.200.240.169 4100

The study ID is present and is correct. What are the correct options needed to C-MOVE a particular study ID?

Thanks.

[Michael Onken]

Hi,

for downloading a complete study you must provide a valid Patient ID as well as the Study Instance UID (not the Study ID).

Regards,
Michael

[Jörg Riesmeier]

... this is at least true for the Patient Root information model (option -P). For the Study Root information model (option -S), the Study Instance UID is sufficient.

[tchiang]

Thank you all. It is working now. I can use Study Instance UID to C-MOVE a particular study.

It brings me to another question. How can I C-MOVE images of a particular series (series-level) or only a particular image (image-level)?

Thanks a lot.

[Jörg Riesmeier]

You did not read the relevant sections of part 4 of the DICOM standard, right?

[tchiang]

No, I did not read the part 4 of the DICOM standard.

Is the part 4 of the DICOM standard relevant to my question? I did a google search on DICOM standard. This is what I found about the part 4 of DICOM standard:
http://www.barco.com/barcoview/download ... ard_v2.pdf

But I did not find the information I need.

Thanks.

[Jörg Riesmeier]

Download part 4 from the official site.

Is the part 4 of the DICOM standard relevant to my question?

Of course, this is where all the DICOM services are defined!

[tchiang]

We use movescu inside a while loop in a perl script to pre-fetch priors. In one of our tests, it took more than 20 hours to run. Among the processed studies, there are 21 studies with Status = Success studies, 16 with Status = Warning (SubOperationsCompleteOneOrMoreFailures) and 25 with Status = Refused (OutOfResourcesSubOperations). I found that it spent a lot of time in Status = Pending.
We have to improve the speed because the time it took is unacceptable. There are several approaches I have in my mind:

1. What is OutOfResourcesSubOperations error? Is it because the images are off-line? Can we detect it (for example using C-FIND) and skip the study or abandon the processing at early stage (before we spend a lot of time waiting for every image to be examined)?
2. Can we configure movescu to abandon processing if it has been pending for a specific amount of time (say 5 minutes)? Is –to option for this purpose? (In one of my testing case having only 4 images, it spent almost one hour in Status = Pending.)
3. Can we configure movescu to abandon processing if more than a specific percentage of the images (say 50%) fail? Can we use –pi or –pr option for this purpose? (Currently, it spends a long time to examine till the last images before it sends Status = Refused signal. It is extremely time wasting for some studies with hundreds of images.)
4. Execute movescu calls in the background (meaning add & at the end of the command line.) We don’t have to wait for the previous movescu to finish before we start another movescu. Unfortunately, this approach may reach beyond the maximum number of the association allowed on some of our DICOM devices.

Any other idea or thoughts are welcome too.
Thanks a lot.

[Jörg Riesmeier]

Please do not post the same message twice!

[tchiang]

Sorry. I thought it would have better chance to get response here because I did not get any response on other thread. I would delete the previous message if I could.