PS-2020a / part04

C.5.1.1.1 SOP Class Extended Negotiation Sub-Item Structure (A-ASSOCIATE-RQ)​

The SOP Class Extended Negotiation Sub-Item consists of a sequence of mandatory fields as defined by PS3.7. Table C.5-1 defines​ theService-class-application-informationfieldforDICOMQuery/RetrieveSOPClassesandSpecializedDICOMQuery/RetrieveSOP​ Classes that include the C-FIND operation. This field may be either one or more bytes in length (i.e., item bytes 2, 3, 4 and 5 are op-​ tional).​

Table C.5-1. SOP Class Extended Negotiation Sub-Item (Service-Class-Application-Information Field) -​

A-ASSOCIATE-RQ​

1 - combined matching requested​

3​ Fuzzy semantic matching of​This byte field defines whether or not fuzzy semantic person name Attribute matching is​ person names​ requested by the Association-requester. It shall be encoded as an unsigned binary integer​

and shall use one of the following values​

0 - fuzzy semantic matching not requested​

1 - fuzzy semantic matching requested​

4​ Timezone query adjustment​ThisbytefielddefineswhetherornottheAttributeTimezoneOffsetFromUTC(0008,0201)​ shall be used to adjust the query meaning for time and datetime fields in queries. It shall​ be encoded as an unsigned binary integer and shall use one of the following values​

0 - Timezone query adjustment not requested​

1 - Timezone query adjustment requested​

5​ EnhancedMulti-FrameImage​This byte field defines whether or not the Attribute Query/Retrieve View (0008,0053) shall​ Conversion​ be used to adjust the view returned in queries to consider conversion to or from Enhanced​ Multi-Frame Images. It shall be encoded as an unsigned binary integer and shall use one​

of the following values​

0 - Query/Retrieve View not supported​

1 - Query/Retrieve View supported​

C.5.1.1.2 SOP Class Extended Negotiation Sub-Item Structure (A-ASSOCIATE-AC)​

The SOP Class Extended Negotiation Sub-Item is made of a sequence of mandatory fields as defined by PS3.7. Table C.5-2 defines​ theService-class-application-informationfieldforDICOMQuery/RetrieveSOPClassesandSpecializedDICOMQuery/RetrieveSOP​ Classes that include the C-FIND operation. This field may be either one or more bytes in length (i.e., item bytes 2, 3, 4 and 5 are op-​ tional).​

- Standard -​

Table C.5-2. SOP Class Extended Negotiation Sub-Item (Service-Class-Application-Information Field) -​

A-ASSOCIATE-AC​

1 - combined matching performed​

3​ Fuzzy semantic matching of​This byte field defines whether or not fuzzy semantic person name Attribute matching will​ person names​ beperformedbytheAssociation-acceptor.Itshallbeencodedasanunsignedbinaryinteger​

and shall use one of the following values​

0 - fuzzy semantic matching not performed​

1 - fuzzy semantic matching performed​

4​ Timezone query adjustment​ThisbytefielddefineswhetherornottheAttributeTimezoneOffsetFromUTC(0008,0201)​ shall be used to adjust the query meaning for time and datetime fields in queries. It shall​ be encoded as an unsigned binary integer and shall use one of the following values​

0 - Timezone adjustment of queries not performed​

1 - Timezone adjustment of queries performed​

5​ EnhancedMulti-FrameImage​This byte field defines whether or not the Attribute Query/Retrieve View (0008,0053) shall​ Conversion​ be used to adjust the view returned in queries to consider conversion to or from Enhanced​ Multi-Frame Images. It shall be encoded as an unsigned binary integer and shall use one​

of the following values​

0 - Query/Retrieve View not supported​

1 - Query/Retrieve View supported​

C.5.2 Association Negotiation for C-MOVE SOP Classes​

