Our client cannot parse the C-FIND response...

39 views
Skip to first unread message

illes.s...@ge.com

unread,
Jan 10, 2019, 10:16:32 AM1/10/19
to Orthanc Users

Dear Orthanc Support,

 

We have tested Orthanc v.1.4.2 DICOM PACS (on Fedora29) with Our Java Based Image Viewer which is part of the GE AWS.

(build information: https://koji.fedoraproject.org/koji/buildinfo?buildID=1146148)

 

We have used findscu command for querying on IMAGE level on Orthanc:

 

$ findscu -k 0008,0052=IMAGE -k PatientID -k StudyInstanceUID="1.2.840.*" -P localhost 8000 -v -aet ORTHANC

 

---

# Dicom-Data-Set

# Used TransferSyntax: Little Endian Explicit

(0002,0003) UI [1.2.840.113619.2.248.116521109919.22106.1423741452885.260] #  58, 1 MediaStorageSOPInstanceUID

(0008,0005) CS [ISO_IR 100]                             #  10, 1 SpecificCharacterSet

(0008,0018) UI [1.2.840.113619.2.248.116521109919.22106.1423741452885.260] #  58, 1 SOPInstanceUID

(0008,0052) CS [IMAGE ]                                 #   6, 1 QueryRetrieveLevel

(0010,0020) LO [AW2027798899.190.1423741452 ]           #  28, 1 PatientID

(0020,000d) UI [1.2.840.113619.2.248.116521109919.22106.1423741452236.2] #  56, 1 StudyInstanceUID

 

Received Final Find Response (Success)

Releasing Association

---

 

We found an unsupported C-FIND DICOM attributin the response:

 

(0002,0003) UI [1.2.840.113619.2.248.116521109919.22106.1423741452885.260] #  58, 1 MediaStorageSOPInstanceUID

--

 

You can check up in C.4.1.1.3.1 Request Identifier Structure section:

http://dicom.nema.org/medical/dicom/current/output/chtml/part04/sect_C.4.html#sect_C.4.1.1.3

 

So according to the standard, providing attributes having groups value under 0008 are invalid in the C-FIND request and response

--

Because of this misbehavior our client cannot parse the C-FIND response.

 

We appreciate your support regarding this issue.

 

Thank you in advance.

 

 

Kind regards,

 

 

Szabolcs Illes

Senior System Engineer

Advantage Workstation

GE Healthcare

illes.s...@ge.com

Sébastien Jodogne

unread,
Jan 10, 2019, 3:26:23 PM1/10/19
to Orthanc Users
Hello,

Thanks for reporting this issue!

It should have been fixed by the following changeset that has just been committed to the Orthanc mainline:

Please could you give a try to this fix by compiling the mainline from source?

This fix will be part of forthcoming Orthanc 1.5.2.

Regards,
Sébastien-

Sébastien Jodogne

unread,
Jan 23, 2019, 8:33:34 AM1/23/19
to Orthanc Users
For reference, the previous fix (that is shipped with Orthanc 1.5.2) was not sufficient by itself. 

Full patch is now available in the following changeset, that will be part of forthcoming Orthanc 1.5.3:

Sébastien-
Reply all
Reply to author
Forward
0 new messages