Multiple value on the same tag movescu

Message

AlbertoSP · #1 Post by **AlbertoSP** » Tue, 2018-07-03, 16:16

Hi, i want to retrieve on a unique query two or more Studies providing the uid.
Something like findscu with the separator \. For example, this query works fine using dcmtk + orthanc:

findscu localhost 4242 -k StudyInstanceUID="1.3.6.1.4.1.14519.5.2.1.4334.1501.305837811806532074576487712656\1.3.6.1.4.1.14519.5.2.1.4334.1501.195431795666397384281132633112" -S -aet FINDSCU -k QueryRetrieveLevel="STUDY"

but when i try this, i received an erro unable to process:

movescu localhost 4242 -k StudyInstanceUID="1.3.6.1.4.1.14519.5.2.1.4334.1501.305837811806532074576487712656\1.3.6.1.4.1.14519.5.2.1.4334.1501.195431795666397384281132633112" -aet FINDSCU +P 10 -P

Can anyone help providing me some example or any other way?

J. Riesmeier · #2 Post by **J. Riesmeier** » Tue, 2018-07-03, 20:09

There are two issues with your movescu call:

The QueryRetrieveLevel is missing (in your case: -k QueryRetrieveLevel="STUDY").
The unique key for the top-level (PATIENT) is missing, i.e. you have to add: -k PatientID=<some-id>

Instead of 2., you might also want to remove the -P from your command line, which selects the Patient Root Q/R Information Model.

AlbertoSP · #3 Post by **AlbertoSP** » Wed, 2018-07-04, 06:51

Thanks for your answer.
I've tried what you wrote but the movescu still not working.

J. Riesmeier · #4 Post by **J. Riesmeier** » Thu, 2018-07-05, 15:58

In order to help you, I would need more technical details than "still not working". Could you post the error message or even the log output (in debug mode)?

AlbertoSP · #5 Post by **AlbertoSP** » Thu, 2018-07-05, 19:23

Oh yeah, sorry.
Orthanc error is this:

I0705 20:19:39.324704 OrthancMoveRequestHandler.cpp:187] (0020,000d) StudyInstanceUID = 1.3.6.1.4.1.14519.5.2.1.4334.1501.305837811806532074576487712656\1.3.6.1.4.1.14519.5.2.1.4334.1501.195431795666397384281132633112
E0705 20:19:39.851018 MoveScp.cpp:192] IMoveRequestHandler Failed: Bad request
I0705 20:19:39.921340 CommandDispatcher.cpp:892] DUL Peer Requested Release
I0705 20:19:39.922844 CommandDispatcher.cpp:899] Association Release

Movescu:
I:
D: DcmDataset::read() TransferSyntax="Little Endian Implicit"
W: Move response with error status (Failed: UnableToProcess)
I: Received Final Move Response
D: ===================== INCOMING DIMSE MESSAGE ====================
D: Message Type : C-MOVE RSP
D: Message ID Being Responded To : 1
D: Affected SOP Class UID : MOVEPatientRootQueryRetrieveInformationModel
D: Remaining Suboperations : none
D: Completed Suboperations : 0
D: Failed Suboperations : 0
D: Warning Suboperations : 0
D: Data Set : none
D: DIMSE Status : 0xc000: Error: Failed - Unable to process
D: ======================= END DIMSE MESSAGE =======================
I: Releasing Association

Both of studies are in the db (check using movescu command with both uid individually, worked fine).

J. Riesmeier · #6 Post by **J. Riesmeier** » Thu, 2018-07-05, 20:30

What does your C-FIND request look like?

AlbertoSP · #7 Post by **AlbertoSP** » Thu, 2018-07-05, 20:37

findscu localhost 4242 -k StudyInstanceUID="1.3.6.1.4.1.14519.5.2.1.4334.1501.305837811806532074576487712656\1.3.6.1.4.1.14519.5.2.1.4334.1501.195431795666397384281132633112" -S -aet FINDSCU -k QueryRetrieveLevel="STUDY"

I: ---------------------------
I: Find Response: 1 (Pending)
I:
I: # Dicom-Data-Set
I: # Used TransferSyntax: Little Endian Explicit
I: (0008,0005) CS [ISO_IR 100] # 10, 1 SpecificCharacterSet
I: (0008,0052) CS [STUDY ] # 6, 1 QueryRetrieveLevel
I: (0020,000d) UI [1.3.6.1.4.1.14519.5.2.1.4334.1501.195431795666397384281132633112] # 64, 1 StudyInstanceUID
I:
I: ---------------------------
I: Find Response: 2 (Pending)
I:
I: # Dicom-Data-Set
I: # Used TransferSyntax: Little Endian Explicit
I: (0008,0005) CS [ISO_IR 100] # 10, 1 SpecificCharacterSet
I: (0008,0052) CS [STUDY ] # 6, 1 QueryRetrieveLevel
I: (0020,000d) UI [1.3.6.1.4.1.14519.5.2.1.4334.1501.305837811806532074576487712656] # 64, 1 StudyInstanceUID

