Transfer Syntax Translation > How it works

During the negotiation portion of an association, the source SCU offers one or more transfer syntaxes for each modality. As a default, the Workflow Engine selects the first transfer syntax offered for each modality to set the transfer syntax. Optionally, the DICOM port can be easily be customized to suppport specific transfer syntaxes to control the results of the negotiation.

The SilverBack Workflow Engine offers all transfer syntaxes when establishing an association with a target application entity title [AET]. The target selects which transfer syntax it prefers during the initial negotiation. Optionally, The DICOM port can be setup to support specific transfer syntaxes to control the results of the negotiation.

The Workflow Engine respects and uses the offered transfer syntax of the source when receiving data from the source or sending data to the source. Plus, the Workflow Engine respects and uses the selected transfer syntax of the target when sending data or receiving data from the target.