A DICOM Network handle to the peer member of the connection.
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 instance of the class. A server may, for example, have three instances of the Nuclear Medicine Class. This value identifies the data with a specific instance.
An array of the attributes to get. The attributes must be specified using the Data Element Tags. For a list of available Data Element Tags, refer to Data Element Tag Constants.
Number of attributes being requested.
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 a peer member of a connection when L_DicomSendNGetRequest is called locally.
To use this callback function, RECEIVENGETREQUESTCALLBACK must be set using L_DicomSetCallback.
Required DLLs and Libraries
For an example, refer to L_DicomSendNGetResponse.
Medical Web Viewer .NET
.NET, Java, Android, and iOS/macOS Assemblies
C API/C++ Class Libraries