DICOM PS3.2 2018e - Conformance

G.4.2.3.3 Association Initiation Policy (Current)
Prev | G.4.2.3 FIND-SCU | Next

##### G.4.2.3.3 Association Initiation Policy

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.4.2.3.3.1 Activity - Query Remote AE

###### G.4.2.3.3.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.4.2.3.3.1.2 Proposed Presentation Contexts

Table G.4.2-17. Proposed Presentation Contexts for FIND-SCU and Query Remote AE

Presentation Context Table
Abstract Syntax | Transfer Syntax | Role | Extended Negotiation
--- | --- | --- | ---
Name | UID | Name | UID
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

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.4.2.3.3.1.2.1 Extended Negotiation

No extended negotiation is performed.

###### G.4.2.3.3.1.3 SOP Specific Conformance

###### G.4.2.3.3.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.

Table G.4.2.3.3.1.3.1-1. Hanging Protocol Information Model C-FIND SOP Specific Conformance

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 “Anatomic Region” 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.4.2.3.3.1.3.2 Presentation Context Acceptance Criterion

FIND-SCU does not accept associations.

###### G.4.2.3.3.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:

1. first encountered explicit Transfer Syntax,

2. default Transfer Syntax.

###### G.4.2.3.3.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-19. Response 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

Prev | Up | Next
G.4.2.3.2 Association Policies | Home | G.4.2.3.4 Association Acceptance Policy

DICOM PS3.2 2018e - Conformance