Thank you for the call. Yes, we have set these parameters through jmx-console but the technical reference manual does not state exact values/names for these parameters.
One more thing that we learned today is to test communication with modality through DCM4Chee. On DCM4Chee there is a menu “Application Entities” where ip and port of the modality can be entered to do a DICOM Echo test. If this echo test succeeds it means that the connection has been established.
The same ip and port is now set in modality in bahmni_pacs database.
We are using GE Healthcare’s CT Revolution ACT. Getting the port for the modality was a tough thing but finally we got the port in the modality’s “Revolution ACTs Dicom Conformance Statement”
For the duplicate orders the HL7 Acknowledgement message is rightly seen in /var/log/pacs-integration/pacs-integration.log is as follows
MSA|AR|1569084438122436|Duplicate MWLItem[pk=30, spsId=ORD-436.1, spsStartDateTime=2019-09-21 22:17:17.964, spsStatus=SCHEDULED, stationAET=ct99, rqProcId=ORD-436.1, modality=CT, accessionNo=ORD-436, patient->ejb/Patient:9
Though the error thrown is misleading
Unable to send the message to the modality
But for the new orders it does not show any information in this log so it is difficult to know in such cases if the message was sent to modality or not.
For such new orders we see the related HL7 message in /var/lib/bahmni/dcm4chee-2.18.1-psql/server/default/log/server.log
OBR-39:^CT SCAN WHOLE ABDOMEN WITHOUT CONTRAST
But such worklist item is not seen on modality.
So as @arjun has rightly mentioned here
We can see the worklist on DCM4Chee but not able to set modality to poll DCM4Chee (Does it actually poll?) to fetch the worklist item and display in modality’s console.