workflow engine as a DICOM Server > How it works

The SilverBack Workflow Engine SCP port is used to listen for incoming DICOM communications. The port continuously waits for incoming requests and as they arrive, passes them onto the Workflow Engine.

If the Workflow Engine receives a C-STORE command, the images are dynamically written into the Workflow Engine Share. The DICOM attributes for these images are then posted to the Workflow Engine database. This step provides rapid, efficient. on demand search capabilities for these images at any time. The source AET receives a successful response and the association is closed normally.

If a C-FIND command is received, the content of the command is converted to SGL and a query of the Workflow Engine database is executed. When the query returns matching patient data fields, the data fields are converted to a series of DICOM responses. These responses are then returned to the source AET and the association is closed normally.

If a C-MOVE command is received, the content of the command is converted to SOL and a query of the Workflow Engine database is executed. The matching patient study/series information is used to determine which image files should be sent.
The source AET receives a successful response and the association is closed normally.
Using the Workflow Engine SCU port, a new association is initiated with the target AET defined within the C-MDVE command. Once established. the selected images are read from the Workflow Engine Share and sent to the target AET.