DVTk (Main) :: Forum

Re: Validation Error [by Timmy]

Fri, 08 Jun 2012 14:13:33 +0200

Query Retrieve SCP Emulator:: Validation Error
I'll give this one more shot, and hope for a reply.

A bit of description on what I am doing. I am trying to use the QR SCP Emulator to test an application that will communicate with a PACs system. I am using a C-Find with a PatientIOD. I am wanting to search by AccessionNumber and PatientID right now, but I am also including the StudyInstanceUID and SeriesInstanceUID, because the QR SCP Emulater gave me an error when I left it off.

For my communication, I am using the following:

List<TransferSyntax> tsns = new
List<TransferSyntax>();
tsns.Add(WellKnownTSNs.ImplicitVrLittleEndian);
tsns.Add(WellKnownTSNs.ExplicitVrLittleEndian);
tsns.Add(WellKnownTSNs.ExplicitVrBigEndian);

List<AbstractSyntax> ts = new List<AbstractSyntax>();
ts.Add(WellKnownASNs.MammographyCADStructuredReport);

The issue that I am having is that my searches are coming up with 0 results, even though the parameters I am using are copied directly from the DICOM so I know there is not an error. I have tried with three different DICOMs in my model, and none of them are being found.

I began removing information, and found that when I sent a search with an empty string for all four fields, I finally got 12 results. This is a bit strange since I have 30 DICOMs in the model.

Could I have set up DVTk wrong, or does it sound like there is an error in my code. Or perhaps I am trying to use the QR SCP Emulator in a way that it is not meant to be used.

Any response would be appreciated.

Re: Image Level Finds [by marcokemper]

Thu, 19 Apr 2012 07:20:18 +0200

Query Retrieve SCP Emulator:: Image Level Finds

Hi Bob,

if you can send me the detailed validation results of the QR SCP Emulator when querying the default data set, I will try to figure out if the problem is SCU and/or SCP related. You can find the detailed validation results under the menu "Stored Files\Explore Validation Results...". Please put these in a zip file and attach it to a reply on this topic.

Regards,
Marco

Re: help me [by satish]

Mon, 18 Jul 2011 09:43:04 +0200

Query Retrieve SCP Emulator:: help me
Hi,

The issue seems very specific to your environment.Did you try installing the emulator on another machine(with a different OS)?

Move SCP conformance. [by zaq]

Fri, 27 May 2011 20:40:54 +0200

Query Retrieve SCP Emulator:: Move SCP conformance.
I have questions regarding C-MOVE SCP functionality of the Q/R emulator. I use version 4.0.2 of the software and there are two things that have caught my attention.

Please have a look at the following fragment of a log from a move operation, that was supposed to transfer 8 instances. Since I hadn't yet started storage SCP, they all failed. Here's how the final response looked like:


C-MOVE-RSP
(0x00000000,"0x00000074") # Group 0000 Length
(0x00000002,"1.2.840.10008.5.1.4.1.2.1.2") # Affected SOP Class UID
(0x00000100,"0x8021") # Command Field
(0x00000120,"0x0001") # Message ID Being Responded To
(0x00000800,"0x0101") # Data Set Type
(0x00000900,"0xB000") # Status
(0x00001020,"0x0000") # Number of Remaining Sub-operations
(0x00001021,"0x0000") # Number of Complete Sub-operations
(0x00001022,"0x0008") # Number of Failed Sub-operations
(0x00001023,"0x0000") # Number of Warning Sub-operations

1. Data Set Type.

According to part four of the DICOM standard, section C.4.2.1.4.2, every final but non-Success response, namely: Canceled, Warning, Refused or Failure, should contain an identifier with exactly one tag: Failed SOP Instance UID List. That's reasonable enough -- we need to know what instances weren't successfully stored. However, Q/R emulator doesn't appear to obey that: the data set type indicates no identifier.

2. Status.

Once again, having read the section C.4.2.3.1 of the aforementioned part of DICOM, I would expect that since all 8 instances were not stored, the status should be either Failure or Refused. That doesn't seem to be the case, the value of 0xb000 means a warning: Sub-operations complete, one or more failures.

Are these errors or is there something I'm missing?

Paweł

Re: Level-based validation conditions [by MGMC]

Wed, 18 May 2011 10:22:38 +0200

Query Retrieve SCP Emulator:: Level-based validation conditions
>>>Obviously the definition files are wrong --

> Ans: Definition files are never wrong you just
> have understand how they are structured. I need
> more specifics on your problem before I can help you.

