Материал: part02

Page 96​ DICOM PS3.2 2020a - Conformance​

Table B.4.2-14. Association Rejection Reasons​

B.4.2.1.4.1.2 Accepted Presentation Contexts​

The Storage AE will accept Presentation Contexts as shown in the Table below.​

Table B.4.2-15. Acceptable Presentation Contexts for Activity Receive Storage Commitment Response​

The Storage AE will prefer to select the Explicit VR Little Endian Transfer Syntax if multiple transfer syntaxes are offered. The Storage​ AE will only accept the SCU role (which must be proposed via SCP/SCU Role Selection Negotiation) within a Presentation Context​ for the Storage Commitment Push Model SOP Class.​

B.4.2.1.4.1.3 SOP Specific Conformance for Storage Commitment SOP Class​

B.4.2.1.4.1.3.1 Storage Commitment Notifications (N-EVENT-REPORT)​

Upon receipt of a N-EVENT-REPORT the timer associated with the Transaction UID will be canceled.​

The behavior of Storage AE when receiving Event Types within the N-EVENT-REPORT is summarized in Table B.4.2-12.​

- Standard -​

The reasons for returning specific status codes in a N-EVENT-REPORT response are summarized in Table B.4.2-13.​

B.4.2.1.4.1.4 SOP Specific Conformance for Verification SOP Class​

The Storage AE provides standard conformance to the Verification SOP Class as an SCP. If the C-ECHO request was successfully​ received, a 0000 (Success) status code will be returned in the C-ECHO response. Otherwise, a C000 (Error - Cannot Understand)​ status code will be returned in the C-ECHO response.​

B.4.2.2 Workflow Application Entity Specification​

B.4.2.2.1 SOP Classes​

EXAMPLE-INTEGRATED-MODALITY provides Standard Conformance to the following SOP Classes:​

Table B.4.2-16. SOP Classes for AE Workflow​

B.4.2.2.2 Association Policies​

B.4.2.2.2.1 General​

The DICOM standard application context name for DICOM is always proposed:​

Table B.4.2-17. DICOM Application Context for AE Workflow​

B.4.2.2.2.2 Number of Associations​

EXAMPLE-INTEGRATED-MODALITY initiates one Association at a time for a Worklist request.​

Table B.4.2-18. Number of Associations Initiated for AE Workflow​

EXAMPLE-INTEGRATED-MODALITYdoesnotsupportasynchronouscommunication(multipleoutstandingtransactionsoverasingle​

Association).​

Table B.4.2-19. Asynchronous Nature as a SCU for AE Workflow​

- Standard -​

B.4.2.2.3 Association Initiation Policy​

B.4.2.2.3.1 Activity - Worklist Update​

B.4.2.2.3.1.1 Description and Sequencing of Activities​

The request for a Worklist Update is initiated by user interaction, i.e., pressing the buttons "Worklist Update"/"Patient Worklist Query"​ orautomaticallyatspecifictimeintervals,configurablebytheuser.With"WorklistUpdate"theautomatedquerymechanismisperformed​ immediately on request, while with "Patient Worklist Query" a dialog to enter search criteria is opened and an interactive query can​ be performed.​

TheinteractivePatientWorklistQuerywilldisplayadialogforenteringdataassearchcriteria.WhentheQueryisstartedonuserrequest,​ only the data from the dialog will be inserted as matching keys into the query.​

With automated worklist queries (including "Worklist Update") the EXAMPLE-INTEGRATED-MODALITY always requests all items​ for a Scheduled Procedure Step Start Date (actual date), Modality (RF) and Scheduled Station AE Title. Query for the Scheduled​ Station AE Title is configurable by a Service Engineer.​

Upon initiation of the request, the EXAMPLE-INTEGRATED-MODALITY will build an Identifier for the C-FIND request, will initiate an​ Association to send the request and will wait for Worklist responses. After retrieval of all responses, EXAMPLE-INTEGRATED-​ MODALITY will access the local database to add or update patient demographic data. To protect the system from overflow, the EX-​ AMPLE-INTEGRATED-MODALITYwilllimitthenumberofprocessedworklistresponsestoaconfigurablemaximum.Duringreceiving​ the worklist response items are counted and the query processing is canceled by issuing a C-FIND-CANCEL if the configurable limit​ of items is reached. The results will be displayed in a separate list, which will be cleared with the next worklist update.​

EXAMPLE-INTEGRATED-MODALITY will initiate an Association in order to issue a C-FIND request according to the Modality​ Worklist Information Model.​

1.Open Association

2.C-FIND Request (Worklist Query)

3.C-FIND Response (Worklist Item) – Status - Pending

4.C-FIND Response (Worklist Item) – Status - Pending

5.C-FIND Response – Status - Success

6.Close Association

7.Select Worklist Item

Figure B.4.2-3. Sequencing of Activity - Worklist Update​

A possible sequence of interactions between the Workflow AE and a Departmental Scheduler (e.g., a device such as a RIS or HIS​ that supports the Modality Worklist SOP Class as an SCP) is illustrated in the Figure above:​

1.​The Worklist AE opens an association with the Departmental Scheduler​

2.​The Worklist AE sends a C-FIND request to the Departmental Scheduler containing the Worklist Query attributes.​

3.​The Departmental Scheduler returns a C-FIND response containing the requested attributes of the first matching Worklist Item.​

4.​The Departmental Scheduler returns another C-FIND response containing the requested attributes of the second matching​ Worklist Item.​

5.​The Departmental Scheduler returns another C-FIND response with status Success indicating that no further matching Worklist​ Items exist. This example assumes that only 2 Worklist items match the Worklist Query.​

6.​The Worklist AE closes the association with the Departmental Scheduler.​

- Standard -​

7.​The user selects a Worklist Item from the Worklist and prepares to acquire new images.​

B.4.2.2.3.1.2 Proposed Presentation Contexts​

EXAMPLE-INTEGRATED-MODALITY will propose Presentation Contexts as shown in the following table:​

Table B.4.2-21. Proposed Presentation Contexts for Activity Worklist Update​

B.4.2.2.3.1.3 SOP Specific Conformance for Modality Worklist​

The behavior of EXAMPLE-INTEGRATED-MODALITY when encountering status codes in a Modality Worklist C-FIND response is​ summarizedintheTablebelow.IfanyotherSCPresponsestatusthan"Success"or"Pending"isreceivedbyEXAMPLEINTEGRATED-​ MODALITY, a message "query failed" will appear on the user interface.​

Table B.4.2-22. Modality Worklist C-FIND Response Status Handling Behavior​

user if an interactive query. Any additional error information in the​ Response will be logged.​

The behavior of EXAMPLE-INTEGRATED-MODALITY during communication failure is summarized in the Table below.​

- Standard -​

Page 100​ DICOM PS3.2 2020a - Conformance​

Table B.4.2-23. Modality Worklist Communication Failure Behavior​

Association aborted by the SCP or network​The worklist query is marked as failed. The reason is logged and reported to the user​ layers​ if an interactive query.​

Acquired images will always use the Study Instance UID specified for the Scheduled Procedure Step (if available). If an acquisition​ is unscheduled, a Study Instance UID will be generated locally.​

The Table below provides a description of the EXAMPLEINTEGRATED-MODALITY Worklist Request Identifier and specifies the at-​ tributes that are copied into the images. Unexpected attributes returned in a C-FIND response are ignored.​

Requested return attributes not supported by the SCP are set to have no value. Non-matching responses returned by the SCP due​ to unsupported optional matching keys are ignored. No attempt is made it filter out possible duplicate entries.​

Table B.4.2-24. Worklist Request Identifier​

- Standard -​