The Hanging Protocol Information Model consists of a single entity. In response to a given C-FIND request, the SCP shall send one C-FIND response per matching Hanging Protocol Instance.
Table U.6-1 defines the Attributes of the Hanging Protocol Information Model:
Table U.6-1. Attributes for the Hanging Protocol Information Model
|
This Attribute is required if expanded or replacement character sets are used. See Section C.2.2.2 and Section C.4.1.1. |
||||
|
This Attribute shall be retrieved with Single Value Matching, Wild Card Matching or Universal Matching. |
||||
|
This Attribute shall be retrieved with Single Value Matching or Universal Matching. |
||||
|
This Attribute shall be retrieved with Sequence Matching or Universal Matching. |
||||
|
This Attribute shall be retrieved with Single Value Matching or Universal Matching. |
||||
|
This Attribute shall be retrieved with Sequence Matching or Universal Matching. |
||||
|
>>Include Table 8-1a “Enhanced SCU/SCP Coded Entry Macro with SCU Support, Matching Key Support and Mandatory Meaning” |
||||
|
This Attribute shall be retrieved with Single Value Matching or Universal Matching. |
||||
|
This Attribute shall be retrieved with Sequence Matching or Universal Matching. |
||||
|
>>Include Table 8-1a “Enhanced SCU/SCP Coded Entry Macro with SCU Support, Matching Key Support and Mandatory Meaning” |
||||
|
This Attribute shall be retrieved with Sequence Matching or Universal Matching. |
||||
|
>>Include Table 8-1a “Enhanced SCU/SCP Coded Entry Macro with SCU Support, Matching Key Support and Mandatory Meaning” |
||||
|
This Attribute shall be retrieved with Single Value Matching or Universal Matching. |
||||
|
This Attribute shall be retrieved with Sequence Matching or Universal Matching. |
||||
|
>Include Table 8-1a “Enhanced SCU/SCP Coded Entry Macro with SCU Support, Matching Key Support and Mandatory Meaning” |
||||
|
Required if Screen Minimum Color Bit Depth (0072,010C) is not present. |
||||
|
Required if Screen Minimum Grayscale Bit Depth (0072,010A) is not present. |
||||
An implementation may conform to one of the Hanging Protocol Information Model SOP Classes as an SCU, SCP or both. The Conformance Statement shall be in the format defined in PS3.2.
An implementation that conforms to one of the Hanging Protocol Information Model SOP Classes shall support queries against the Hanging Protocol Information Model using the C-FIND SCU Behavior described for the Basic Worklist Management Service Class (see Section K.4.1.2 and Section U.4.1).
An implementation that conforms to one of the Hanging Protocol Information Model SOP Classes as an SCU shall state in its Conformance Statement whether it requests Type 3 Return Key Attributes, and shall list these Optional Return Key Attributes.
An implementation that conforms to one of the Hanging Protocol Information Model SOP Classes as an SCU shall state in its Conformance Statement how it makes use of Specific Character Set (0008,0005) when encoding queries and interpreting responses.
An implementation that conforms to one of the Hanging Protocol Information Model SOP Classes as an SCU shall support transfers against the Hanging Protocol Information Model using the C-MOVE SCU baseline behavior described for the Query/Retrieve Service Class (see Section C.4.2.2.1 and Section U.4.2).
An implementation that conforms to the Hanging Protocol Information Model - GET SOP Class as an SCU shall support transfers against the Hanging Protocol Information Model using the C-GET SCU baseline behavior described for the Query/Retrieve Service Class (see Section C.4.3.2.1 and Section U.4.3).
An implementation that conforms to one of the Hanging Protocol Information Model SOP Classes as an SCP shall support queries against the Hanging Protocol Information Model using the C-FIND SCP Behavior described for the Basic Worklist Management Service Class (see Section K.4.1.3).
An implementation that conforms to one of the Hanging Protocol Information Model SOP Classes as an SCP shall state in its Conformance Statement whether it supports Type 3 Return Key Attributes, and shall list these Optional Return Key Attributes.
An implementation that conforms to one of the Hanging Protocol 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.
An implementation that conforms to one of the Hanging Protocol Information Model SOP Classes as an SCP shall support transfers against the Hanging Protocol Information Model using the C-MOVE SCP baseline behavior described for the Query/Retrieve Service Class (see Section C.4.2.3.1).
An implementation that conforms to one of the Hanging Protocol Information Model SOP Classes as an SCP, which generates transfers using the C-MOVE operation, shall state in its Conformance Statement the Hanging Protocol Storage Service Class SOP Class under which it shall support the C-STORE sub-operations generated by the C-MOVE.
An implementation that conforms to the Hanging Protocol Information Model - GET SOP Class as an SCP shall support transfers against the Hanging Protocol Information Model using the C-GET SCP baseline behavior described for the Query/Retrieve Service Class (see Section C.4.3.3.1).
An implementation that conforms to the Hanging Protocol Information Model - GET SOP Class as an SCP, which generates transfers using the C-GET operation, shall state in its Conformance Statement the Hanging Protocol Storage Service Class SOP Class under which it will support the C-STORE sub-operations generated by the C-GET.