True statement.
I managed to get it running as expected some days ago,
but I can't recall what I did....
Most likely I reverted back to the older definition files.

The header of "Patient Root Query-Retrieve Information Model - Find.def" gives:

# DVTk Defintion File created on 10-11-2010 15:33:47 #

Is that the new or old one ?

>Ans: There is no CFINDRQ Dimse Command in the
> definition file. I believe it is C-FIND-RQ.
> Try this and it should get you further.

Not sure what I shall try here... The text "CFINDRQ" is not
a part of my DICOM message since the message is defined
via Command Field (value 0x0020).
Here is what the emulator receives and prints:

Received:
C-FIND-RQ
(0x00000000,"0x0000004C") # Group 0000 Length
(0x00000002,"1.2.840.10008.5.1.4.1.2.2.1") # Affected SOP Class UID
(0x00000100,"0x0020") # Command Field
(0x00000110,"0x0001") # Message ID
(0x00000700,"0x0000") # Priority
(0x00000800,"0x0000") # Data Set Type

(0x00080020,"") # Study Date
(0x00080052,"STUDY ") # Query/Retrieve Level
(0x00081030,"* ") # Study Description
(0x00100010,"* ") # Patient's Name
(0x00100020,"") # Patient ID
(0x00100030,"") # Patient's Birth Date
(0x00100040,"") # Patient's Sex
(0x00101000,"") # Other Patient IDs
(0x0020000D,"") # Study Instance UID

... Dicom message with Dimse Command CFINDRQ received.
Skipping definition file validation: unable to find correct definition file for Dimse Command "CFINDRQ" and SOP Class UID "1.2.840.10008.5.1.4.1.2.2.1".
Link to Summary Result
DISPLAY: Command Set attributes
(0x00000000,"0x0000004C") # Group 0000 Length
(0x00000002,"1.2.840.10008.5.1.4.1.2.2.1") # Affected SOP Class UID
(0x00000100,"0x0020") # Command Field
(0x00000110,"0x0001") # Message ID
(0x00000700,"0x0000") # Priority
(0x00000800,"0x0000") # Data Set Type
Data Set attributes
(0x00080020,"") # Study Date
(0x00080052,"STUDY ") # Query/Retrieve Level
(0x00081030,"* ") # Study Description
(0x00100010,"* ") # Patient's Name
(0x00100020,"") # Patient ID
(0x00100030,"") # Patient's Birth Date
(0x00100040,"") # Patient's Sex
(0x00101000,"") # Other Patient IDs
(0x0020000D,"") # Study Instance UID

...

Still no idea how to fix that. Needless to say that
the def file "Study Root Query-Retrieve Information Model - Find.def" exists - if that file is needed.

Kind regards

Marcus

Re: import dicom files [by silkduvets]

Fri, 18 Feb 2011 02:36:50 +0200

Query Retrieve SCP Emulator:: import dicom files
Why I can't download it.

Re: Querying for series doesn't work [by rsibilio]

Fri, 19 Nov 2010 13:31:57 +0200

Query Retrieve SCP Emulator:: Querying for series doesn't work
Hi Emiliano,

I think my first suggestion would be to use the DICOM Network Analyzer (if you are not familiar it is available for download from this site). The reason I am suggesting the DICOM Network analyzer is to confirm the messages and tags that are being sent and received from your QSCU to the QSCP. I have found that queries can get different results with different providers due to the interpretation of DICOM standards. At least that is where I would start, but I am typically testing in the opposite direction, using DVT as the QSCU to my QSCP.

I hope this helps.

RoseAnn

Re: Question related to PDU-Length in Modality emulator (Echo test) [by satish]

Tue, 30 Mar 2010 12:43:09 +0200

Query Retrieve SCP Emulator:: Question related to PDU-Length in Modality emulator (Echo test)
In DICOM, only the actual length of the data is represented by the PDU length.You dont have subtract 6 before sending the data. Try using the DVTk Network Analyzer to sniff the packets and check what the actual length is. A more detailed description of the scenario will help.

Re: C_GET [by ren1]

Thu, 12 Mar 2009 15:01:23 +0200

Query Retrieve SCP Emulator:: C_GET
Many thanks for your help. The emulator now validates my message.

Re: Cancel is not recognized by QR SCP [by cpt]

Thu, 12 Mar 2009 01:42:47 +0200

Query Retrieve SCP Emulator:: Cancel is not recognized by QR SCP
Piyush,

Thanks, I created a ticket the other day.

cpt