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.