An implementation that conforms to one of the SOP Classes of the Media Storage Service Class:
shall meet the requirements specified in Section I.2.1;
shall meet the requirements specified in PS3.10;
shall perform M-WRITE Operations according to the SOP Class specification identified by the SOP Class UID in the Meta File Information;
shall support the Media Storage Directory SOP Class (stored in the DICOMDIR File).
An implementation that conforms to one of the SOP Classes of the Media Storage Service Class:
shall meet the requirements specified in Section I.2.2;
shall meet the requirements specified in PS3.10;
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;
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.
An implementation that conforms to one of the SOP Classes of the Media Storage Service Class:
shall meet the requirements specified in Section I.2.3;
shall meet the requirements specified in PS3.10;
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;
shall perform M-WRITE Operations according to the SOP Class specification identified by the SOP Class UID in the Meta File Information;
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;
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.
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 PS3.2.
Table I.3-1. Allowed 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:
the subset of the Basic Directory Information Object Model supported;
When the Directory Information Module is created or updated (Directory Information Module supported), the optional standard keys that may be included in Directory Records shall be documented. Private Keys and Private Records may also be documented;
In addition to Standard Media Storage SOP Classes, implementations may support Standard Extended, Specialized and/or Private SOP Classes as defined by PS3.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 PS3.2.