Help Needed: GE CT Scanner Fails to Retrieve Modality Worklist (MWL) from dcm4chee

[David Nguyen]

Hello dcm4che community,
I'm struggling to connect a GE CT scanner to our dcm4chee PACS for Modality Worklist. When I initiate a query from the CT console, it immediately fails with an "Invalid" error
What I have done:
On dcm4chee: I have added the CT scanner's AE Title, IP address, and port to the list of allowed devices.
On the GE CT scanner: I have configured the dcm4chee server's AE Title, IP, and port for the MWL service.
Troubleshooting steps taken:
I can successfully ping the dcm4chee server from the CT scanner, so network connectivity is fine.
Despite these checks, the CT scanner still returns an error or an empty list. I suspect there might be some specific configuration parameters or matching key requirements for GE scanners that I am missing.
Could anyone who has experienced a similar issue or has expertise in connecting GE modalities to dcm4chee offer some guidance? What other settings should I look into, or are there specific logs in dcm4chee I should check to diagnose the root cause?
Any help would be greatly appreciated.
Thank you

[David Nguyen]

i am using dcm4chee 5.23.0 secure

Vào lúc 16:36:36 UTC+7 ngày Chủ Nhật, 14 tháng 9, 2025, David Nguyen đã viết:

[Loqman Dali Youcef]

On GE ct scann you need to configure a Connect pro . To access to rhis parameters you need a ssa key for configuration and following steps to configure MWL on the ct scann 

--
You received this message because you are subscribed to the Google Groups "dcm4che" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dcm4che+u...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/dcm4che/81d8df71-f5f7-43cb-92c9-729e4cd034c2n%40googlegroups.com.

[David Nguyen]

I have also configured dcm4chee's AET for the CT scanner, but it still doesn't work.

[David Nguyen]

Anyone with any information regarding connecting a GE CT scanner to dcm4chee please let me know

Vào lúc 20:18:25 UTC+7 ngày Thứ Năm, 18 tháng 9, 2025, David Nguyen đã viết:

[David Nguyen]

I have also configured it, when I manually enter 3 values ​​pid, accNo, patient name, after taking the photo, I can still send the photo normally, the problem here is that I cannot update the worklist from dcm4chee's MWL

Vào lúc 08:09:09 UTC+7 ngày Thứ Tư, 17 tháng 9, 2025, Loqman Dali Youcef đã viết:

[David Nguyen]

I have also configured dcm4chee's AET for the CT scanner, but it still doesn't work.

Vào lúc 08:09:09 UTC+7 ngày Thứ Tư, 17 tháng 9, 2025, Loqman Dali Youcef đã viết:

On GE ct scann you need to configure a Connect pro . To access to rhis parameters you need a ssa key for configuration and following steps to configure MWL on the ct scann 

[Thomas Schmidt]

Hi David.

Not sure this is any any help, but some years ago we had a similar issue with a GE CT scanner.  It turned out that GE CT scanners validate the worklist result hard against the DICOM standard. In our case the issue was that some of the patients registered in our RIS had medical alerts that wasn't limited correctly in regards to the DICOM Long String value representation (https://dicom.nema.org/dicom/2013/output/chtml/part05/sect_6.2.html). It turned out some patients had more than 64 characters in their Medical Alerts data. And whenever one patient had this, the whole Worklist result was discarded by the GE CT scanner. Not the best design decision in the scanner software in my opinion. But I ended up making changes to the Medical Alerts registration in our RIS to avoid the issue.

My recomendation would be to check the worklist result "by hand" and check if anything looks out of order

regards,

Thomas.

[Mizanur Rahman]

I can help you

To view this discussion visit https://groups.google.com/d/msgid/dcm4che/2e50e00a-1381-40c0-8e7f-d8752216ab8cn%40googlegroups.com.

--

----------------------------------------

MD MIZANUR RAHMAN

Director

System Automation BD

[Stephen Douglas Scotti]

Good suggestion.  Using https://support.dcmtk.org/docs/findscu.html from the CLI with verbose logging, and checking the dcm4che log files would probably reveal the error.  I've run into a similar problem multiple times. with non-conformant MWL file structures.