We have a PACS system from our HIS vendor and we are wanting to setup a PacsOne server for offsite backups every night. First off, are there any thoughts on this? Has anyone ever tried to do this?
The first issue I've run into is when I tell our PACS system to export I get a "Cannot initiate session: I/O error Failed SOP Instance" error in the job status page. Any ideas as to what's going on here?
Thanks in advance!
~Matt
Using PacsOne as backup
There are at least 2 ways you can do this:
1. Have your current PACS automatically forward all received images to PacsOne:
This is similar to the Automatic Routing function of PacsOne, and this setup will have your current PACS send a copy of received images to PacsOne automatically. For existing images, you can either manually forward them to PacsOne, or export them into CD/DVDs and import them from PacsOne.
2. If your current PACS supports Dicom Query/Retrieve as a SCP, then you can have PacsOne automatically synchronize with your current PACS:
Define an AE for your current PACS in the Application Entity of PacsOne, make sure you check the "Dicom Query/Retrieve SCP" checkbox, enable the Automatic Syncing with this AE and select one or more hourly schedules for PacsOne to sync with your currrent PACS.
1. Have your current PACS automatically forward all received images to PacsOne:
This is similar to the Automatic Routing function of PacsOne, and this setup will have your current PACS send a copy of received images to PacsOne automatically. For existing images, you can either manually forward them to PacsOne, or export them into CD/DVDs and import them from PacsOne.
2. If your current PACS supports Dicom Query/Retrieve as a SCP, then you can have PacsOne automatically synchronize with your current PACS:
Define an AE for your current PACS in the Application Entity of PacsOne, make sure you check the "Dicom Query/Retrieve SCP" checkbox, enable the Automatic Syncing with this AE and select one or more hourly schedules for PacsOne to sync with your currrent PACS.
This usually means PacsOne could not connect to your current PACS via Dicom protocol.
1. Can you Ping the AE Title of your current PACS from the Application Entity page of PacsOne Server? If so, then there is Dicom connectivity between the 2 applications.
2. If the above works, then click on the Query/Retrieve link for the AE Title of your current PACS, then click on <List All Studies> to have PacsOne query your current PACS and find all studies on your current PACS. If your current PACS does return a list of studies to PacsOne, then this will verify your current PACS does support Dicom Query/Retrieve as a SCP.
Based on the error you got, it's very likely that #1 above would not work. If that's the case, make sure you have configured the correct IP address and port number for your current PACS on the Application Entity page of PacsOne, and make sure there is no firewall blocking connections to that IP address/port number.
1. Can you Ping the AE Title of your current PACS from the Application Entity page of PacsOne Server? If so, then there is Dicom connectivity between the 2 applications.
2. If the above works, then click on the Query/Retrieve link for the AE Title of your current PACS, then click on <List All Studies> to have PacsOne query your current PACS and find all studies on your current PACS. If your current PACS does return a list of studies to PacsOne, then this will verify your current PACS does support Dicom Query/Retrieve as a SCP.
Based on the error you got, it's very likely that #1 above would not work. If that's the case, make sure you have configured the correct IP address and port number for your current PACS on the Application Entity page of PacsOne, and make sure there is no firewall blocking connections to that IP address/port number.