DICOM Conformance Statement - InCenter - Philips
DICOM Conformance Statement - InCenter - Philips
DICOM Conformance Statement - InCenter - Philips
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
<strong>DICOM</strong> <strong>Conformance</strong> <strong>Statement</strong> Page 41 of 82<br />
Figure 12: Sequencing of RWA Query/Retrieve Image<br />
For each retrieve request (selected from query results) the VF Workstation AE<br />
accepts an association from the selected peer entity (Archive) and uses it to receive<br />
image Storage (C-STORE) requests and send subsequent responses. On request of<br />
the Storage SCU (Archive) the association is released.<br />
4.2.2.4.1.2. Accepted Presentation Contexts<br />
The VF Workstation AE will accept Presentation Contexts as shown in Table 49.<br />
Table 49: Acceptable Presentation Contexts for Query/Retrieve Image<br />
Presentation Context Table<br />
Abstract Syntax Transfer Syntax<br />
Name UID Name List UID List<br />
© Koninklijke <strong>Philips</strong> Electronics N.V. 2009<br />
XPS031-090132.02 Veradius R1.1 6 Jul 2009<br />
Role<br />
Extended<br />
Negotiation<br />
Any defined SOP class ELE 1.2.840.10008.1.2.1 SCP None<br />
EBE 1.2.840.10008.1.2.2<br />
ILE 1.2.840.10008.1.2<br />
Note: For performance reasons the ELE transfer syntax is preferred and shall be chosen in case<br />
multiple transfer syntaxes are proposed in the association negotiation.<br />
The VF Workstation AE shall accept all contexts in the intersection of the proposed<br />
and acceptable presentation contexts. This means that the VF Workstation AE<br />
accepts multiple proposed presentation contexts with the same SOP class but<br />
different transfer syntaxes.<br />
There is no check for duplicate contexts, and these will therefore be accepted.<br />
4.2.2.4.1.3. SOP Specific <strong>Conformance</strong> for SOP Classes<br />
4.2.2.4.1.3.1. Verification<br />
The VF Workstation AE provides standard conformance to the Verification service<br />
class.<br />
The status code behavior is as summarized in Table 50.