Difference between revisions of "Move"
(Created page with "==Description== =={{GVESB}} Configuration== The dicom-move-call Element is used by Channel and routed-call. It has the attributes:") |
|||
| Line 1: | Line 1: | ||
==Description== | ==Description== | ||
| + | Move service is the operation for the transfer of a DICOM object. The service establishes an association between the client that invoked it and the provider to which the call is intended; the service provides unique key values to identify the object to be transferred; the provider generates the sub-operations [[Store]] for each identified object to be transferred; when the number of sub- operations [[Store]] reaches zero the provider generate and send a state response of success ( Success). The sub-operations [[Store]] occur on a different association than that of the Move . | ||
=={{GVESB}} Configuration== | =={{GVESB}} Configuration== | ||
The dicom-move-call Element is used by [[Channel]] and [[routed-call]]. It has the attributes: | The dicom-move-call Element is used by [[Channel]] and [[routed-call]]. It has the attributes: | ||
| + | {|class="gvtable" | ||
| + | ! Attribute !! Type !! Description | ||
| + | |- | ||
| + | | type || fixed || This attribute must assume the value '''call'''. | ||
| + | |- | ||
| + | | class || fixed || This attribute must assume the value '''it.greenvulcano.gvesb.virtual.dicom.DicomMoveCallOperation'''. | ||
| + | |- | ||
| + | | name || required || Operation name. Used in the [[Flow]] section to associate workflow nodes to VCL operations. | ||
| + | |- | ||
| + | | nameAssociation || required || Association name. It is used for the connection to a host. It is configured in '''GVAdapters'''. This value is referenced by a property "DICOM_ASSOCIATION" or manually, choosing a value among those available. | ||
| + | |- | ||
| + | | queryLevel || implied || | ||
| + | |- | ||
| + | | patientID || implied || | ||
| + | |- | ||
| + | | patientName || implied || | ||
| + | |- | ||
| + | | sopClass || implied || | ||
| + | |- | ||
| + | | sopClassUID || implied || | ||
| + | |- | ||
| + | | studyInstanceUID || implied || | ||
| + | |- | ||
| + | | seriesInstanceUID || implied || | ||
| + | |} | ||
Revision as of 12:53, 14 July 2015
Description
Move service is the operation for the transfer of a DICOM object. The service establishes an association between the client that invoked it and the provider to which the call is intended; the service provides unique key values to identify the object to be transferred; the provider generates the sub-operations Store for each identified object to be transferred; when the number of sub- operations Store reaches zero the provider generate and send a state response of success ( Success). The sub-operations Store occur on a different association than that of the Move .
GreenVulcano® ESB Configuration
The dicom-move-call Element is used by Channel and routed-call. It has the attributes:
| Attribute | Type | Description |
|---|---|---|
| type | fixed | This attribute must assume the value call. |
| class | fixed | This attribute must assume the value it.greenvulcano.gvesb.virtual.dicom.DicomMoveCallOperation. |
| name | required | Operation name. Used in the Flow section to associate workflow nodes to VCL operations. |
| nameAssociation | required | Association name. It is used for the connection to a host. It is configured in GVAdapters. This value is referenced by a property "DICOM_ASSOCIATION" or manually, choosing a value among those available. |
| queryLevel | implied | |
| patientID | implied | |
| patientName | implied | |
| sopClass | implied | |
| sopClassUID | implied | |
| studyInstanceUID | implied | |
| seriesInstanceUID | implied |
