L_INT LDicomNet::SendNReportResponse(nPresentationID, nMessageID, pszClass, pszInstance, nStatus, nEvent, pDS)
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.
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.
Class affected by the request. This will be an SOP Class or an SOP MetaClass.
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.
The status of the original request. For a list of possible values, refer to Status Constants.
An application specific event for which a report is to be generated.
Application specific data set which contains information related to the operation.
|>0||An error occurred. Refer to Return Codes.|
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
For an example, refer to LDicomNet::OnReceiveNReportRequest.
Medical Web Viewer .NET
.NET, Java, Android, and iOS/macOS Assemblies
C API/C++ Class Libraries