The Defined Procedure 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 Defined Procedure Protocol Instance.
Table HH.6-1 defines the Attributes of the Defined Procedure Protocol Information Model.
Table HH.6-1. Attributes for the Defined Procedure 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 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” |
||||
|
Shall be retrieved with Single Value Matching, Wild Card 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 Sequence Matching or Universal Matching. |
||||
|
>Include Table 8-1a “Enhanced SCU/SCP Coded Entry Macro with SCU Support, Matching Key Support and Mandatory Meaning” |
||||
|
Shall be retrieved with Single Value Matching, Wild Card Matching or Universal Matching. |
||||
|
Shall be retrieved with Single Value Matching or Range Matching. |
||||
|
Shall be retrieved with Single Value Matching or Range Matching. If both Instance Creation Date and Instance Creation Time are specified for Range Matching, they are to be treated as as if they were a single DateTime Attribute e.g.,the date range July 5 to July 7 and the time range 10am to 6pm specifies the time period starting on July 5, 10am until July 7, 6pm. |
||||
|
Shall be retrieved with Single Value Matching, Wild Card Matching or Universal Matching. |
||||
|
Shall be retrieved with Single Value Matching, Wild Card Matching or Universal Matching. |
||||
|
Shall be retrieved with Single Value Matching, Wild Card Matching or Universal Matching. |
||||
|
Shall be retrieved with Single Value Matching, Wild Card Matching or Universal Matching. |
||||
|
Shall be retrieved with Single Value Matching, Wild Card Matching or Universal Matching. |
||||
|
Shall be retrieved with Single Value Matching, Wild Card 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” |
||||
An implementation may conform to one or more of the Defined Procedure Protocol Query/Retrieve SOP Classes as an SCU or SCP. The Conformance Statement shall be in the format defined in PS3.2.
An implementation that conforms to the Defined Procedure Protocol Information Model - FIND SOP Class shall support queries against the Defined Procedure 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 HH.4.1).
An implementation that conforms to the Defined Procedure Protocol Information Model - FIND SOP Class 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 the Defined Procedure Protocol Information Model - FIND SOP Class 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 the Defined Procedure Protocol Information Model - MOVE SOP Class as an SCU shall support transfers against the Defined Procedure 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 HH.4.2).
An implementation that conforms to the Defined Procedure Protocol Information Model - GET SOP Class as an SCU shall support transfers against the Defined Procedure Protocol Information Model, using the C-GET SCU baseline behavior described for the Query/Retrieve Service Class (see Section C.4.3.2).
An implementation that conforms to the Defined Procedure Protocol Information Model - FIND SOP Class as an SCP shall support queries against the Defined Procedure Protocol Information Model, using the C-FIND SCP Behavior described for the Basic Worklist Management Service Class (see Section K.4.1.3).
Note
The contents of the Model Specification Sequence (0018,9912) would be useful to index for systems that support query or selection of appropriate Protocols for specific systems.
An implementation that conforms to the Defined Procedure Protocol Information Model - FIND SOP Class 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 the Defined Procedure Protocol Information Model - FIND SOP Class 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 the Defined Procedure Protocol Information Model - MOVE SOP Class as an SCP shall support transfers against the Defined Procedure Protocol Information Model, using the C-MOVE SCP baseline behavior described for the Query/Retrieve Service Class (see Section C.4.2.3.1).
Note
It is expected that a device that does not match the contents of the Model Specification Sequence (0018,9912) will not execute the Protocol.
An implementation that conforms to the Defined Procedure Protocol Information Model - MOVE SOP Class as an SCP, which generates transfers using the C-MOVE operation, shall state in its Conformance Statement appropriate Storage Service Class, under which it shall support the C-STORE sub-operations generated by the C-MOVE.
An implementation that conforms to the Defined Procedure Protocol Information Model - GET SOP Class as an SCP shall support retrievals against the Defined Procedure Protocol Information Model using the C-GET SCP baseline behavior described for the Query/Retrieve Service Class in Section C.4.3.3.