IdentifierDoesNotMatchSOPClass error

[Wonko]

Hi there!

Any idea what is the cause for this?

Code: Select all

findscu --study -k 0008,0052=STUDY -k "0010,0020=12345667" pacs 104
Response: Failed: IdentifierDoesNotMatchSOPClass

This happens for some patient IDs, while others produce the desired output withour error. The PACS is a CHILI pacs, based on dcmtk 3.5.3. The patient's id queried for is existing.

BTW, findscu returns with a status code of 0 (success). Is this a bug?

Here comes some more verbose output:

Code: Select all

Request Parameters:
Our Implementation Class UID:    1.2.826.0.1.3680043.2.596.0.2.2.1
Our Implementation Version Name: ATV_DICOM_220
Their Implementation Class UID:
Their Implementation Version Name:
Application Context Name:    1.2.840.10008.3.1.1.1
Calling Application Name:    MYAET
Called Application Name:     THEIRAET
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
Requesting Association
Constructing Associate RQ PDU
PDU Type: Associate Accept, PDU Length: 181 + 6 bytes PDU header
  02  00  00  00  00  b5  00  01  00  00  50  41  4e  53  59  53
  35  31  51  52  20  20  20  20  20  20  41  54  56  51  52  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  35  51  00  00  04  00  00  40  00  52  00
  00  16  31  2e  32  2e  32  37  36  2e  30  2e  32  33  2e  31
  2e  30  2e  33  2e  35  2e  33  55  00  00  0f  43  48  49  4c
  49  5f  44  43  4d  54  4b  5f  33  35  33
Association Parameters Negotiated:
Our Implementation Class UID:    1.2.826.0.1.3680043.2.596.0.2.2.1
Our Implementation Version Name: ATV_DICOM_220
Their Implementation Class UID:    1.2.276.0.23.1.0.3.5.3
Their Implementation Version Name: CHILI_DCMTK_353
Application Context Name:    1.2.840.10008.3.1.1.1
Calling Application Name:    MYAET
Called Application Name:     THEIRAET
Responding Application Name: THEIRAET
Our Max PDU Receive Size: 16384
Their Max PDU Receive Size: 16384
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
Association Accepted (Max Send PDV: 16372)
Find SCU RQ: MsgID 1
REQUEST:

# Dicom-Data-Set
# Used TransferSyntax: UnknownTransferSyntax
(0008,0052) CS [PATIENT]                                #   8, 1 QueryRetrieveLevel
(0010,0020) LO [12345667]                              #  10, 1 PatientID
--------
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 34 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 43264                                    #   2, 1 Status
C-Find RSP: MsgID: 1 [Status=Failed: IdentifierDoesNotMatchSOPClass]
  AffectedSOPClassUID: =FINDStudyRootQueryRetrieveInformationModel
  Data Set: Not Present
Releasing Association

[Jörg Riesmeier]

The debug output does not seem to match the command line: in the output the query level is PATIENT and on the command line it is STUDY. I guess this answers your question.

[Wonko]

Whoops. Sorry for this, I picked the wrong debug output after trying out the different information models.

But the output of the right command replacing PATIENT with STUDY in (0008,0052)) is just the same, apart from the change in (0008,0052) of course.

[Marco Eichelberg]

If you are performing your query in Study Root (--study), then I would think that your query is not well-formed since there is no PATIENT query level in that model. Include at least an empty Study Instance UID in your query.