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.
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:
*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.
- 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.
some references:
http://davidsimic.com/2016/07/30/dcm4chee-pacs-synchronization-via-dicom-forwarding/
https://dcm4che.atlassian.net/wiki/spaces/ee2/pages/2556081/Forward+Service2