Any idea where I can get a Dicom Conformance Document for that device ?

I tried contacting GE and some used equipment vendors, but cannot find one.

I did find this with a Google Search, but it looks like that is for CT ?

https://www.gehealthcare.com/-/jssmedia/widen/2018/01/25/0204/gehealthcarecom/migrated/2018/02/19/0840/rability-dicom-computed-tomography-gehc-dicom-conformance_optima_brivo_doc1051015_rev5_pdf.pdf

Stephen D. Scotti

GE, interop standards, sent me what they say is a document having the Conformance for that device.

"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:

.. . . .

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.

Suggestions:
1. Connect with support engineers from both vendors, preferably in same meeting, and ask them to diagnose and recommend/implement fix.
2. Put your question in Orthanc user group https://groups.google.com/g/orthanc-users

Regards,

Jouke Numan

Op dinsdag 4 oktober 2022 om 07:52:12 UTC+2 schreef stephen....@gmail.com:
> GE, interop standards, sent me what they say is a document having the Conformance for that device.
>
> "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:
>
> . . . .
>
> 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.