The following negotiation rules apply to DICOM SOP Classes and Specialized DICOM SOP Classes of the Query/Retrieve Service​ Class that include the C-MOVE operation.​

The Association-requester (retrieval SCU role) shall convey in the A-ASSOCIATE request:​

•​one Abstract Syntax, in a Presentation Context, for each retrieval based SOP Class supported​

•​optionally, one SOP Class Extended Negotiation Sub-Item, for each retrieval based SOP Class​

The Association-acceptor (retrieval SCP role) of an A-ASSOCIATE request shall accept:​

•​one Abstract Syntax, in a Presentation Context, for each retrieval based SOP Class supported​

•​optionally, one SOP Class Extended Negotiation Sub-Item, for each retrieval based SOP Class​

- Standard -​

C.5.2.1 SOP Class Extended Negotiation​

The SOP Class Extended Negotiation allows, at Association establishment, peer DICOM AEs to exchange application Association​ informationdefinedbyspecificSOPClasses.ThisisachievedbydefiningtheService-class-application-informationfield.TheService-​ class-application-information field is used to define support for relational-retrievals.​

This negotiation is optional. If absent, the default condition shall be:​

•​no relational-retrieval support​

•​no Enhanced Multi-Frame Image Conversion support​

TheAssociation-requester,foreachSOPClass,mayuseoneSOPClassExtendedNegotiationSub-Item.TheSOPClassisidentified​ by the corresponding Abstract Syntax Name (as defined by PS3.7) followed by the Service-class-application-information field. This​ field defines:​

•​relational-retrieval support by the Association-requester​

•​Enhanced Multi-Frame Image Conversion support by the Association-requester​

TheAssociation-acceptorshallreturnasinglebytefield(singlesub-field)ifofferedasinglebytefield(singlesub-field)bytheAssociation-​ requester. The Association-acceptor may return either a single byte field (single sub-field) or a multiple byte field if offered a multiple​ byte field by the Association-requester. A one byte response to a multiple byte request means that the missing sub-fields shall be​ treated as 0 values.​

Note​

The restriction to return only a single byte field if that was all that was offered is because the original DICOM Standard only​ contained one byte and older systems may not be expecting more.​

