DICOM PS3.4 2023e - Service Class Specifications
KK.2.4 Conformance (Current)
Prev  KK.2 Inventory Creation SOP Class  Next
PS3.4 > Storage Management Service Class > Inventory Creation SOP Class > Conformance

KK.2.4 Conformance

An implementation may claim conformance to this SOP Class as an SCU, SCP or both. The Conformance Statement shall be in the format defined in PS3.2.

KK.2.4.1 SCU Conformance

An implementation that is conformant to the Inventory Creation SOP Class as an SCU shall meet conformance requirements for:

  • the operations and actions that it invokes,

  • the notifications that it receives.

KK.2.4.1.1 Operations

The SCU shall document in the SCU Operations Statement:

  • the behavior and actions that cause the SCU to generate an N-ACTION primitive (Initiate, Request Status, Cancel, Pause, or Resume),

  • the behavior and actions taken by the SCU upon receiving an N-ACTION error status.

KK.2.4.1.2 Notifications

The SCU shall document in the SCU Notifications Statement:

  • the behavior and actions taken by the SCU upon receiving an N-EVENT-REPORT primitive (Inventory Terminated with Instances, Inventory Status, or Inventory Terminated without Instances).

Prev  Up  Next
KK.2.3.3 Service Class User Behavior  Home  KK.2.4.2 SCP Conformance
DICOM PS3.4 2023e - Service Class Specifications