Configuring the OnePacs Gateway to route to multiple destinations based on rules
In certain situations it may be desirable to be able to forward cases from the gateway to multiple destinations based on rules. By default, the OnePacs Gateway only forwards studies to the OnePacs server. This is the recommended configuration. If your goal is to store a copy of studies to an SCP via DICOM and you have the ability to install the study retriever it may be simpler to create a user with a user access filter or give the user access to a shared folder to control what studies will be accessible and then setup the study retriever with that user configured on the local network of the SCP. The study retriever can then be setup to store to a destination using the destinations tab. If everything (Gateway, study retriever, additional SCP) is on the local network then the “Local gateway settings” should be enabled on the OnePacs Study Retriever
It is also possible to configure a gateway to forward studies to more than just the OnePacs server. This configuration can be performed by technically advanced users, or may be performed by the OnePacs support staff. For users with the requisite technical skill to perform this configuration, instructions follow.
Advanced configuration to support multiple forwards
It is possible to modify the gateway installation to support forwards to multiple destinations. Follow the steps below to add an additional forward destination AE title to your OnePacs Gateway deployment:
- First, install the OnePacs Gateway and reboot.
- Log in to the OnePacs Gateway administrative interface.
- On the AE Management tab, create a new AE title definition for the additional forward destination. At a minimum you will need to enter the AE Title, HostName, and Port of your destination. You may press the echo button to ensure that the device is properly setup.
- Press the create button.
- Second, Log into JMX console
If you want to add a simple forward for all studies
Select the service=Forward To add a simple forward for all studies add the new destination AE Title as part of a comma separated list in the Forwarding Rules configuration.
Add a more complex forward rule using the forward2 service
If you need more power to determine how studies are forwarded you could also configure the service=Forward2 which uses XSL to forward studies based on DICOM attributes.
- Create a new folder dcm4chee-ae in the C:/onepacs/gateway/server/default/conf/ directory. Go into that directory.
- Create a new folder and name it the same name as your calling AE Title that will be sending the DICOM to the gateway.
- Go into that folder and create a file called forward.xsl. This file will control what is forwarded to where when studies are sent from the matching calling AE Title.
*Note that if you are using the forward2 service in this manner, you need to also delete the destinations listed in the "ForwardingRules" configuration shown above; otherwise, studies will be forwarded both according to the forward service and the forward2 service.
Edit the file to forward the to the correct destination AE title. There are several example forward.xsl files that already exist in your installation under the C:/onepacs/gateway/server/default/conf/dcm4chee-ae/MOD_AET directory and may be used as examples. Below is an example of a forward that will forward everything from a device with the calling AE title of CALLING_AE1 to DESTINATION_AE1 and will only forward studies that have DICOM institution name (0008,0080) of INSTITUTION_NAME to AE title DESTINATION_AE2. (Both destinations would have been added before when adding the AE titles)