Storage Commit - Push Model > 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.

The Workflow Engine accepts an incoming N-ACTIDN-REQUEST. This request defines the specific DICOM data objects [InstanceUle] that the Workflow Engine must manage. This list is preserved until the Storage Commit procedure is completed.

the Workflow Engine then sends an N-ACTION-RESPONSE to the source AET to confirm that the request has been received and is being processed.

The process of writing the study data to a permanent storage technology differs from site to site. Because this process varies, the amount of time required to record data also fluctuates. The Workflow Engine periodically checks the recording process until it is completed. If the requested image data is not found or the allowed timeout period has expired, the Workflow Engine places the affected lnstanceUle in the failed sequence portion of the N-EVENT-REPORT.

Once the study data is successfully recorded onto its permanent storage medium, the Workflow Engine sends an N-EVENT-REPORT to the source. This report serves as a receipt to confirm that the study is safe and under the responsibility of the archive entity. The source may then safely remove the study data from its local storage area, as/if necessary.