L_DicomSendNReportResponse

#include "ltdic.h"

L_LTDIC_API L_INT L_DicomSendNReportResponse(hNet, nPresentationID, nMessageID, pszClass, pszInstance, nStatus, nEvent, hDS)

HDICOMNET hNet;	a DICOM Network handle
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
HDICOMDS hDS;	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
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.
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.
hDS	Application specific data set which contains information related to the operation.

Returns

DICOM_SUCCESS	The function was successful.
>0	An error occurred. Refer to Return Codes.

Comments

L_DicomSendNReportResponse is sent by the SCP in response to an L_DicomSendNReportRequest call placed by an SCU. This generates a call to RECEIVENREPORTRESPONSECALLBACK 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, Linux.

Example

#include <windowsx.h> 
static HWND hList;      /* handle to list box */ 
L_VOID EXT_CALLBACK OnReceiveNReportRequest (HDICOMNET hNet, L_UCHAR nPresentationID, L_UINT16 nMessageID, L_TCHAR *pszClass, L_TCHAR *pszInstance, L_UINT16 nEvent, HDICOMDS hDS, L_VOID *pUserData) 
{ 
   UNREFERENCED_PARAMETER(pUserData); 
   UNREFERENCED_PARAMETER(hDS); 
   L_TCHAR szMsg[800]; 
   L_INT nRet; 
   ListBox_AddString(hList, TEXT("Command Set - N-REPORT-REQUEST")); 
   wsprintf(szMsg, TEXT("     Presentation ID: %d"), nPresentationID); 
   ListBox_AddString(hList, szMsg); 
   wsprintf(szMsg, TEXT("     Message ID: %d"), nMessageID); 
   ListBox_AddString(hList, szMsg); 
   wsprintf(szMsg, TEXT("     Affected SOP Class: %s"), pszClass); 
   ListBox_AddString(hList, szMsg); 
   wsprintf(szMsg, TEXT("     Event: %d"), nEvent); 
   ListBox_AddString(hList, szMsg); 
   /* send response */ 
   nRet = L_DicomSendNReportResponse(hNet, nPresentationID, nMessageID, pszClass, pszInstance, COMMAND_STATUS_SUCCESS, nEvent, 0); 
   if (nRet != DICOM_SUCCESS) 
      MessageBox(NULL, TEXT("Error Inside Callback Function"), TEXT(""), MB_OK); 
}

Help Version 19.0.2017.10.27

Products | Support | Contact Us | Copyright Notices
© 1991-2017 LEAD Technologies, Inc. All Rights Reserved.

LEADTOOLS DICOM C API Help

Introduction

Version History

Getting Started

Features of LEADTOOLS DICOM

Redistributables/Files To Be Included With Your Application

Functions:	L_DicomSendNReportRequest, RECEIVENREPORTREQUESTCALLBACK, RECEIVENREPORTRESPONSECALLBACK
Topics:	Working with DICOM Network Connections