K.6.2.3 Conformance Requirements

An implementation may conform to the General Purpose Worklist SOP Class as an SCU and/or as an SCP.

An implementation that conforms to the General Purpose Worklist SOP Class shall also support the General Purpose Worklist Management Meta SOP Class.

The Conformance Statement shall be in the format defined in Annex A of PS 3.2.

K.6.2.3.1 SCU Conformance

An implementation that conforms to the General Purpose Worklist SOP Class shall support queries against the Worklist Information Model described in Section K.6.2.2 of this Annex using the baseline C-FIND SCU Behavior described in Section K.4.1.2 of this Annex.

An implementation that conforms to the General Purpose Worklist SOP Class as an SCU shall state in its Conformance Statement whether it requests matching on Optional Matching Key Attributes. If it requests Type 3 Return Key Attributes, then it shall list these Optional Return Key Attributes.

An implementation that conforms to the General Purpose Worklist SOP Class as an SCU shall state in its Conformance Statement whether or not it supports extended negotiation of fuzzy semantic matching of person names.

An implementation that conforms to the General Purpose Worklist SOP Class as an SCU shall state in its Conformance Statement how it makes use of Specific Character Set (0008,0005) and Timezone Offset From UTC (0008,0201) when encoding queries and interpreting responses.

K.6.2.3.2 SCP Conformance

An implementation that conforms to the General Purpose Worklist SOP Class shall support queries against the Worklist Information Model described in Section K.6.2.2 of this Annex using the C-FIND SCP Behavior described in Section K.4.1.3 of this Annex.

An implementation that conforms to the General Purpose Worklist SOP Class as an SCP shall state in its Conformance Statement whether it supports matching on Optional Matching Key Attributes. If it supports Type 3 Return Key Attributes, then it shall list all Optional Return Key Attributes which it supports.

An implementation that conforms to the General Purpose Worklist SOP Class as an SCP shall state in its Conformance Statement whether or not it supports extended negotiation of fuzzy semantic matching of person names. If fuzzy semantic matching of person names is supported, then the mechanism for fuzzy semantic matching shall be specified.

An implementation that conforms to the General Purpose Worklist SOP Class as an SCP shall state in its Conformance Statement how it makes use of Specific Character Set (0008,0005) and Timezone Offset From UTC (0008,0201) when interpreting queries, performing matching and encoding responses.