4.2.3. Workflow Application Entity Specification¶
4.2.3.1. SOP Classes¶
The Workflow Application Entity provides Standard Conformance to the following SOP Class(es) :
SOP Class Name |
SOP Class UID |
SCU |
SCP |
---|---|---|---|
Modality Performed Procedure Step |
1.2.840.10008.3.1.2.3.3 |
Yes |
Yes |
Instance Availability Notification |
1.2.840.10008.5.1.4.33 |
Yes |
No |
Modality Worklist |
1.2.840.10008.5.1.4.31 |
No |
Yes |
Unified Procedure Step - Push SOP Class SCP |
1.2.840.10008.5.1.4.34.6.1 |
No |
Yes |
Unified Procedure Step - Watch SOP Class SCP |
1.2.840.10008.5.1.4.34.6.2 |
No |
Yes |
Unified Procedure Step - Pull SOP Class SCP |
1.2.840.10008.5.1.4.34.6.3 |
No |
Yes |
Unified Procedure Step - Event SOP Class SCP |
1.2.840.10008.5.1.4.34.6.4 |
No |
Yes |
4.2.3.2. Association Policies¶
4.2.3.2.1. General¶
The DICOM standard Application Context Name for DICOM 3.0 is always accepted and proposed:
Application Context Name |
1.2.840.10008.3.1.1.1 |
4.2.3.2.2. Number of Associations¶
The Workflow Application Entity can support multiple simultaneous Associations requested by peer AEs. The maximum total number of simultaneous Associations accepted from peer AEs is configurable. It is unlimited by default.
The Workflow Application Entity initiates one Association at a time to send Modality Performed Procedure Step N-CREATE and N-SET request and one Association at a time to send Instance Availability Notifications to peer AEs.
Maximum number of simultaneous Associations requested by peer AEs |
No Maximum Limit (Configurable) |
Maximum number of simultaneous Associations initiated by the Workflow Application Entity to peer Modality Performed Procedure Step SCPs |
1 |
Maximum number of simultaneous Associations initiated by the Workflow Application Entity to peer Instance Availability Notification SCPs |
1 |
4.2.3.2.3. Asynchronous Nature¶
The Workflow Application Entity supports asynchronous communication (multiple outstanding transactions over a single Association). The maximum number of outstanding asynchronous transactions is configurable. It is unlimited by default.
Maximum number of outstanding asynchronous transactions |
No Maximum Limit (Configurable) |
4.2.3.2.4. Implementation Identifying Information¶
The implementation information for the Workflow Application Entity is:
Implementation Class UID |
1.2.40.0.13.1.3 |
Implementation Version Name |
dcm4che-5.xx.yy |
All Application Entities of dcm4che DICOM Archive 5 use the same Implementation Version Name. This Version Name is updated with each new release of the product software.
4.2.3.3. Association Initiation Policies¶
4.2.3.3.1. Activity - Forward Modality Performed Procedure¶
4.2.3.3.1.1. Description and Sequencing of Activities¶
<TODO>
4.2.3.3.1.2. Proposed Presentation Contexts¶
The Workflow AE will propose Presentation Contexts as shown in the following table:
Presentation Context Table |
|||||
---|---|---|---|---|---|
Abstract Syntax |
Transfer Syntax |
Role |
Extended Negotiation |
||
Name |
UID |
Name |
UID |
||
Modality Performed Procedure Step |
1.2.840.10008.3.1.2.3.3 |
DICOM Implicit VR Little Endian |
1.2.840.10008.1.2 |
SCU SCP |
None |
DICOM Explicit VR Little Endian |
1.2.840.10008.1.2.1 |
4.2.3.3.1.3. SOP Specific Conformance¶
<TODO>
4.2.3.3.2. Activity - Send Instance Available Notification¶
4.2.3.3.2.1. Description and Sequencing of Activities¶
<TODO>
4.2.3.3.2.2. Proposed Presentation Contexts¶
The Workflow AE will propose Presentation Contexts as shown in the following table:
Presentation Context Table |
|||||
---|---|---|---|---|---|
Abstract Syntax |
Transfer Syntax |
Role |
Extended Negotiation |
||
Name |
UID |
Name |
UID |
||
Instance Availability Notification |
1.2.840.10008.5.1.4.33 |
DICOM Implicit VR Little Endian |
1.2.840.10008.1.2 |
SCU |
None |
DICOM Explicit VR Little Endian |
1.2.840.10008.1.2.1 |
4.2.3.3.2.3. SOP Specific Conformance¶
<TODO>
4.2.3.4. Association Acceptance Policies¶
<TODO>