The Application Event Logging Service Class defines an application-level class-of-service that facilitates the network transfer of Event Log Records to be logged or recorded in a central location.
The Application Event Logging Service Class addresses the class of application specific logs (e.g., procedural event logs) that are managed by a medical application. The Application Event Logging Service Class does not specify the means of accessing the central logs.
Note: This Service Class does not address system security or audit logs that are managed by general system logging applications, and which may use non-DICOM protocols (e.g., SYSLOG).
Two peer DICOM AEs implement a SOP Class of the Application Event Logging Service Class with one serving in the SCU role and one serving in the SCP role. SOP Classes of the Application Event Logging Service Class are implemented using the DIMSE-N N-ACTION service as defined in PS 3.7.
The N-ACTION service conveys the following semantics:
— The SCU notifies the SCP that an event has occurred that the SCP should record in a log. The Action Information of the N-ACTION-RQ contains the information about the event.
— The SCP responds with a confirmation of the status of the recording action.
The association negotiation procedure is used to negotiate the supported SOP Classes. PS 3.7 specifies the association procedure. The Application Event Logging Service Class does not support extended negotiation.
The release of an association shall not have any effect on the contents of the log managed by the SCP.