←Select platform

OnNGet Method

Summary

Allows addins to handle N-GET-REQ commands.

Syntax

C++

public DicomCommandStatusType OnNGet( 
   DicomClient Client, 
   byte PresentationId, 
   int MessageID, 
   string AffectedClass, 
   string Instance, 
   long[] Attributes, 
   DicomDataSet Response 
)

  
Function OnNGet( _ 
   ByVal Client As Leadtools.Dicom.Addin.DicomClient, _ 
   ByVal PresentationId As Byte, _ 
   ByVal MessageID As Integer, _ 
   ByVal AffectedClass As String, _ 
   ByVal Instance As String, _ 
   ByVal Attributes() As Long, _ 
   ByVal Response As Leadtools.Dicom.DicomDataSet _ 
) As Leadtools.Dicom.DicomCommandStatusType

Leadtools.Dicom.DicomCommandStatusType OnNGet(  
   Leadtools.Dicom.Addin.DicomClient^ Client, 
   byte PresentationId, 
   int MessageID, 
   String^ AffectedClass, 
   String^ Instance, 
   array<int64>^ Attributes, 
   Leadtools.Dicom.DicomDataSet^ Response 
)

Parameters

Client
The client that sent the command.

PresentationId
The Presentation Context ID. The ID provides information about both the class type of the data and the Transfer Syntax to use when transferring the data.

MessageID
The 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.

AffectedClass
The class affected by the request. This will be a SOP Class or a Meta SOP Class

Instance
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.

Attributes
An array of the required attributes. The attributes must be specified using the Data Element Tags.

Response
The response dataset to be filled by the implementor.