scanora 5.0 dicom conformance statement - Soredex

More documents

Recommendations

Info

SOREDEX SCANORA <strong>5.0</strong> DICOM CONFORMANCE STATEMENT FIGURE 8: SEQUENCE OF ACTIVITY – REQUESTING STORAGE COMMITMENT The N-ACTION message is sent automatically, after an image is stored, after a configurable time period. The AE then waits for a N-EVENT-REPORT from the SCP during the same association. This wait time can be configured. If the N-EVENT-REPORT message is not received, the association is closed, and the Storage Commitment SCP is expected to initiate another association for sending the N-EVENT-REPORT, see 4.2.3.4.1 Activity – Receive Storage Commitment Result. The status of the Storage Commitment is displayed for the operator: commitment pending, waiting for storage commitment retry, committed or storage commitment failed. The request can be resent or aborted by the user. 4.2.3.3.2.2 Proposed Presentation Context SCANORA Storage SCU AE is capable of proposing the Presentation Contexts shown in the following table: TABLE 4-22: PRESENTATION CONTEXT TABLE OF REQUESTING STORAGE COMMITMENT Presentation Context Table Abstract Syntax Transfer Syntax Role Extended Negotiation Name UID Name List UID List Storage Commitment Push Model 1.2.840.10008. 1.20.1 Explicit VR Little Endian, Implicit VR Little Endian, Explicit VR Big Endian 1.2.840.10008.1.2, 1.2.840.10008.1.2.1, 1.2.840.10008.1.2.2 SCU None 4.2.3.3.2.3 SOP Specific Conformance The supported operations are described below. 38 / 55
SOREDEX SCANORA <strong>5.0</strong> DICOM CONFORMANCE STATEMENT 4.2.3.3.2.3.1 Storage Commitment Operations (N-ACTION) The storage Commitment request can be configured to be sent automatically, after the storing of an image. Only one SOP Instance is included in one request. The request can be sent for all the same SOP Classes as can be stored, see 4.2.3.3.1 Activity – Send Store Request. The request can be configured to be resent until a successful N-ACTION Response or N-EVENT-REPORT with Event Type ID equal to 1 is received. The maximum retry limit and retry interval can be configured. A new Transaction UID is used for the retries. The request can also be resent manually by the operator. The Storage Media File-Set ID and UID attributes are not supported. 4.2.3.3.2.3.2 Storage Commitment Operations (N-EVENT-REPORT) Event Type Name Event Type ID Behavior Storage Commitment Request Successful Storage Commitment Request Complete - Failures Exist 1 The References SOP Instances under References SOP Sequence (0008,1199) are considered as 'Committed' in the SCANORA database. SCANORA can be configured to automatically delete these images immediately or after a delay of either 12, 24 or 48 hours. A log entry is written of each deleted image. 2 The References SOP Instances under References SOP Sequence (0008,1199) are treated the same way as in the success case (Event Type 1). The referenced SOP Instances under Failed SOP Sequence (0008,1198) are considered as 'Commitment failed''. These images will not be deleted. SCANORA can be configured to automatically resend the Commitment Request (N-ACTION), after Event Type ID equal to 2 is received. The maximum retry limit and retry interval can be configured. The operator can also manually resend the Commitment Request. 4.2.3.3.3 Activity – Send Verification Same as in 4.2.1.3.5 Activity – Send Verification. 39 / 55
Page 1 and 2: SOREDEX SCANORA 5.0 DICOM CONFORMAN
Page 37: SOREDEX SCANORA 5.0 DICOM CONFORMAN
Page 55: SOREDEX SCANORA 5.0 DICOM CONFORMAN

scanora 5.0 dicom conformance statement - Soredex

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?