DICOM PS3.4 2024d - Service Class Specifications |
---|
Association establishment is the first phase of any instance of communication between peer DICOM AEs. The Association negotiation procedure specified in PS3.7 shall be used to negotiate the supported SOP Classes or Meta SOP Classes.
Support for the SCP/SCU Role Selection Negotiation is optional. The SOP Class Extended Negotiation is optional.
The SOP Class Extended Negotiation allows, at Association establishment, peer DICOM AEs to exchange application Association information defined by specific SOP Classes. This is achieved by defining the Service-class-application-information field. The Service-class-application-information field is used to define support for fuzzy semantic matching of person names.
This negotiation is optional. If absent, the default conditions shall be:
The Association-requestor, for each SOP Class, may use one SOP Class Extended Negotiation Sub-Item. The SOP Class is identified by the corresponding Abstract Syntax Name (as defined by PS3.7) followed by the Service-class-application-information field. This field defines three or more sub-fields:
The meaning of fuzzy semantic person name matching and of timezone query adjustment is as defined in Section K.2.2.2 and Section C.2.2.2.1.
The Association-acceptor shall return a three byte field (three sub-fields) if offered a three byte field (three sub-fields) by the Association-requestor. The Association-acceptor may return more than three bytes if offered more than three bytes by the Association-requestor. A three byte response to a more than three byte request means that the missing sub-field shall be treated as 0 values.
The Association-acceptor, for each sub-field of the SOP Class Extended Negotiation Sub-Item offered, either accepts the Association-requestor proposal by returning the same value (1) or turns down the proposal by returning the value (0).
If the SOP Class Extended Negotiation Sub-Item is not returned by the Association-acceptor then fuzzy semantic matching of person names is not supported and timezone query adjustment is unspecified over the Association (default condition).
If the SOP Class Extended Negotiation Sub-Items do not exist in the A-ASSOCIATE indication they shall be omitted in the A-ASSOCIATE response.
The SOP Class Extended Negotiation Sub-Item consists of a sequence of mandatory fields as defined by PS3.7. This field shall be three or four bytes in length.
Table K.5.1-1. SOP Class Extended Negotiation Sub-Item (Service-Class-Application-Information Field) - A-ASSOCIATE-RQ
This Sub-Item is identical to Extended Negotiation Sub-Items as used by the Query/Retrieve SOP Classes. However, relational-queries (Byte 1) are not relevant since the worklist information models are single level, and date-time matching (Byte 2) is already required by the worklist information models and Enhanced Multi-Frame Image Conversion support is not applicable (Byte 5).
The SOP Class Extended Negotiation Sub-Item is made of a sequence of mandatory fields as defined by PS3.7. This field shall be three or four bytes in length.
Table K.5.1-2. SOP Class Extended Negotiation Sub-Item (Service-Class-Application-Information Field) - A-ASSOCIATE-AC
DICOM PS3.4 2024d - Service Class Specifications |
---|