7.2 DICOM Media Interchange Conformance Requirements

An implementation claiming DICOM Media Interchange conformance shall:

— conform to the minimum conformance requirements defined in this section;

— provide with the implementation a Conformance Statement structured according to the rules and policies in this Part including Annex C;

— conform to at least one Standard Application Profile as defined in PS 3.11;

— support one of the Physical Media and associated Media Format, as specified by PS 3.12;

— comply with the rules governing SOP Class types outlined in Section 7.3;

— comply with the specific rules governing media storage Application Profile according to their types as specified in Section 7.4. No other types of Application Profiles may be used;

— read as an FSR or FSU all SOP Classes defined as mandatory by each of the supported Application Profiles encoded in any of the mandatory Transfer Syntaxes.

— write as an FSC or FSU all SOP Classes defined as mandatory by each of the supported Application Profiles in one of the mandatory Transfer Syntaxes;

— be able to gracefully ignore any Standard, Standard Extended, specialized or Private SOP Classes which may be present on the Storage Medium but are not defined in any of the Application Profiles to which conformance is claimed.

Note: There may be more than one Application Profile used to create or read a File-set on a single physical medium (e.g., a medium may have a File-set created with Standard and Augmented Application Profiles).

— be able to gracefully ignore Directory Records in the DICOMDIR file which do not correspond to Directory Records defined in any of the Application Profiles to which conformance is claimed.

— access the File-set(s) on media using the standard roles defined in PS 3.10;

— produce and/or process Data Sets as defined in PS 3.5 encapsulated in DICOM Files;

Note: Conformance to PS 3.5 also implies conformance to PS 3.6

— obtain legitimate right to a registered <org id> for creating UIDs (see PS 3.5) if an implementation utilizes Privately Defined UIDs (i.e., UIDs not defined in the DICOM Standard).

An implementation which does not meet all the above requirements shall not claim conformance to DICOM for Media Storage Interchange.