DICOM PS3.2 2023a - Conformance

N.5.2.5 Storage Service

N.5.2.5.1 SCU of the Storage SOP Classes

As a Service Class User of the Storage Service Class, the <Product> uses the C-STORE-RQ message to request storage of DICOM objects by a remote SCP. See Section N.1.1 Content and Transfer in the Overview for the list of supported SOP Classes.

For details regarding the content of SOP Instances that are created by the system, see Section N.9, which describes the underlying IOD of the supported SOP Classes.

[Provide some details regarding the triggering of storage requests (e.g., automatically when an instance is stored, automatically when the study is closed, or initiated by the user).]

[Describe when and how your product divides sets of instances into multiple series and or studies and how these are ordered.]

[Describe the behavior of your product in the case of a C-STORE operation using a referenced pixel data Transfer Syntax such as JPIP Referenced Pixel Data Transfer Syntax. This includes the duration of validity of the reference.]

N.5.2.5.1.1 Transcoding of Transfer Syntaxes

[For implementations that store locally using multiple Transfer Syntaxes and if the SCU includes multiple Transfer Syntaxes in each Presentation Context it negotiates, the following can provide a useful summary for assessing compatibility with receiving systems. If this information is not useful for your product, replace the content of this Section with the text "N/A" and append "- N/A" to the end of the section title.]

Table N.5-9 describes supported transcodings between the locally stored encoding of SOP Instances and the negotiated Transfer Syntax. The following Values can be used:

  • SUPPORTED: Transcoding is possible and same SOP Instance UID is re-used.

  • NEW_UID: Transcoding is possible; however a new SOP Instance is created for transfer, e.g., due to lossy compression.

  • NOT_SUPPORTED: Transcoding is not possible.

[Table N.5-9 shows an example of how this transcoding could look, modify and add columns and rows as needed for Transfer Syntaxes supported by your product. If you need to provide further details on specific transcoding those can be added as notes below the table.]

Table N.5-9. Transcoding of Transfer Syntaxes

Stored Transfer Syntax

Sent Transfer Syntax

Implicit VR Little Endian

Explicit VR Little Endian

JPEG Lossless, Non-Hierarchical, First-Order Prediction (Process 14)

JPEG Baseline (Process 1)

Implicit VR Little Endian

SUPPORTED (See Note 1)

SUPPORTED

NEW_UID

Explicit VR Little Endian

SUPPORTED

SUPPORTED

NEW_UID

JPEG Lossless, Non-Hierarchical, First-Order Prediction (Process 14)

SUPPORTED

SUPPORTED

NEW_UID

JPEG Baseline (Process 1)

NOT_SUPPORTED

NOT_SUPPORTED

NOT_SUPPORTED

ACME Private Transfer Syntax 1 (See Note 2)

NOT_SUPPORTED

SUPPORTED

NOT_SUPPORTED

NOT_SUPPORTED


Note

  1. Explanation of the details of the transcoding (e.g., for known Private Attributes, the correct VR will be used. All others will be encoded as VR UN)

  2. This Private Transfer Syntax is using Explicit VR Little Endian with compressed pixel data.

DICOM PS3.2 2023a - Conformance