Friday, February 10, 2012
Google Custom Search

ClearCanvas Highlights

Download our Open Source software
Watch some Videos
Get the Source
Check out our Licensing
Join our  Forums
Some Research: OICR IPP-Trials

Our Community

Membership Membership:
Latest New User Latest: Chivan
New Today New Today: 3
New Yesterday New Yesterday: 27
User Count Overall: 20593

People Online People Online:
Visitors Visitors: 11
Members Members: 2
Total Total: 13

Online Now Online Now:
01: richteh
02: vposhataev

ClearCanvas Community Forums

Incorrect C-Move response code in message object
Last Post 2010-06-11 01:16 PM by steve. 1 Replies.
Printer Friendly
Sort:
PrevPrev NextNext
You are not authorized to post a reply.
Author Messages
nieljake
Basic Member
Basic Member
Posts:23

--
2010-06-11 10:17 AM  

We are here in the client handler for a C-Move failure scenario:

class AssociationHandler : IDicomClientHandler

OnReceiveResponseMessage()

The code:

message.Status.Code;

ALWAYS gives 42752 even when 42753 or 42754 is actually received. Here is a log from my program. It says A700 (which is 42752) but A701 (Which is 42753) was actually received. One problem is according to part 4 of the standard, A700 does not exist as a valid response code for C-Moves, yet it is what the message object gives for message.Status.Code;

2010-06-11 09:02:42,359 [2580] [DicomClient: 172.16.23.191:4000 [16]] ERROR - Failure response received for C-Move request. Response: A700 - Unknown Response Received!
2010-06-11 09:02:42,359 [2580] [DicomClient: 172.16.23.191:4000 [16]] DEBUG - Receive MetaInfo:
(0000,0002) UI =Patient Root Query/Retrieve Information Model – MOVE #   28 Affected SOP Class UID 1
(0000,0100) US 32801                                    #    2 Command Field 1
(0000,0120) US 1                                        #    2 Message ID Being Responded To 1
(0000,0800) US 257                                      #    2 Data Set Type 1
(0000,0900) US 42753                                    #    2 Status 1

 

 

 

 

 

steve
Senior Member
Senior Member
Posts:1885

--
2010-06-11 01:16 PM  

 Jake,

This looks like a bug in the DicomStatuses.Lookup method and how it deals with statuses that have a mask.  Specifically, it appears that this method is picking the status DicomStatuses.StorageStorageOutOfResources as the matching status (because it has a mask that matches the real status) instead of the explicit status that directly matches.

I've created a ticket here for this issue.  For the time being, if possible, I'd suggest accessing the status attribute directly in the command group instead of using this property.

Steve

Real-time support available to Clinical Edition and Team Edition customers
You are not authorized to post a reply.

Active Forums 4.1
Copyright 2011 ClearCanvas Inc.