Probably interfacting Orthanc MWL server with GE DX Modality

All other questions regarding DCMTK

Moderator: Moderator Team

Post Reply
Message
Author
Stephen D. Scotti
Posts: 16
Joined: Fri, 2020-06-19, 07:56

Probably interfacting Orthanc MWL server with GE DX Modality

#1 Post by Stephen D. Scotti »

GE, interop standards, sent me what they say is a document having the Conformance for a GE XR-385 DX modality.

"GE Healthcare DR-F Acquisition Workstation DICOM Conformance Statement"

That is helpful, but I/we are still having some trouble getting the Orthanc MWL server to function with that device as a MWL server. The Orthanc MWL server is working adequately with multiple other devices, including CT, MAMMO and US, including some GE US modalities, so it seems to be something peculiar with the interface to the GE DX unit. I do not have full access to the log files, mostly on the GE side of things.

The Orthanc log shows the C-FIND request:

===================== INCOMING DIMSE MESSAGE ====================
Message Type : C-FIND RQ
Presentation Context ID : 1
Message ID : 539
Affected SOP Class UID : FINDModalityWorklistInformationModel
Data Set : present
Priority : medium
======================= END DIMSE MESSAGE =======================
T0930 10:08:20.268539 FindScp.cpp:215] (dicom) Received C-FIND Request:

