Q.4.3.2 Conformance Requirements

An implementation may conform to the Relevant Patient Information Model SOP Classes as an SCU and/or as an SCP.

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

Q.4.3.2.1 SCU Conformance

An implementation which conforms to one or more of the Relevant Patient Information Model SOP Classes shall support queries against the Relevant Patient Information Model described in Section Q.4.3.1 using the baseline C-FIND SCU Behavior described in Section Q.4.2.

An implementation which conforms to one or more of the Relevant Patient Information Model SOP Classes as an SCU shall state in its Conformance Statement which SOP Class(es) it supports, and which Root template(s) it may request in a query if not specified by the SOP Class. The Conformance Statement shall also state the definition of any supported template extensions.

Q.4.3.2.2 SCP Conformance

An implementation which conforms to one or more of the Relevant Patient Information Model SOP Classes shall support queries against the Relevant Patient Information Model described in Section Q.4.3.1 using the baseline C-FIND SCP Behavior described in Section Q.4.2.

An implementation which conforms to one or more of the Relevant Patient Information Model SOP Classes as an SCP shall state in its Conformance Statement which SOP Class(es) it supports, and which Root template(s) it will support in a query response if not specified by the SOP Class. The Conformance Statement shall also state the definition of any supported template extensions.

An implementation which conforms to one or more of the Relevant Patient Information Model SOP Classes as an SCP shall state in its Conformance Statement how it makes use of Specific Character Set (0008,0005) when interpreting queries, performing matching, and encoding responses.