IntelePACS DICOM Conformance Statement (4.3.1 and ... - Intelerad
IntelePACS DICOM Conformance Statement (4.3.1 and ... - Intelerad
IntelePACS DICOM Conformance Statement (4.3.1 and ... - Intelerad
- No tags were found...
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
Implementation Model<br />
Possible reasons for failed storage are:<br />
• Server failed to parse the image <strong>DICOM</strong> header<br />
• One or more required fields are missing from the <strong>DICOM</strong> header<br />
• One or more UID tags are related to other UIDs not present in this image<br />
• Local storage is full<br />
• The color space is not supported by the SCP AE <strong>and</strong> it is configured to reject this<br />
case.<br />
3.2.1.3 Storage Commitment<br />
The server will accept a Storage Commitment request that includes a list of SOP<br />
Instance UIDs to be committed. The server checks each SOP Instance UID with two<br />
requirements<br />
• The image is registered in the local image database<br />
• The image is physically located on the local storage medium<br />
The server creates a Storage Commitment response <strong>and</strong> transmits this to the calling AE<br />
by establishing a separate association using the AE Title, TCP/IP address <strong>and</strong> Port<br />
specified in the control database.<br />
The server will issue Storage Commitment requests to Foreign Storage SCPs. On<br />
receipt of a failure N-ACTION response code, the server will resend the SOP Instances<br />
to the Foreign storage SCP.<br />
6
Change language