# Dicom-Data-Set
# Used TransferSyntax: Little Endian Explicit
(0008,0005) CS [ISO_IR 100] # 10, 1 SpecificCharacterSet
(0008,0050) SH (no value available) # 0, 0 AccessionNumber
(0008,0090) PN (no value available) # 0, 0 ReferringPhysicianName
(0008,1110) SQ (Sequence with explicit length #=1) # 24, 1 ReferencedStudySequence
(fffe,e000) na (Item with explicit length #=2) # 16, 1 Item
(0008,1150) UI (no value available) # 0, 0 ReferencedSOPClassUID
(0008,1155) UI (no value available) # 0, 0 ReferencedSOPInstanceUID
(fffe,e00d) na (ItemDelimitationItem for re-encoding) # 0, 0 ItemDelimitationItem
(fffe,e0dd) na (SequenceDelimitationItem for re-encod.) # 0, 0 SequenceDelimitationItem
(0008,1120) SQ (Sequence with explicit length #=1) # 24, 1 ReferencedPatientSequence
(fffe,e000) na (Item with explicit length #=2) # 16, 1 Item
(0008,1150) UI (no value available) # 0, 0 ReferencedSOPClassUID
(0008,1155) UI (no value available) # 0, 0 ReferencedSOPInstanceUID
(fffe,e00d) na (ItemDelimitationItem for re-encoding) # 0, 0 ItemDelimitationItem
(fffe,e0dd) na (SequenceDelimitationItem for re-encod.) # 0, 0 SequenceDelimitationItem
(0010,0010) PN [*] # 2, 1 PatientName
(0010,0020) LO (no value available) # 0, 0 PatientID
(0010,0030) DA (no value available) # 0, 0 PatientBirthDate
(0010,0040) CS (no value available) # 0, 0 PatientSex
(0010,1010) AS (no value available) # 0, 0 PatientAge
(0010,1030) DS (no value available) # 0, 0 PatientWeight
(0010,2000) LO (no value available) # 0, 0 MedicalAlerts
(0010,2110) LO (no value available) # 0, 0 Allergies
(0010,21c0) US (no value available) # 0, 0 PregnancyStatus
(0020,000d) UI (no value available) # 0, 0 StudyInstanceUID
(0020,0010) SH (no value available) # 0, 0 StudyID
(0032,1032) PN (no value available) # 0, 0 RequestingPhysician
(0032,1060) LO (no value available) # 0, 0 RequestedProcedureDescription
(0032,1064) SQ (Sequence with explicit length #=1) # 40, 1 RequestedProcedureCodeSequence
(fffe,e000) na (Item with explicit length #=4) # 32, 1 Item
(0008,0100) SH (no value available) # 0, 0 CodeValue
(0008,0102) SH (no value available) # 0, 0 CodingSchemeDesignator
(0008,0103) SH (no value available) # 0, 0 CodingSchemeVersion
(0008,0104) LO (no value available) # 0, 0 CodeMeaning
(fffe,e00d) na (ItemDelimitationItem for re-encoding) # 0, 0 ItemDelimitationItem
(fffe,e0dd) na (SequenceDelimitationItem for re-encod.) # 0, 0 SequenceDelimitationItem
(0038,0010) LO (no value available) # 0, 0 AdmissionID
(0038,0050) LO (no value available) # 0, 0 SpecialNeeds
(0038,0300) LO (no value available) # 0, 0 CurrentPatientLocation
(0038,0500) LO (no value available) # 0, 0 PatientState
(0040,0100) SQ (Sequence with explicit length #=1) # 156, 1 ScheduledProcedureStepSequence
(fffe,e000) na (Item with explicit length #=13) # 148, 1 Item
(0008,0060) CS (no value available) # 0, 0 Modality
(0032,1070) LO (no value available) # 0, 0 RequestedContrastAgent
(0040,0001) AE (no value available) # 0, 0 ScheduledStationAETitle
(0040,0002) DA (no value available) # 0, 0 ScheduledProcedureStepStartDate
(0040,0003) TM (no value available) # 0, 0 ScheduledProcedureStepStartTime
(0040,0006) PN (no value available) # 0, 0 ScheduledPerformingPhysicianName
(0040,0007) LO (no value available) # 0, 0 ScheduledProcedureStepDescription
(0040,0008) SQ (Sequence with explicit length #=1) # 40, 1 ScheduledProtocolCodeSequence
(fffe,e000) na (Item with explicit length #=4) # 32, 1 Item
(0008,0100) SH (no value available) # 0, 0 CodeValue
(0008,0102) SH (no value available) # 0, 0 CodingSchemeDesignator
(0008,0103) SH (no value available) # 0, 0 CodingSchemeVersion
(0008,0104) LO (no value available) # 0, 0 CodeMeaning
(fffe,e00d) na (ItemDelimitationItem for re-encoding) # 0, 0 ItemDelimitationItem
(fffe,e0dd) na (SequenceDelimitationItem for re-encod.) # 0, 0 SequenceDelimitationItem
(0040,0009) SH (no value available) # 0, 0 ScheduledProcedureStepID
(0040,0010) SH (no value available) # 0, 0 ScheduledStationName
(0040,0011) SH (no value available) # 0, 0 ScheduledProcedureStepLocation
(0040,0012) LO (no value available) # 0, 0 PreMedication
(0040,0020) CS (no value available) # 0, 0 ScheduledProcedureStepStatus
(fffe,e00d) na (ItemDelimitationItem for re-encoding) # 0, 0 ItemDelimitationItem
(fffe,e0dd) na (SequenceDelimitationItem for re-encod.) # 0, 0 SequenceDelimitationItem
(0040,1001) SH (no value available) # 0, 0 RequestedProcedureID
(0040,1003) SH (no value available) # 0, 0 RequestedProcedurePriority
(0040,1004) LO (no value available) # 0, 0 PatientTransportArrangements
(0040,3001) LO (no value available) # 0, 0 ConfidentialityConstraintOnPatientDataDescription

and then responses are sent, . . . .,

but the connection is then terminated by the client:

I0930 10:08:20.272838 CommandDispatcher.cpp:917] (dicom) Finishing association with AET 1026DGXR01 on IP 10.12.17.19: DUL Peer Requested Release
I0930 10:08:20.272872 CommandDispatcher.cpp:925] (dicom) Association Release with AET 1026DGXR01 on IP 10.12.17.19

On the client side, there are some error messages:

"Some of the worklist query responses are not valid and thus discarded. Check the contents on the remote worklist .."
"Some of the incoming Workist entries are invalid. The entries have been discarded"

Without access to more detailed logging information on the GE client, it is a bit difficult to determine what the exact issue is.
If it was possible to get a sample of a 'working" MWL file, that would be helpful.

I should say that I do not think that the MWL files have the Meta-Information Header. Is that necessary for a MWL response ?


Any suggestions appreciated.

Stephen D. Scotti, M.D.

Michael Onken
DCMTK Developer
Posts: 2048
Joined: Fri, 2004-11-05, 13:47
Location: Oldenburg, Germany
Contact:

Re: Probably interfacting Orthanc MWL server with GE DX Modality

#2 Post by Michael Onken »

Hi Stephen,

this is a DCMTK-based forum so asking this questions makes more sense in the Orthanc Community or GE community (?), or in comp.protocols.dicom newsgroups.

Best regards,
Michael

Post Reply

Who is online

Users browsing this forum: Ahrefs [Bot], Google [Bot] and 1 guest