FIND-SCU provide Standard Conformance to the following SOP Class(es):
Table G.4.2-13SOP Classes Supported by FIND-SCU
|SOP Class Name||SOP Class UID||SCU||SCP|
|Hanging Protocol Information Model – FIND||1.2.840.10008.5.1.4.38.2||Yes||No|
FIND-SCU initiates but never accepts associations.
Table G.4.2-14Maximum PDU Size Received as a SCP for FIND-SCU
|Maximum PDU size received||Unlimited|
Table G.4.2-15Number of Associations as a SCP for FIND-SCU
|Maximum number of simultaneous associations||1|
FIND-SCU will only allow a single outstanding operation on an Association. Therefore, FIND-SCU will not perform asynchronous operations window negotiation.
Table G.4.2-16DICOM Implementation Class and Version for FIND-SCU
|Implementation Class UID||1.2.840.999999.3.6|
|Implementation Version Name||Viewer1.0|
FIND-SCU attempts to initiate a new association when a study is received for which an appropriate Hanging Protocol Instance is not already stored in the local database.
G.126.96.36.199.1.1 Description and Sequencing of Activities
A single attempt will be made to query the remote AE. If the query fails, for whatever reason, no retry will be performed.
G.188.8.131.52.1.2 Proposed Presentation Contexts
Table G.4.2-17Proposed Presentation Contexts for FIND-SCU and Query Remote AE
|Presentation Context Table|
|Abstract Syntax||Transfer Syntax||Role||Extended Negotiation|
|See Table G.4.2-13||See Table G.4.2-13||Implicit VR Little Endian||1.2.840.10008.1.2||SCU||None|
|Explicit VR Little Endian||1.2.840.10008.1.2.1||SCU||None|
FIND-SCU will propose multiple Presentation Contexts, one for each of the supported Transfer Syntaxes, and an additional Presentation Context with all of the supported Transfer Syntaxes, in order to determine which Transfer Syntaxes the remote SCP supports, and which it prefers.
G.184.108.40.206.1.2.1 Extended Negotiation
No extended negotiation is performed.
G.220.127.116.11.1.3 SOP Specific Conformance
G.18.104.22.168.1.3.1 SOP Specific Conformance to C-FIND SOP Classes
FIND-SCU provides standard conformance to the supported C-FIND SOP Class.
The following applies to Hanging Protocol Information Model C-FIND.
If present in the response, Specific Character Set will be used to identify character sets other than the default character set for matching between Hanging Protocol and Image Instances.
|Name||Tag||Types of Matching|
|SOP Class UID||(0008,0016)||zero length|
|SOP Instance UID||(0008,0018)||zero length|
|Hanging Protocol Name||(0072,0002)||S, *, U|
|Hanging Protocol Description||(0072,0004)||zero length|
|Hanging Protocol Level||(0072,0006)||S, U|
|Hanging Protocol Creator||(0072,0008)||zero length|
|Hanging Protocol Creation Datetime||(0072,000A)||zero length|
|Hanging Protocol Definition Sequence||(0072,000C)||SQ, U|
|>Modality||(0008,0060)||From list (US, MR, MG) or zero length|
|>Anatomic Region Sequence||(0008,2218)||From CID 4, PS 3.16 or zero length|
|>> Code Value||(0008,0100)||S, U|
|>> Coding Scheme Designator||(0008,0102)||S, U|
|>>Coding Scheme Version||(0008,0103)||zero length|
|>>Code Meaning||(0008,0104)||zero length|
|>Laterality||(0020,0060)||From list (R, L, U, B) or zero length|
|> Procedure Code Sequence||(0008,1032)||zero length|
|>Reason for Requested Procedure Code Sequence||(0040,100A)||zero length|
|Number of Priors Referenced||(0072,0014)||zero length|
|Hanging Protocol User Identification Code Sequence||(0072,000E)||From list of local coded terms or zero length|
|>Code Value||(0008,0100)||S, U|
|>Coding Scheme Designator||(0008,0102)||S, U|
|>Coding Scheme Version||(0008,0103)||zero length|
|>Code Meaning||(0008,0104)||zero length|
|Hanging Protocol User Group Name||(0072,0010)||zero length|
|Number of Screens||(0072,0100)||zero length|
|Nominal Screen Definition Sequence||(0072,0102)||zero length|
G.22.214.171.124.1.3.2 Presentation Context Acceptance Criterion
FIND-SCU does not accept associations.
G.126.96.36.199.1.3.3 Transfer Syntax Selection Policies
FIND-SCU prefers explicit Transfer Syntaxes. If offered a choice of Transfer Syntaxes in the accepted Presentation Contexts, it will apply the following priority to the choice of Presentation Context to use for the C-FIND operation:
first encountered explicit Transfer Syntax,
default Transfer Syntax.
G.188.8.131.52.1.3.4 Response Status
FIND-SCU will behave as described in Table G.4.2-19 in response to the status returned in the C-FIND response command message(s).
Table G.4.2-19Response Status for FIND-SCU and Query Remote AE Request
|Service Status||Further Meaning||Status Codes||Behavior|
|Refused||Out of Resources||A700||Current query is terminated; remaining queries continue|
|Error||Identifier does not match SOP Class||A900||Current query is terminated; remaining queries continue|
|Unable to process||Cxxx||Current query is terminated; remaining queries continue|
|Cancel||Matching terminated due to Cancel request||FE00||Ignored (should never occur, since cancels never issued)|
|Success||Matching is complete - No final Identifier is supplied||0000||Current query is terminated. If one or more Pending responses were received, logic is applied to trigger Retrieve of best suited Hanging Protocol Instances; remaining queries continue|
|Pending||Matches are continuing - Current Match is supplied and any Optional Keys were supported in the same manner as Required Keys||FF00||Identifier stored temporarily for use in setting up Retrieve.|
|Matches are continuing - Warning that one or more Optional Keys were not supported for existence and/or matching for this Identifier||FF01||Identifier stored temporarily for use in setting up Retrieve|
FIND-SCU does not accept associations.