Keywords:  DICOM SOP class, DICOM Service Command, DIMSE, SOP, Service Object Pair, Normalized, Notification service, N_Event_Report, Operation services, N_Get, N_Set, MPPS, Modality, N_Action, N_Create, N_Delete
Normalized Commands

A DICOM SOP class is a combination of a DICOM service command (DIMSE) and an information object, or a Service Object Pair (SOP). The normalized service commands services start with the letter N.

The Normalized commands provide two types of operations:

1. Notification service:

The N_Event_Report, to notify an event involving an SOP instance to a peer DIMSE-service user. This might be used by a printer to notify a film jam, or by an archive to issue the results of storage commitment.

2. Operation services:

·           The N_Get service, to request the retrieval of information from a peer DIMSE-service-user, like status information from a printer.

·           The N_Set service, to request the modification of information by a peer DIMSE-service-user, such as to update the number of images generated by a modality as part of an MPPS.

·           The N_Action service to request a peer DIMSE service-user to perform an action, such as the storage commitment of images, or to print a film.

·           The N_Create service to request a peer DIMSE service-user to create an instance of a SOP class, such as the initial film session for a printer.

·           The N_Delete service to request a peer DIMSE service-user to delete an instance of a SOP class, like deleting a film-box from a printer after it has been printed.

 The normalized domain is like a scratch pad or a clipboard. Information within the normalized objects, such as patient location, can be set, updated and the complete object can be deleted as necessary. An example of a normalized service is, therefore, the print service. A device such as a workstation creates a virtual queue, consisting of films and populated with images, all of which get deleted after the actual print has been performed.
Search Database