HDICOMNET hNet;

/* a DICOM Network handle */

L_UCHAR nPresentationID;

/* presentation ID */

L_UINT16 nMessageID;

/* message ID */

L_CHAR * pszClass;

/* class type */

L_CHAR * pszInstance;

/* instance */

L_UINT16 * pnAttribute;

/* array of attributes */

L_UINT32 nCount;

/* number of attributes */

L_VOID * pUserData;

/* pointer to additional data */

Parameter

Description

hNet

A DICOM Network handle to the peer member of the connection.

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.

pszInstance

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.

pnAttribute

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.

nCount

Number of attributes being requested.

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_DicomSendNGetRequest, L_DicomSendNGetResponse, RECEIVENGETRESPONSECALLBACK

Topics:

Receiving Messages