LDicomNet::SendNReportResponse

#include "ltdic.h"

L_INT LDicomNet::SendNReportResponse(nPresentationID, nMessageID, pszClass, pszInstance, nStatus, nEvent, pDS)

L_UCHAR nPresentationID;

presentation ID

L_UINT16 nMessageID;

message ID

L_TCHAR * pszClass;

class type

L_TCHAR * pszInstance;

instance

L_UINT16 nStatus;

status

L_UINT16 nEvent;

event

LDicomDS *pDS;

data set

Sends an N-EVENT-REPORT-RSP message to a peer member of a connection. This function is available in the PACS Imaging Toolkit.

Parameter

Description

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.

nStatus

The status of the original request. For a list of possible values, refer to Status Constants.

nEvent

An application specific event for which a report is to be generated.

pDS

Application specific data set which contains information related to the operation.

Returns

0

SUCCESS

>0

An error occurred. Refer to Return Codes.

Comments

LDicomNet::SendNReportResponse is sent by the SCP in response to an LDicomNet::SendNReportRequest call placed by an SCU. This generates a call to LDicomNet::OnReceiveNReportResponse on the SCU.

A report is generated to let all peers attached to a server know of some event that has occurred. This event may be the addition of a new patient, the deletion of a patient, the addition of a new study, etc. The nEvent value, which designates the event that occurred, is determined by the server. To find out the values used, you must contact the organization that created the server. When creating a server, the values and their corresponding meanings are determined by those creating the server.

Required DLLs and Libraries

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

Platforms

Win32, x64

Help Version 19.0.2017.10.27
Products | Support | Contact Us | Copyright Notices
© 1991-2017 LEAD Technologies, Inc. All Rights Reserved.
LEADTOOLS DICOM C++ Class Library Help
Introduction
Version History
Getting Started
LEADTOOLS DICOM Features
Redistributables/Files To Be Included With Your Application
Quick Reference
Classes and Member Functions
CallBack Functions
Appendix