| DICOM PS3.2 2025b - Conformance |
|---|
An implementation claiming DICOM conformance may choose to support one or more of the following communication mechanisms:
Conformance to the DIMSE protocol (see Section 7.1.1 DIMSE Protocol Conformance Requirements)
Conformance to DICOM Web Services (see Section 7.1.2 DICOM Web Services Conformance Requirements)
Conformance to DICOM Media Storage (see Section 7.2 DICOM Media Interchange Conformance Requirements)
Conformance to the DICOM Real-Time Video (see Section 7.8 DICOM Real-Time Video Conformance Requirements)
An implementation claiming DIMSE network conformance shall:
Conformance to a Standard or Standard Extended SOP Class implies conformance to the related IOD outlined in PS3.3, the Data Elements defined in PS3.6, and the operations and notifications defined in PS3.7.
comply with the rules governing SOP Class types outlined in Section 7.3;
accept a Presentation Context for the Verification SOP Class as an SCP if the implementation accepts any DICOM Association requests;
produce and/or process Data Sets as defined in PS3.5;
An implementation claiming DICOM Web Services conformance shall:
conform to the minimum conformance requirements defined in this Section;
provide a Conformance Statement structured according to the rules and policies in this Part and follow the template provided in Annex N;
conform to at least one Service as defined in PS3.18;
comply with the rules governing SOP Class types outlined in Section 7.3;
produce and/or process Data Sets as defined in PS3.5 and/or PS3.18;
obtain a legitimate right to a registered <org id> for creating UIDs (see PS3.5) if an implementation utilizes Privately Defined UIDs (i.e., UIDs not defined in the DICOM Standard).
| DICOM PS3.2 2025b - Conformance |
|---|