RECEIVECFINDREQUESTCALLBACK

HDICOMNET hNet;

/* a DICOM Network handle */

L_UCHAR nPresentationID;

/* presentation ID */

L_UINT16 nMessageID;

/* message ID */

L_TCHAR * pszClass;

/* class type */

L_UINT16 nPriority;

/* priority of the message */

HDICOMDS hDS;

/* data set to be found */

L_VOID * pUserData;

/* pointer to additional data */

Parameter

Description

hNet

A DICOM Network handle.

nPresentationID

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.

nMessageID

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.

pszClass

Class affected by the request. This will be an SOP Class or an SOP MetaClass.

nPriority

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:

Value

Meaning

COMMAND_PRIORITY_LOW

[0x0002] Low priority message.

COMMAND_PRIORITY_MEDIUM

[0x0000] Medium priority message.

COMMAND_PRIORTY_HIGH

[0x0001] High priority message.

hDS

Pointer to the data set to be found.

pUserData

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.

LTDIC

For a listing of the exact DLLs and Libraries needed, based on the toolkit version, refer to Files To Be Included With Your Application

Functions:

L_DicomSendCFindRequest, L_DicomSendCFindResponse, RECEIVECFINDRESPONSECALLBACK

Topics:

Receiving Messages