findscu problem
Cedric
query some working stations and receive DICOM files.
I use the DCMTK library and the binaries echoscu,findscu...
When i run storescp on my computer, i can "puch" files from working
stations to it.
But i have a problem with th findscu binary.
In fact, when i enter this comand :
findscu hostname 4006 -d --aetitle myaetitle --call aettitle --key
0010,0020=A1000000000 --patient --key 0008,0052=PATIENT --key
0010,0020
i have an error during the association :
Request Parameters:
Our Implementation Class UID: 1.2.276.0.7230010.3.0.3.5.2
Our Implementation Version Name: OFFIS_DCMTK_352
Their Implementation Class UID:
Their Implementation Version Name:
Application Context Name: 1.2.840.10008.3.1.1.1
Calling Application Name: myaetitle
Called Application Name: aetitle
Responding Application Name: resp AP Title
Our Max PDU Receive Size: 16384
Their Max PDU Receive Size: 0
Presentation Contexts:
Context ID: 1 (Proposed)
Abstract Syntax: =FINDPatientRootQueryRetrieveInformationModel
Proposed SCP/SCU Role: Default
Accepted SCP/SCU Role: Default
Proposed Transfer Syntax(es):
=LittleEndianExplicit
=BigEndianExplicit
=LittleEndianImplicit
Requested Extended Negotiation: none
Accepted Extended Negotiation: none
Constructing Associate RQ PDU
findscu: Association Rejected:
Result: Rejected Permanent, Source: Service User
Reason: No Reason
When i try with --study option i have this :
Request Parameters:
Our Implementation Class UID: 1.2.276.0.7230010.3.0.3.5.2
Our Implementation Version Name: OFFIS_DCMTK_352
Their Implementation Class UID:
Their Implementation Version Name:
Application Context Name: 1.2.840.10008.3.1.1.1
Calling Application Name: AERIS
Called Application Name: SHIVA
Responding Application Name: resp AP Title
Our Max PDU Receive Size: 16384
Their Max PDU Receive Size: 0
Presentation Contexts:
Context ID: 1 (Proposed)
Abstract Syntax: =FINDStudyRootQueryRetrieveInformationModel
Proposed SCP/SCU Role: Default
Accepted SCP/SCU Role: Default
Proposed Transfer Syntax(es):
=LittleEndianExplicit
=BigEndianExplicit
=LittleEndianImplicit
Requested Extended Negotiation: none
Accepted Extended Negotiation: none
Constructing Associate RQ PDU
PDU Type: Associate Accept PDU Length: 184
02 00 00 00 00 b2 00 01 00 00 53 48 49 56 41 20
20 20 20 20 20 20 20 20 20 20 41 45 52 49 53 20
20 20 20 20 20 20 20 20 20 20 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 10 00 00 15 31 2e
32 2e 38 34 30 2e 31 30 30 30 38 2e 33 2e 31 2e
31 2e 31 21 00 00 1b 01 00 00 00 40 00 00 13 31
2e 32 2e 38 34 30 2e 31 30 30 30 38 2e 31 2e 32
2e 31 50 00 00 32 51 00 00 04 00 00 70 00 52 00
00 14 31 2e 32 2e 38 34 30 2e 31 31 33 36 31 39
2e 36 2e 31 30 38 55 00 00 0e 41 57 34 5f 31 5f
30 36 5f 33 5f 45 58 54
Association Parameters Negotiated:
Our Implementation Class UID: 1.2.276.0.7230010.3.0.3.5.2
Our Implementation Version Name: OFFIS_DCMTK_352
Their Implementation Class UID: 1.2.840.113619.6.108
Their Implementation Version Name: AW4_1_06_3_EXT
Application Context Name: 1.2.840.10008.3.1.1.1
Calling Application Name: AERIS
Called Application Name: SHIVA
Responding Application Name: SHIVA
Our Max PDU Receive Size: 16384
Their Max PDU Receive Size: 28672
Presentation Contexts:
Context ID: 1 (Accepted)
Abstract Syntax: =FINDStudyRootQueryRetrieveInformationModel
Proposed SCP/SCU Role: Default
Accepted SCP/SCU Role: Default
Accepted Transfer Syntax: =LittleEndianExplicit
Requested Extended Negotiation: none
Accepted Extended Negotiation: none
DIMSE Command To Send:
# Dicom-Data-Set
# Used TransferSyntax: UnknownTransferSyntax
(0000,0000) UL 0 # 4, 1
CommandGroupLength
(0000,0002) UI =FINDStudyRootQueryRetrieveInformationModel # 28, 1
AffectedSOPClassUID
(0000,0100) US 32 # 2, 1
CommandField
(0000,0110) US 1 # 2, 1
MessageID
(0000,0700) US 2 # 2, 1
Priority
(0000,0800) US 1 # 2, 1
DataSetType
DIMSE sendDcmDataset: sending 88 bytes
DIMSE sendDcmDataset: sending 36 bytes
DIMSE receiveCommand
DIMSE receiveCommand: 1 pdv's (88 bytes), presID=1
DIMSE Command Received:
# Dicom-Data-Set
# Used TransferSyntax: LittleEndianImplicit
(0000,0002) UI =FINDStudyRootQueryRetrieveInformationModel # 28, 1
AffectedSOPClassUID
(0000,0100) US 32800 # 2, 1
CommandField
(0000,0120) US 1 # 2, 1
MessageIDBeingRespondedTo
(0000,0800) US 257 # 2, 1
DataSetType
(0000,0900) US 49153 # 2, 1
Status
Response: Failed: UnableToProcess
Could you help me please ?
Sorry if this message is a bit long but i try to give you all the
informations i can.
Thanks for your help.
Cedric
know how to use findscu.
a new error message :
findscu -v -S -aec SHIVA -aet AERIS -k 0008,0052=STUDY -k
0010,0040="M" shiva 4006
Requesting Association
Association Accepted (Max Send PDV: 28660)
Find SCU RQ: MsgID 1
REQUEST:
# Dicom-Data-Set
# Used TransferSyntax: UnknownTransferSyntax
(0008,0052) CS [STUDY] # 6, 1
QueryRetrieveLevel
(0010,0040) CS [M] # 2, 1
PatientsSex
--------
C-Find RSP: MsgID: 1 [Status=Failed: IdentifierDoesNotMatchSOPClass]
AffectedSOPClassUID: =FINDStudyRootQueryRetrieveInformationModel
Data Set: Not Present
Releasing Association
Could you help me, please? (the echoscu has a succes status and i
manage to move images with this command when i know the Patient ID :
movescu -d -aet AERIS -aec SHIVA -P -k 0008,0052=PATIENT -k
0010,0020=A100100000 +P 4006 192.168.56.30 4006
Joerg Riesmeier
> i don't know if the problem is the GE working station or me who
> don't know how to use findscu.
It seems that your problem is more related to the DICOM standard,
i.e. possibly you did not really understand what the different
query information models are for. Therefore, I would suggest
that you first read annex C of part 4 of the DICOM standard where
the Query/Retrieve Service Class is described in details.
Then I would recommend that you check which information models
and query keys are supported by the SCP (read the conformance
statement of the application). For example: PatientsSex
(0010,0040) is an optional key in the Study Root model.
Btw, working examples of how to use findscu can be found in both
the documentation of the tool (findscu.txt) and this newsgroup.
Regards,
Joerg Riesmeier
OFFIS
Dominick Anggara
From the log, the problem is that you are trying to query tag that
not supported at STUDY Level Query SOP Class which is
Patient Sex (0010,0040)="M".
Try to use Study level query such as Study Date, Study ID, Accession
Number or unique Study Instance UID. If you want to use Patient Sex as
your query identifier, try to use PATIENT ROOT Level.
You CMOVE request is successful because you use PATIENT Level Root
with specified PATIENT ID.
I don't have find_scu/move_scu utitity to test it.
Let me know if my comments help.
Dominick Anggara
Integration Engineer
PointDx, Inc.
Cedric
conformance statement that the App. Entity provides only Study Root
Query/Retrieve Inf. model -FIND that is to say SOP Class
1.2.840.10008.5.1.4.1.1.2.2.1 .
Dominick said that it may be the tag. But i tried this command with
studydate :
findscu -v -aet AERIS -aec SHIVA -S -k 0008,0052=STUDY -k
0008,0020="20040505" shiva 4006
or this command with StudyID :
findscu -v -aet AERIS -aec SHIVA -S -k 0008,0052=STUDY -k
0020,0010="839" shiva 4006
an i always have the same response :
Requesting Association
Association Accepted (Max Send PDV: 28660)
Find SCU RQ: MsgID 1
REQUEST:
# Dicom-Data-Set
# Used TransferSyntax: UnknownTransferSyntax
(0008,0052) CS [STUDY] # 6, 1
QueryRetrieveLevel
(0020,0010) SH [839] # 4, 1
StudyID
--------
C-Find RSP: MsgID: 1 [Status=Failed: IdentifierDoesNotMatchSOPClass]
AffectedSOPClassUID: =FINDStudyRootQueryRetrieveInformationModel
Data Set: Not Present
Releasing Association
thanks for your help.
mrmich...@gmail.com
You're calling...
findscu -v -aet AERIS -aec SHIVA -S -k 0008,0052=STUDY -k 0020,0010="839" shiva 4006
findscu -v -S -k 0008,0052=STUDY -k 0020,0010="839" -aet AERIS -aec SHIVA shiva 4006
My succesful ones look something like this...
findscu.exe -S -k 0008,0052="IMAGE" -k 0008,0050="<insert accession number here>" <my PACS server> <my PACS server port> -aet <my target AE Title> -aec <my calling AE Title>