aeskulap-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Aeskulap-users] aeskulap dicom issues


From: Mitchell Laks
Subject: [Aeskulap-users] aeskulap dicom issues
Date: Wed, 11 Apr 2007 02:19:44 -0400
User-agent: Mutt/1.5.13 (2006-08-11)

Dear Alexander,
I have not seen much activity in months for aeskulap.
I have been thinking about  it.
i just tried to query a ctn server which returns errors
indicating dicom non compliance.
are you still interested in bug reports?

********************************
ACCEPTED   (AES localhost meshulums fun) (Rashi ) 20070410 235709.000000 16454
Parent
CFind Request
Message ID:              1
Data Set Type:           0001
Priority:                0002
Class UID:               1.2.840.10008.5.1.4.1.2.1.1
Find callback
SOP Class:      1.2.840.10008.5.1.4.1.2.1.1
Query Level:    STUDY
Response Count: 1

DCM Dump Elements
Object type: ELEMENT LIST
Object size: 126
Group: 0008, Length:       72
0008 0005       10 //      ID Specific Character Set//ISO_IR 100
0008 0020        0 //                  ID Study Date//
0008 0030        0 //                  ID Study Time//
0008 0052        5 //                 ID Query Level//STUDY
0008 0061        0 //         ID Modalities in Study//
0008 1010        0 //                ID Station Name//
0008 1030        0 //           ID Study Description//
Group: 0010, Length:       38
0010 0010        6 //               PAT Patient Name//krauss
0010 0020        0 //                 PAT Patient ID//
0010 0030        0 //          PAT Patient Birthdate//
0010 0040        0 //                PAT Patient Sex//
Group: 0020, Length:       16
0020 000d        0 //         REL Study Instance UID//
0020 0010        0 //                   REL Study ID//
DCM Dump Elements Complete

STUDY level query, Patient Root model is missing Patient ID (0010 0020) or has 
extra PATIENT level attributes
Find callback
SOP Class:      1.2.840.10008.5.1.4.1.2.1.1
Query Level:    STUDY
Response Count: 2
Writing to network: Connection reset by peer
   f0012 TCP I/O Error (Illegal seek) occurred in routine: sendReleaseRPTCP
Exiting
q

*******************************
looks like it was not well formed dicom query from the AES = aeskulap server
i used your interface to ask for
krauss
which is patient name

thus the error is:

STUDY level query, Patient Root model is missing Patient ID (0010 0020) or has 
extra PATIENT level attributes
Find callback


i find wustl ctn gives good debugging output on dicom queries.

any thoughts?

Mitchell




reply via email to

[Prev in Thread] Current Thread [Next in Thread]