
GE H
EALTHCARE
D
IRECTION
DOC0500644, R
EV
4 D
ISCOVERY
, L
IGHT
S
PEED AND
B
RIGHT
S
PEED
DICOM C
ONFORMANCE
S
TATEMENT
78 of 157
5.3.1.6.2 Commit response with FAILURE status
The following attributes are expected as part of DATA Set for N-Event-Request from SCP:
Attribute Tag Value
Transaction UID (0008,1195) Value received from SCP
Failed SOP Sequence (0008,1198) Value received from SCP
SOP Class UID (0008,1150) Value received from SCP
SOP Instance UID (0008,1155) Value received from SCP
Failure Reason (0008,1197) Value received from SCP
In case of complete/partial failure the user will be notified about the status and the job entry will
be paused. There is no attempt made to retry automatically the failed sop instances. However
the user can manually retry the failed jobs. Such requests will be treated as new requests. This
will go through the whole sequence of operations once again.
The failure reason is ignored.
Failed SOP instances will have their archive flag information unaltered.
Note: The archive status flag in the browser is a shared flag with local archive. When the
status is “Y”, it means that the images are archived but doesn’t specify whether on local
archive device or remote archive device. It is left to the user’s discretion whether the
local sop instances (with their archive flag set to “Y”) are to be deleted.
N-Event-Response will be sent on the same association itself. No DATA Set will be sent
along with the response.
Note: (0008, 1199) Reference SOP Sequence is not handled.
5.3.1.7 Association Acceptance Policy
A single association will be accepted at any time to receive Storage Commitment responses.
5.4 Communication Profiles
5.4.1 Supported Communication Stacks (parts 8,9)
DICOM Upper Layer (Part 8) is supported using TCP/IP.
5.4.2 TCP/IP Stack
The TCP/IP stack is inherited from a UNIX Operating System.
5.4.2.1 Physical Media Support
Ethernet v2.0, IEEE 802.3.
Komentáře k této Příručce