[Describe the messaging sequence of AE for a Real-World activity that is performed.
E.g.: Local Real-World Activity <2> first open an Association, triggers message <a> and message <b> on this Association before closing it. Action <c> is then performed on the system before Local Real-World Activity <1> can be launched to send message <d> on a new Association and receives message <e> on the same Association.]
[Also include its use of DICOM Web Services, including any proxy functionality between a Web Service and the equivalent DIMSE Service here.
Also include its use of DICOM-RTV Services, including any proxy functionality between a DICOM-RTV and another service provided through DIMSE Service or RESTful (i.e., storage of received video and audio with associated metadata).
[Below are examples for a Query Retrieve AE and a Web AE. Modify as applicable for your product implementation.]
Table N.7-2 lists Association parameters applicable to <AE1.>
[If your system uses different Association parameters for each AE fill in the table below for each AE and mark this section as N/A.]
Table N.7-2. Association Parameters for <AE1>
This section details the Association policies of the Application Entity when it is initiating an Association.
[For each Real-World Activity of AE1 provide subsections Section N.7.2.1.3, “Association Initiation”.x.]
[Describe the policies for creating Associations. Include the following details:
[Describe the actions and behavior that cause the product to issue N-ACTION requests and how it relates to the previous storage request, e.g., is the storage commitment initiated right after a successful C-STORE, or is the storage commitment issued after all instance in the study have been successfully stored, …]
[Describe the Association initiation behavior of your product with regards to the N-EVENT-REPORT request, e.g., whether the N-EVENT-REPORT request is sent on the same Association or whether it is initiated on a different Association.]
[Describe your system behavior if your product cannot establish an Association with the SCU, e.g., is there a retry mechanism, is that configurable, …]
The Extended Negotiation parameters for all services that are supported by the Application Entity for the Real-World Activity <Activity 1> are described in Table N.7-3.
[Describe below all the Extended Negotiation that the Application Entity requests for the <Activity 1> during Association negotiation. Use "Y" in the "Support" column to indicate support for Extended Negotiation or "N" to indicate that Extended Negotiation is not supported, and the default Value is sent in the Association field. Describe any behavior pertaining to handling extended behavior during Association initiation under this section.]
[Modify the table below to reflect the services participating in <Activity 1>.]
Table N.7-3. Extended Negotiation for <Activity 1> of <AE1> - Association Initiation
|
Applicable to all Storage SOP Classes listed under Section N.5. |
|||
|
Applicable to all Query Retrieve - FIND SOP Classes mentioned under Section N.5. |
|||
|
Applicable to all Query Retrieve - MOVE SOP Classes mentioned under Section N.5. |
|||
[Describe if the AE supports Role Negotiation in the case of Storage commitment happening synchronously i.e., if the N-ACTION and the N-EVENT-REPORT are performed in the same Association.]
This section details the Association policies of the Application Entity when it is the acceptor of an Association.
[For each Real-World Activity of AE1 provide subsections Section N.7.2.1.4, “Association Acceptance”.x.]
[Describe the service specific Association acceptance behavior of your product, e.g.
The Extended Negotiation parameters for all services that are requested by the Application Entity for the Real-World Activity <Activity 2> are described in Table N.7-4.
[Describe below all the Extended Negotiation that the Application Entity supports for <Activity 2> during Association negotiation. Use "Y" in the "Support" column to indicate support for Extended Negotiation or "N" to indicate that Extended Negotiation is not supported, and the default Value is sent in the Association field. Describe any behavior pertaining to handling extended behavior during Association acceptance under this section.]
[Modify the table below to reflect the services participating in <Activity 2>.]
Table N.7-4. Extended Negotiation for <Activity 2> of <AE1> - Association Acceptance
|
Applicable to all Storage SOP Classes listed under Section N.5. |
|||
|
Applicable to all Query Retrieve - FIND SOP Classes mentioned under Section N.5. |
|||
|
Applicable to all Query Retrieve - MOVE SOP Classes mentioned under Section N.5. |
|||
Transfer Syntax Selection Policies
This section provides tables that describe the Transfer Syntax preference for different SOP Classes or SOP Class groups when there are multiple Transfer Syntaxes provided by the Association initiator for Real-World Activity <Activity 2> of <AE1> of the system.
[The preference for Transfer Syntax selection is based on the type of data i.e., Image SOP Classes, Video SOP Classes or non-image/video SOP Classes.]
[Edit the tables below to indicate the transfer selection polices applicable to the documented activity.
If there are exceptions to the standard preference SOP Classes, mention this in the "Comments" column.
If the preference order is based on some other criteria, add another table.]
Table N.7-5. Transfer Syntax Selection Preference Order - Image SOP Classes for <AE1>