I.3 Conformance

I.3.1 Conformance as an FSC

An implementation which conforms to one of the SOP Classes of the Media Storage Service Class:

  1. shall meet the requirements specified in Section I.2.1;

  2. shall meet the requirements specified in PS 3.10;

  3. shall perform M-WRITE Operations according to the SOP Class specification identified by the SOP Class UID in the Meta File Information;

  4. shall support the Media Storage Directory SOP Class (stored in the DICOMDIR File).

I.3.2 Conformance as an FSR

An implementation which conforms to one of the SOP Classes of the Media Storage Service Class:

  1. shall meet the requirements specified in Section I.2.2;

  2. shall meet the requirements specified in PS 3.10;

  3. shall perform M-READ Operations according to the SOP Class specification identified by the SOP Class UID in the Meta File Information. M-READ of non-supported SOP Classes shall simply result in ignoring such stored Data Sets;

  4. shall read DICOMDIR Files without a Directory Information Module or with a Directory Information Module including Directory Records of a Type not supported by the implementation.

I.3.3 Conformance as an FSU

An implementation which conforms to one of the SOP Classes of the Media Storage Service Class:

  1. shall meet the requirements specified in Section I.2.3;

  2. shall meet the requirements specified in PS 3.10;

  3. shall perform M-READ Operations according to the SOP Class specification identified by the SOP Class UID in the Meta File Information. M-READ of unsupported SOP Classes shall simply result in ignoring such stored Data Sets;

  4. shall perform M-WRITE Operations according to the SOP Class specification identified by the SOP Class UID in the Meta File Information;

  5. shall support the Media Storage Directory SOP Class (stored in the DICOMDIR File). Directories containing a Directory Information Module shall be updated by an FSU. Directories containing no Directory Information Module shall not be updated by an FSU;

  6. shall read DICOMDIR Files without a Directory Information Module or with a Directory Information Module including Directory Records of a Type not supported by the implementation.

I.3.4 Conformance Statement Requirements

An implementation of the Media Storage Service Class may support one or more Roles as specified in Table I.3-1. In addition, the implementation may conform to one or more of the SOP Classes of the Media Storage Service Class defined in Section I.4. The Conformance Statement shall be in the format defined by PS 3.2.

Table I.3-1Allowed Combinations of Roles

Roles FSR FSC FSU
With a Directory Information Module Allowed Allowed Allowed Directory shall be updated
With no Directory Information Module Allowed Allowed Allowed Directory shall not be updated

The following aspects shall be documented in the Conformance Statement of any implementation claiming conformance to one of the Media Storage SOP Classes:

I.3.5 Standard Extended, Specialized, and Private Conformance

In addition to Standard Media Storage SOP Classes, implementations may support Standard Extended, Specialized and/or Private SOP Classes as defined by PS 3.2.

For all three types of SOP Classes, implementations shall be permitted to conform as an FSC, FSR, both or as an FSU. The Conformance Statement shall be in the format defined in PS 3.2.