Gateway Inbound
Gateway Inbound
Hello OnePacs team!
We have successfully installed the gateway at our client's computer. When we try to send exams performed at the main clinic everything works fine. However, everytime we try sending an exam performed at one of the client's subsidiary's (from the main clinic's PACS) the file does not go through. Do you think the gateway is not allowing these exams to go through because the subsidiary's DICOM tag named institution is named differently from the main clinic? How can we solve this?
Thanks!
Rodrigo
We have successfully installed the gateway at our client's computer. When we try to send exams performed at the main clinic everything works fine. However, everytime we try sending an exam performed at one of the client's subsidiary's (from the main clinic's PACS) the file does not go through. Do you think the gateway is not allowing these exams to go through because the subsidiary's DICOM tag named institution is named differently from the main clinic? How can we solve this?
Thanks!
Rodrigo
-
- Posts: 195
- Joined: Wed Jun 20, 2012 5:14 am
Re: Gateway Inbound
The sending facility's DICOM tag for institution won't matter. Are you sure all the parameters are set up correctly (called AE title, etc.)? And most importantly, is that other facility able to communicate with the gateway? Are they on the same local network? Did you try pinging the gateway?
Re: Gateway Inbound
Hello John,
We are not sending the images directly from the subsidiary to the gateway. The subsidiary sends the images via VPN to the PACS installed at the Main clinic (HQ) and the PACS at the HQ sends the images to the gateway (installed at the HQ). All exams processed at the HQ are going through, but the ones processed at the subsidiary are not...
We are not sending the images directly from the subsidiary to the gateway. The subsidiary sends the images via VPN to the PACS installed at the Main clinic (HQ) and the PACS at the HQ sends the images to the gateway (installed at the HQ). All exams processed at the HQ are going through, but the ones processed at the subsidiary are not...
Re: Gateway Inbound
This is what the clinic's PACS' log says:
[00001224 @ 15-Aug-2013 11:24:11]: Connecting to DICOM node XXXX at 172.16.105.198:4104
[00001224 @ 15-Aug-2013 11:24:11]: ERROR: Exception [Unable to connect to DICOM node [XXXX:172.16.105.198:4104] Error 0x2c0c [MSM_ERR_SOP]]
[00001224 @ 15-Aug-2013 11:24:11]: ERROR: Exception [Queue Sending Failed]
[00001224 @ 15-Aug-2013 11:24:11]: INFO: Queue 74 not sent successfully
tag : 0000,1224
[00001224 @ 15-Aug-2013 11:24:11]: Connecting to DICOM node XXXX at 172.16.105.198:4104
[00001224 @ 15-Aug-2013 11:24:11]: ERROR: Exception [Unable to connect to DICOM node [XXXX:172.16.105.198:4104] Error 0x2c0c [MSM_ERR_SOP]]
[00001224 @ 15-Aug-2013 11:24:11]: ERROR: Exception [Queue Sending Failed]
[00001224 @ 15-Aug-2013 11:24:11]: INFO: Queue 74 not sent successfully
tag : 0000,1224
Re: Gateway Inbound
It is hard to tell what is going on from your PACS log there. It could be a network, or DICOM protocol error. Can you send us the gateway's logs? See this web page for instructions:
http://wiki.onepacsforums.com/doku.php? ... cs_gateway
-- Damien
http://wiki.onepacsforums.com/doku.php? ... cs_gateway
-- Damien
-
- Posts: 195
- Joined: Wed Jun 20, 2012 5:14 am
Re: Gateway Inbound
BTW make sure to send the logs through the onepacs messaging system, which is secure according to requirements for HIPAA. Please send them to user name "admin". And post a note here when you do so so we know to look for them. Thanks.
Re: Gateway Inbound
Hello Damien/John,
Thank you for your quick reply. The log has been sent via the onepacs messaging system. Please let me know if it was sent correctly.
Thanks,
Rodrigo
Thank you for your quick reply. The log has been sent via the onepacs messaging system. Please let me know if it was sent correctly.
Thanks,
Rodrigo
Re: Gateway Inbound
I looked at the logs and it appears that we are getting a network timeout on our side. Your system makes a network connection, but we do not receive any DICOM association information over the connection so the network read operation on the gateway side times out. Is there anything else you can think of that might be different in the way these studies are sent versus the others that work? Also, can you verify that the other studies still work? I see a lot of images being sent in the logs, but then the last attempts fail. If nothing works, then I imagine there must be a network glitch. If only the subset of images fail, then I think there must be something different in the way they are being sent, because it is all the same to the gateway....
-- Damien
-- Damien
Re: Gateway Inbound
Hello Damien,
We have found the problem. Images were being sent as jpeg 2000 from the subsidiary to the HQ and then sent to the gateway without conversion to DICOM. Exams processed at the HQ were being sent as DICOM so that's why it was working. We have now changed the PACS to automatically convert images sent from the subsidiary to DICOM before being sent to us. Now the system is working perfectly. Thanks again for your help!
We have found the problem. Images were being sent as jpeg 2000 from the subsidiary to the HQ and then sent to the gateway without conversion to DICOM. Exams processed at the HQ were being sent as DICOM so that's why it was working. We have now changed the PACS to automatically convert images sent from the subsidiary to DICOM before being sent to us. Now the system is working perfectly. Thanks again for your help!
Re: Gateway Inbound
No problem! Glad it was figured out.
-- Damien
-- Damien