DICOM PS3.4 2020c - Service Class Specifications

P.2 Procedural Event Logging SOP Class Definition (Current)
Prev | P Application Event Logging Service Class (Normative) | Next

## P.2 Procedural Event Logging SOP Class Definition

The Procedural Event Logging SOP Class allows SCUs to report to an SCP the events that are to be recorded in a Procedure Log SOP Instance, as described in PS3.3. This allows multiple devices participating in a Study to cooperatively construct a log of events that occur during that Study.

The multiple procedural events reported through this SOP Class are related by Patient ID, Study Instance UID, Study ID, and/or Performed Location. The mechanism by which multiple devices obtain these shared identifiers is not defined by this SOP Class.

### Note

The Modality Worklist or UPS SOP Classes may be used for this purpose. For simple devices that cannot support worklist SOP Classes, the SCP may be able to use Performed Location, or the SCU AE Title, to relate the use of the device to a particular procedure.

The SCP may also provide for recording events for which the SCU does not provide identifiers for matching. The mechanism by which the SCP determines the association of such an unidentified event with the log for a specific procedure is not defined by this SOP Class.

### Note

The network address and/or AE Title of the SCU may be used to identify the device as a participant in a particular procedure.

### P.2.1 DIMSE Service Group

The DIMSE-N Services applicable to the Procedural Event Logging SOP Class are shown in Table P.2-1.

Table P.2-1. DIMSE Service Group Applicable to Procedural Event Logging

DICOM Message Service Element | Usage SCU/SCP
--- | ---
N-ACTION | M/M

The DIMSE-N Services and Protocol are specified in PS3.7.

Prev | Up | Next
P Application Event Logging Service Class (Normative) | Home | P.2.2 Operation

DICOM PS3.4 2020c - Service Class Specifications