| DICOM PS3.2 2023a - Conformance |
|---|
As a Service Class Provider of the Study Root Q/R - Information Model - FIND SOP Class, the <Product> uses the C-FIND-RSP to communicate matches back to the SCU. It supports the Matching Keys listed in Table N.5-18 for hierarchical queries.
In the "Matching Type" column, the following Values can be used:
SINGLE_VALUE: SCP can perform single Value matching on this Attribute.
UID: SCP can perform List of UID matching on this Attribute.
WILDCARD: SCP can perform Wildcard matching on this Attribute.
SEQUENCE: SCP can perform sequence matching on this Attribute.
UNIVERSAL: SCP can provide the Attribute in the C-FIND response (universal matching).
[The table below contains a set of Attributes (standard Attributes as well as private Attributes) that could be supported by a product. Add and remove Attributes in order to match your product implementation using the matching type as defined above. If multiple codes are supported, list all of them. Use the "Comments" column if clarification is needed.]
[If <product> supports Extended Negotiation for Relational Queries, describe supported matching Attributes.]
[Document your product behavior in case you are encountering non supported private Attributes.]
[Describe the behavior of the product if it receives a C-FIND-CANCEL request.]
[Document your product's query capabilities and behavior for handling non-default character sets, especially for handling person names (VR of PN).]
[If your product supports Extended Negotiation for fuzzy semantic matching of person names describe how matching is performed, e.g., whether your matching is insensitive to case, position, accent, or character encoding, or whether you support phonetic matching.]
| DICOM PS3.2 2023a - Conformance |
|---|