J. Riesmeier · #8 Post by **J. Riesmeier** » Thu, 2018-07-05, 20:40

And the C-MOVE request?

AlbertoSP · #9 Post by **AlbertoSP** » Thu, 2018-07-05, 20:42

movescu localhost 4242 -k StudyInstanceUID="1.3.6.1.4.1.14519.5.2.1.4334.1501.305837811806532074576487712656\1.3.6.1.4.1.14519.5.2.1.4334.1501.195431795666397384281132633112" -aet FINDSCU +P 10 -k QueryRetrieveLevel="STUDY" -k PatientID="GSM714044" -d

D: $dcmtk: movescu v3.6.3 2018-02-05 $
D:
D: Request Parameters:
D: ====================== BEGIN A-ASSOCIATE-RQ =====================
D: Our Implementation Class UID: 1.2.276.0.7230010.3.0.3.6.3
D: Our Implementation Version Name: OFFIS_DCMTK_363
D: Their Implementation Class UID:
D: Their Implementation Version Name:
D: Application Context Name: 1.2.840.10008.3.1.1.1
D: Calling Application Name: FINDSCU
D: Called Application Name: ANY-SCP
D: Responding Application Name: ANY-SCP
D: Our Max PDU Receive Size: 16384
D: Their Max PDU Receive Size: 0
D: Presentation Contexts:
D: Context ID: 1 (Proposed)
D: Abstract Syntax: =FINDPatientRootQueryRetrieveInformationModel
D: Proposed SCP/SCU Role: Default
D: Proposed Transfer Syntax(es):
D: =LittleEndianExplicit
D: =BigEndianExplicit
D: =LittleEndianImplicit
D: Context ID: 3 (Proposed)
D: Abstract Syntax: =MOVEPatientRootQueryRetrieveInformationModel
D: Proposed SCP/SCU Role: Default
D: Proposed Transfer Syntax(es):
D: =LittleEndianExplicit
D: =BigEndianExplicit
D: =LittleEndianImplicit
D: Requested Extended Negotiation: none
D: Accepted Extended Negotiation: none
D: Requested User Identity Negotiation: none
D: User Identity Negotiation Response: none
D: ======================= END A-ASSOCIATE-RQ ======================
I: Requesting Association
D: setting network send timeout to 60 seconds
D: setting network receive timeout to 60 seconds
D: Constructing Associate RQ PDU
D: PDU Type: Associate Accept, PDU Length: 217 + 6 bytes PDU header
D: 02 00 00 00 00 d9 00 01 00 00 41 4e 59 2d 53 43
D: 50 20 20 20 20 20 20 20 20 20 46 49 4e 44 53 43
D: 55 20 20 20 20 20 20 20 20 20 00 00 00 00 00 00
D: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
D: 00 00 00 00 00 00 00 00 00 00 10 00 00 15 31 2e
D: 32 2e 38 34 30 2e 31 30 30 30 38 2e 33 2e 31 2e
D: 31 2e 31 21 00 00 1b 01 00 00 00 40 00 00 13 31
D: 2e 32 2e 38 34 30 2e 31 30 30 30 38 2e 31 2e 32
D: 2e 31 21 00 00 1b 03 00 00 00 40 00 00 13 31 2e
D: 32 2e 38 34 30 2e 31 30 30 30 38 2e 31 2e 32 2e
D: 31 50 00 00 3a 51 00 00 04 00 00 40 00 52 00 00
D: 1b 31 2e 32 2e 32 37 36 2e 30 2e 37 32 33 30 30
D: 31 30 2e 33 2e 30 2e 33 2e 36 2e 32 55 00 00 0f
D: 4f 46 46 49 53 5f 44 43 4d 54 4b 5f 33 36 32
D: Parsing an A-ASSOCIATE PDU
D: Association Parameters Negotiated:
D: ====================== BEGIN A-ASSOCIATE-AC =====================
D: Our Implementation Class UID: 1.2.276.0.7230010.3.0.3.6.3
D: Our Implementation Version Name: OFFIS_DCMTK_363
D: Their Implementation Class UID: 1.2.276.0.7230010.3.0.3.6.2
D: Their Implementation Version Name: OFFIS_DCMTK_362
D: Application Context Name: 1.2.840.10008.3.1.1.1
D: Calling Application Name: FINDSCU
D: Called Application Name: ANY-SCP
D: Responding Application Name: ANY-SCP
D: Our Max PDU Receive Size: 16384
D: Their Max PDU Receive Size: 16384
D: Presentation Contexts:
D: Context ID: 1 (Accepted)
D: Abstract Syntax: =FINDPatientRootQueryRetrieveInformationModel
D: Proposed SCP/SCU Role: Default
D: Accepted SCP/SCU Role: Default
D: Accepted Transfer Syntax: =LittleEndianExplicit
D: Context ID: 3 (Accepted)
D: Abstract Syntax: =MOVEPatientRootQueryRetrieveInformationModel
D: Proposed SCP/SCU Role: Default
D: Accepted SCP/SCU Role: Default
D: Accepted Transfer Syntax: =LittleEndianExplicit
D: Requested Extended Negotiation: none
D: Accepted Extended Negotiation: none
D: Requested User Identity Negotiation: none
D: User Identity Negotiation Response: none
D: ======================= END A-ASSOCIATE-AC ======================
I: Association Accepted (Max Send PDV: 16372)
I: Sending Move Request
D: ===================== OUTGOING DIMSE MESSAGE ====================
D: Message Type : C-MOVE RQ
D: Presentation Context ID : 3
D: Message ID : 1
D: Affected SOP Class UID : MOVEPatientRootQueryRetrieveInformationModel
D: Data Set : present
D: Priority : medium
D: Move Destination : FINDSCU
D: ======================= END DIMSE MESSAGE =======================
I: Request Identifiers:
I:
I: # Dicom-Data-Set
I: # Used TransferSyntax: Little Endian Explicit
I: (0008,0052) CS [STUDY] # 6, 1 QueryRetrieveLevel
I: (0010,0020) LO [GSM714044] # 10, 1 PatientID
I: (0020,000d) UI [1.3.6.1.4.1.14519.5.2.1.4334.1501.305837811806532074576487712656\1.3.6.1.4.1.14519.5.2.1.4334.1501.195431795666397384281132633112] # 130, 2 StudyInstanceUID
I:
D: DcmDataset::read() TransferSyntax="Little Endian Implicit"
W: Move response with error status (Failed: UnableToProcess)
I: Received Final Move Response
D: ===================== INCOMING DIMSE MESSAGE ====================
D: Message Type : C-MOVE RSP
D: Message ID Being Responded To : 1
D: Affected SOP Class UID : MOVEPatientRootQueryRetrieveInformationModel
D: Remaining Suboperations : none
D: Completed Suboperations : 0
D: Failed Suboperations : 0
D: Warning Suboperations : 0
D: Data Set : none
D: DIMSE Status : 0xc000: Error: Failed - Unable to process
D: ======================= END DIMSE MESSAGE =======================
I: Releasing Association

