A DICOM Network handle.
Presentation ID. The presentation ID provides information about both the class type of the data and the transfer syntax to use when transferring the data.
Message ID. Each message sent by a member of a connection should have a unique ID. Since a member of a connection may send several messages, this ID allows that member to identify when a specific request has been completed.
Class affected by the request. This will be an SOP Class or an SOP MetaClass.
The priority level of the message. The Service Class Provider may or may not support priority. Therefore, setting this parameter may or may not have any effect. Possible values are:
|COMMAND_PRIORITY_LOW||[0x0002] Low priority message.|
|COMMAND_PRIORITY_MEDIUM||[0x0000] Medium priority message.|
|COMMAND_PRIORITY_HIGH||[0x0001] High priority message.|
Character string that contains the name of the application entity that originally requested the move. For a simple storage request from a client to a server, this should be ". When the request is a sub-operation of a C-MOVE, this will contain the name of the AE that requested the move.
Pointer to the data set to be moved.
Void pointer that you can use to access a variable or structure containing data that your callback function needs. This gives you a way to receive data indirectly from the function that uses this callback function.
Keep in mind that this is a void pointer, which must be cast to the appropriate data type within your callback function.
A call to this function is generated on an SCP when L_DicomSendCMoveRequest is called by the SCU.
To use this callback function, RECEIVECMOVEREQUESTCALLBACK must be set using L_DicomSetCallback.
For an example, refer to L_DicomSendCMoveResponse.
Medical Web Viewer .NET
.NET, Java, Android, and iOS/macOS Assemblies
C API/C++ Class Libraries