Which Optional Keys it supports for existence (i.e., to be returned in responses) and which for matching.

Which Attributes it supports in Items of those Key Attributes that are Sequences.

Whether it supports Relational Search. If it supports Relational Search, then it shall also support Extended Negotiation of Relational-queries as an SCP.

Whether or not it supports Extended Negotiation of combined date-time matching, fuzzy semantic matching of person names, empty value matching, and/or multiple value matching. If fuzzy semantic matching of person names is supported, then the mechanism for fuzzy semantic matching shall be specified.

Whether it supports case-insensitive matching for PN VR Attributes, and list the Attributes for which this applies.

How it uses Specific Character Set (0008,0005) and Timezone Offset From UTC (0008,0201) when interpreting queries, performing matching and encoding responses.

Any limitations it places on the number of C-FIND responses.

The conditions after which a Record Key (0008,041B) value is not valid to allow resumption of a C-FIND operation.

Any non-DICOM mechanisms used to access SOP Instances that may be specified by a File Access URI (0008,0409), including protocols (such as NFS, SMB, or HTTP), and use of folders and/or container files (ZIP, TAR, GZIP, TARGZIP, BLOB) for the SOP Instances. If such mechanisms are used, the use of Metadata Sequence (0008,041D) or Updated Metadata Sequence (0008,041E) shall be described.

Whether it provides responses that include entities from multiple repositories (federation), and how it handles differences in support for Attribute matching across those repositories in constructing responses.