7.4 Rules Governing Types of Application Profiles

Application Profile used in a Conformance Statement shall be of one of three basic types. Each Application Profile in an implementation claiming conformance to the DICOM Standard shall be handled in accordance with the following rules, as dictated by the type of Application Profile.

7.4.1 Standard Application Profile

A Standard Application Profile shall:

  1. conform to all relevant Parts of DICOM with no changes;

  2. support only one of the Physical Media and associated Media Format, as specified by PS 3.12.

To claim conformance to a Standard Application Profile, an implementation shall make a declaration of this fact in its Conformance Statement, and identify its selected options, roles, and behavior.

An implementation of a Standard Application Profile may extend Standard SOP Classes of this Standard application profile. Such Standard Extended SOP Classes shall meet the requirements specified in Section 7.3.

7.4.2 Augmented Application Profile

An Augmented Application Profile shall:

  1. be a proper super set of the Standard Application Profile. It adds the support of additional Standard or Standard Extended SOP Classes;

  2. use the same Physical Media and its associated Media Format specified in the corresponding Standard Application Profile;

  3. not include Specialized or Private SOP Classes.

An Augmented Application Profile may:

  1. include one or more Standard or Standard Extended SOP Classes in addition to those of the corresponding Standard Application Profile. These additional SOP Classes may be mandatory or optional;

  2. include the extensions (e.g. additional required keys, additional directory records) to the Basic Directory Information Object corresponding to the SOP Classes defined in a);

  3. add one or more new roles (FSC, FSR, FSU).

To claim conformance to an Augmented Application Profile, an implementation shall make a declaration of this fact in its Conformance Statement, and shall identify the Standard Application Profile from which it is derived and specify the augmentations. The implementation shall also identify its selected options, roles, and behavior.

An implementation of a Augmented Application Profile may:

  1. extend Standard SOP Classes of the corresponding Standard application profile. Such Standard Extended SOP Classes shall meet the requirements specified in Section 7.3;

  2. also claim conformance to the Standard Application Profile on which this Augmented Profile is based. In this case, FSC and FSU implementations shall be able to restrict their behavior to the Standard Application Profile (i.e., provide a means to write only the Standard or Standard Extended SOP Classes defined in the corresponding Standard Application Profile).

7.4.3 Private Application Profile

A Private Application Profile:

— conforms to PS 3.10 and to the Media Storage Service Class specified in PS 3.4;

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

Note: The intent of these two conditions is to ensure that at least the DICOMDIR is readable by other APs.

— complies with the rules governing SOP Classes in section 7.3.

To claim conformance to a Private Application Profile, an implementation shall make a declaration of this fact in its Conformance Statement, and shall provide a description of the Application Profile patterned after the descriptions in PS 3.11. The implementation shall also identify its selected options, roles, and behavior.

Note: An implementation that does not meet the provisions of Section 7, including the types of Application Profile, is not conformant to DICOM and so is outside the scope of DICOM conformance. Such an implementation is not an Application Profile in DICOM terminology. For example, if an implementation chooses to write DICOM files onto media that is not in PS 3.12, or use a file system not defined for a specific media type in PS 3.12, then that implementation cannot claim that it conforms to the DICOM Standard using that media or file system.