Is there a difference in the response to a C-FIND MWL between dcm4chee 5.33 and the old 2.17.3?

[perlab]

The reson for asking is we are updating our software to a more modern and secure system. But our 10 year old Philips Mobile modality don't like dcm4chee 5.33. When querying the Worklist for CR orders both from my laptop with dcm4che-tools (findscu) and from the Philips modality we get different results. My laptop is successful retrieving all available orders. The modality receives nada. I can se in the server.log at dcm4chee that both request are the same and the responses are the same. But nothing show up at the modality.

A big difference in the installations is that the old system run on a windows server but the new run in docker on an Ubuntu server latest lts

Any idea anyone what can be the problem?

[Chercess01]

Are you sure that the Philips device itself does not reject lists? Philips also has filters

[perlab]

No I am not sure of the Philips modality capabilities. But it is not obvious at all of how to get access to more elaborate settings or the server/dicom log for that matter. The Philips modality is a black box to me.

By accessing dcm4chee 5.33 server log I can see the DICOM C-FIND MWL request from the modality is correct and exactly the same as the request sent by the dcm4che-tools findscu command. The response is the same in both cases as well.

The modality act correctly when querying dcm4chee 2.17.3 MWL. I have not yet had the time to make the same call dcm4che-tools against 2.17.3 to see if there is a difference between the 2.17.3 response and the 5.33 response. If there is I need to figure out how to make the modality accept the 5.33 response or tweak the 5.33 response to something the modality may accept.

Also as the installations between 2.17.3 and the 5.33 are quite different I am still not completely convinced that communication works. although DICOM-ECHO works both ways for all involved parties.

We do not use secure communication yet but that is main objective Only standard DICOM ports are used.

[Chercess01]

is mwl displayed correctly in com dcm4chee 5.33?

[vrindanayak]

You can do the following as shown in example with findscu tool (the only thing here is findscu is simulating the modality)

In Wildfly configuration (standalone/configuration/dcm4chee-arc.xml) file, set following logger to DEBUG mode

<logger category="org.dcm4che3.net">
                <level name="DEBUG"/>
</logger>

Simulated triggering MWL C-FIND RQ using findscu tool

In archive server.log, it shows the complete request dataset as received by archive

2025-07-15 16:58:29,401 DEBUG [org.dcm4che3.net.Dimse] (EE-ManagedExecutorService-default-Thread-546) WORKLIST<-FINDSCU(7) >> 1:C-FIND-RQ Dataset receiving...
2025-07-15 16:58:29,401 DEBUG [org.dcm4che3.net.Timeout] (EE-ManagedExecutorService-default-Thread-546) WORKLIST<-FINDSCU(7): stop idle timeout
2025-07-15 16:58:29,401 DEBUG [org.dcm4che3.net.Dimse] (EE-ManagedExecutorService-default-Thread-546) Dataset:
(0008,0050) SH [] AccessionNumber
(0010,0010) PN [] PatientName
(0010,0020) LO [] PatientID
(0020,000D) UI [] StudyInstanceUID
(0032,1060) LO [] RequestedProcedureDescription
(0040,0100) SQ [1 Items] ScheduledProcedureStepSequence
>Item #1
>(0008,0060) CS [CR] Modality
>(0040,0002) DA [20250707] ScheduledProcedureStepStartDate
>(0040,0007) LO [] ScheduledProcedureStepDescription
>(0040,0009) SH [] ScheduledProcedureStepID
(0040,1001) SH [] RequestedProcedureID

[vrindanayak]

To answer your question itself in the issue title - No, there should be no difference, as dcm4chee archive v5.x follows the DICOM / IHE standards for :

• Modality Worklist SOP Class
• Query Modality Worklist RAD-5

[perlab]

thank you Vrindathis is the answer I was hoping for but I was not shure of. as the modality react differently to mwl responses comming from either 2.17.3 or 5.33 that should be the same the problem is most likely on the modality receiving side. Do you have any idea?/per---Per Lindevallmob: +46 70 777 0763mail: ***@***.*** juli 2025 kl. 17:07 skrev Vrinda ***@***.***>: To answer your question itself in the issue title - No, there should be no difference, as dcm4chee archive v5.x follows the DICOM / IHE standards for : Modality Worklist SOP Class Query Modality Worklist RAD-5 —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>

[vrindanayak]

I have already suggested how you can check what is the MWL C-FIND request dataset that the modality is sending to dcm4chee archive v5.x in #4745 (reply in thread) (in this link I've simulated with findscu)

Once you have the MWL C-FIND request dataset that modality is sending to dcm4chee archive v5.x, you could compare / simulate it with findscu tool and check where the root cause is.

I do not have experience with dcm4chee v2.x so I can't suggest anything w.r.t. it.

[perlab]

I will work more on this next week

/per