L_DicomSendNReportResponse

#include "ltdic.h"

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

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

Parameters

HDICOMNET hNet

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

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

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

L_TCHAR * pszClass

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

L_TCHAR * 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.

L_UINT16 nStatus

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

L_UINT16 nEvent

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

HDICOMDS hDS

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

Returns

Value Meaning
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

Platforms

Win32, x64, Linux.

See Also

Functions

Topics

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 20.0.2019.9.20
Products | Support | Contact Us | Intellectual Property Notices
© 1991-2019 LEAD Technologies, Inc. All Rights Reserved.

LEADTOOLS DICOM C API Help