The Association-acceptor, for each SOP Class Extended Negotiation Sub-Item offered, either accepts the Association-requester​ 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 relational-retrievals and Enhanced​ Multi-Frame Image Conversion are not supported (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-ASSO-​ CIATE response.​

C.5.2.1.1 SOP Class Extended Negotiation Sub-Item Structure (A-ASSOCIATE-RQ)​

The SOP Class Extended Negotiation Sub-Item consists of a sequence of mandatory fields as defined by PS3.7. Table C.5-3 defines​ theService-class-application-informationfieldforDICOMQuery/RetrieveSOPClassesandSpecializedDICOMQuery/RetrieveSOP​ Classes that include the C-MOVE and C-GET operations.​

Table C.5-3. SOP Class Extended Negotiation Sub-Item (Service-Class-Application-Information Field) -​

A-ASSOCIATE-RQ​

- Standard -​

2​ EnhancedMulti-FrameImage​This byte field defines whether or not the Attribute Query/Retrieve View (0008,0053)​ Conversion​ shall be used to adjust the view returned in queries to consider conversion to or from​ Enhanced Multi-Frame Images. It shall be encoded as an unsigned binary integer and​

shall use one of the following values​

0 - Query/Retrieve View not supported​

1 - Query/Retrieve View supported​

C.5.2.1.2 SOP Class Extended Negotiation Sub-Item Structure (A-ASSOCIATE-AC)​

The SOP Class Extended Negotiation Sub-Item consists of a sequence of mandatory fields as defined by PS3.7. Table C.5-4 defines​ theService-class-application-informationfieldforDICOMQuery/RetrieveSOPClassesandSpecializedDICOMQuery/RetrieveSOP​ Classes that include the C-MOVE and C-GET operations.​

Table C.5-4. SOP Class Extended Negotiation Sub-Item (Service-Class-Application-Information Field) -​

A-ASSOCIATE-AC​

C.5.3 Association Negotiation for C-GET SOP Classes​

WhenanSCPperformstheC-GEToperationitinducesaC-STOREoperationforthepurposeoftransmittingcompositeSOPInstances​ for Storage. This induced C-STORE operation (called a sub-operation) requires a switch from the C-GET Presentation Context to a​ Presentation Context that supports the specific C-STORE sub-operation.​

ThefollowingnegotiationrulesapplytoretrievalbasedDICOMQuery/RetrieveSOPClassesandSpecializedDICOMQuery/Retrieve​ SOP Classes that include the C-GET operation.​

The Association-requester (retrieve SCU role) in the A-ASSOCIATE request shall convey:​

a.​C-GET operation support with:​

•​one Abstract Syntax, in a Presentation Context, for each SOP Class supported​

•​and optionally, one SOP Class Extended Negotiation Sub-Item, for each retrieval based SOP Class​

b.​Induced Storage sub-operation support where the SOP Class (in the retrieval SCU role) is acting as a Storage SOP Class in the​ SCP Role. See Figure C.5-1. For each supported Storage SOP Class, the A-ASSOCIATE request contains:​

•​one Abstract Syntax in a Presentation Context​

•​oneSCP/SCURoleSelectionNegotiationSub-itemwiththeSCP-rolefieldsettoindicatesupportoftheSCProle.TheSCP/SCU​ Role Selection Negotiation shall be used as defined in PS3.7.​

- Standard -​

1.DICOM Retrieve Operation (C-GET-RQ)

2.Storage Sub-operation (C-STORE-RQ)

Acting as a storage SCP

1.DICOM Retrieve Operation (C-GET-RQ)

2.Storage Sub-operation (C-STORE-RQ)

Acting as a storage SCP

Figure C.5-1. An Example of the Sub-Operation SCU/SCP Roles​

Note​

This negotiation does not place any requirements on the SCU-flag of the SCP/SCU Role Selection Negotiation Sub-Item. It​ may be set if the Association-requester supports the Storage Service Class in the SCU role.​

The Association-acceptor (retrieve SCP role) in the A-ASSOCIATE response shall convey:​

a.​C-GET operation support with:​

•​one Abstract Syntax, in a Presentation Context, for each SOP Class supported​

b.​Induced Storage sub-operation support where the SOP Class (using the retrieval SCP role) is acting as a Storage SOP Class in​ the SCU Role. See Figure C.5-1. For each supported Storage SOP Class, the A-ASSOCIATE response contains both:​

•​one Abstract Syntax, in a Presentation Context​

•​one SCP/SCU Role Selection Negotiation Sub-item with the SCP-role field set to indicate the acceptance of the Association-​ requester's support of the SCP role. The SCP/SCU Role Selection Negotiation shall be used as defined in PS3.7.​

Note​

The negotiation does not place any requirements on the SCU-flag of the SCP/SCU Role Selection Negotiation Sub-Item. It​ may be set if the Association-acceptor accepts the Storage SCP role. Figure C.5-2 illustrates an example of the retrieve (C-​ GET) negotiation.​

Figure C.5-2 illustrates an example of the retrieve (C-GET) negotiation.​

- Standard -​

C.5.3.1 SOP Class Extended Negotiation​

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 relational-retrievals and alternative views for Enhanced Multi-Frame Image Conversion.​

DICOM AE “A”

DICOM AE “B”

DICOM AE "B" accepts the role of Retrieve SCP

DICOM AE "B" rejects the role of Storage SCP (Does not allow DICOM AE "A" to be a Storage SCU)

Figure C.5-2. An Example of the Retrieve (C-GET) Negotiation​

Extended negotiation for SOP Classes based on the retrieval services that include C-GET operations is identical to the negotiation​ defined for C-MOVE, which is defined in Section C.5.2.1 of this Annex.​

Extended negotiation for the SOP Classes of the Storage Service Class (for the C-STORE sub-operation) is defined in Annex B.​

C.6 SOP Class Definitions​

C.6.1 Patient Root SOP Class Group​

In the Patient Root Query/Retrieve Information Model, the information is arranged into four levels that correspond to one of the four​ values in element (0008,0052) shown in Table C.6.1-1.​

Table C.6.1-1. Query/Retrieve Level Values for Patient Root​

- Standard -​

Note​

The use of the word "Images" rather than "Composite Object Instances" is historical to allow backward compatibility with​ previous editions of the standard. It should not be taken to mean that Composite Object Instances of other than image type​ are not included at the level indicated by the value IMAGE.​

C.6.1.1 Patient Root Query/Retrieve Information Model​

C.6.1.1.1 E/R Model​

The Patient Root Query/Retrieve Information Model may be represented by the entity relationship diagram shown in Figure C.6-1.​

Patient

1 has

0-n

Study

1 contains

0-n

Series

1 contains

0-n

Instance

Figure C.6-1. Patient Root Query/Retrieve Information Model E/R Diagram​

C.6.1.1.2 Patient Level​

Table C.6-1 defines the Attributes at the Patient Query/Retrieve level of the Patient Root Query/Retrieve Information Model.​

Note​

1.​A description of the Attributes of this Information Model is contained in Section C.3 of this Part.​

2.​Although the Patient ID may not be globally unique, the Study Instance UID is globally unique ensuring that no two​ studies may be misidentified. The scope of uniqueness of the Patient ID may be specified using the Issuer of Patient​ ID (0010,0021).​

3.​Previously,OtherPatientIDs(0010,1000)wasincludedinthistable.ThisAttributehavebeenretired.SeePS3.42017a.​

Table C.6-1. Patient Level Attributes for the Patient Root Query/Retrieve Information Model​

- Standard -​

C.6.1.1.3 Study Level​

Table C.6-2 defines the keys at the Study Information level of the Patient Root Query/Retrieve Information Model.​

Note​

1.​A description of the Attributes of this Information Model is contained in Section C.3 of this Part.​

2.​Although the Patient ID may not be globally unique, the Study Instance UID is globally unique ensuring that no two​ studies may be misidentified. The scope of uniqueness of the Patient ID may be specified using the Issuer of Patient​ ID (0010,0021).​

Table C.6-2a. Enhanced Code Value Keys Macro with Optional Keys​

Table C.6-2b. Basic Code Value Keys Macro with Optional Keys​

- Standard -​

Table C.6-2. Study Level Keys for the Patient Root Query/Retrieve Information Model​

C.6.1.1.4 Series Level​

Table C.6-3 defines the keys at the Series Information level of the Patient Root Query/Retrieve Information Model.​

Table C.6-3. Series Level Attributes for the Patient Root Query/Retrieve Information Model​

- Standard -​

Note​

The Attribute Number of Series Related Instances is an optional key. It is, however recognized as a broadly needed key and​ return Attribute, which SCPs are strongly encouraged to support.​

C.6.1.1.5 Composite Object Instance Level​

Table C.6-4 defines the keys at the Composite Object Instance Information level of the Patient Root Query/Retrieve Information​ Model.​

Table C.6-4. Composite Object Instance Level Keys for the Patient Root Query/Retrieve Information​ Model​

Note​

1.​SOP Class UID (0008,0016) is an optional key, but it is strongly recommended that it always be returned by all SCPs,​ if matching is requested.​

2.​The Concept Name Code Sequence (0040,A043) and Content Template Sequence (0040,A504) are optional keys that​ are useful for identifying instances of various Structured Reporting Storage SOP Classes. It is strongly recommended​ that these keys be supported by the SCP for query against such instances.​

- Standard -​