J. Riesmeier · #10 Post by **J. Riesmeier** » Thu, 2018-07-05, 20:56

Does it work if you omit the key "PatientID" (which is not allowed for a C-MOVE request in Study Root Q/R Information Model, only in Patient Root Q/R Information Model):

Code: Select all

movescu localhost 4242 -k StudyInstanceUID="1.3.6.1.4.1.14519.5.2.1.4334.1501.305837811806532074576487712656\1.3.6.1.4.1.14519.5.2.1.4334.1501.195431795666397384281132633112" -aet FINDSCU +P 10 -k QueryRetrieveLevel="STUDY" -d

AlbertoSP · #11 Post by **AlbertoSP** » Thu, 2018-07-05, 20:58

Still "Error: Failed - Unable to process"

J. Riesmeier · #12 Post by **J. Riesmeier** » Thu, 2018-07-05, 20:59

I tested a similar request with DCMTK's dcmqrscp: it worked.

DICOM @ OFFIS

Multiple value on the same tag movescu

Multiple value on the same tag movescu

Re: Multiple value on the same tag movescu

Re: Multiple value on the same tag movescu

Re: Multiple value on the same tag movescu

Re: Multiple value on the same tag movescu

Re: Multiple value on the same tag movescu

Re: Multiple value on the same tag movescu

Re: Multiple value on the same tag movescu

Re: Multiple value on the same tag movescu

Re: Multiple value on the same tag movescu

Re: Multiple value on the same tag movescu

Re: Multiple value on the same tag movescu

Who is online