DICOM Conformance Statement AIDA compact NEO - Karl Storz
DICOM Conformance Statement AIDA compact NEO - Karl Storz
DICOM Conformance Statement AIDA compact NEO - Karl Storz
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
Product Info OR1-55-E, 07/2010 • <strong>DICOM</strong> <strong>Conformance</strong> <strong>Statement</strong> <strong>AIDA</strong> <strong>compact</strong> <strong>NEO</strong><br />
<strong>DICOM</strong> <strong>Conformance</strong> <strong>Statement</strong> - <strong>AIDA</strong> <strong>compact</strong> 3.0<br />
3.2.1.2 Number of Associations<br />
<strong>AIDA</strong> initiates only one association at a time. It accepts up to four open associations.<br />
3.2.1.3 Asynchronous Nature<br />
<strong>AIDA</strong> does not use asynchronous communication (multiple outstanding transactions over a single<br />
association).<br />
3.2.1.4 Implementation Identifying Information<br />
<strong>AIDA</strong> Implementation Class UID 1.2.276.0.67.2<br />
Implementation Version Name<br />
<strong>AIDA</strong>C30<br />
3.2.2 WLM-SCU AE Specification<br />
3.2.2.1 SOP Classes<br />
The <strong>AIDA</strong> system provides Standard <strong>Conformance</strong> to the following SOP Classes:<br />
Table 3.2-1 SOP Classes for WLM-SCU AE<br />
SOP Class Name SOP Class UID SCU SCP<br />
Modality Worklist Information Model – FIND 1.2.840.10008.5.1.4.31 Yes No<br />
3.2.2.2 Association Policies<br />
See 3.2.1 General Association Policies.<br />
3.2.2.3 Association Initiation Policy<br />
<strong>AIDA</strong> attempts to initiate a new association for the following service operations:<br />
Query Modality Worklist<br />
3.2.2.3.1 Associated Real-World Activity – Query Worklist of a remote AE<br />
Depending on the configuration, the user initiates either a broad query or a patient based query. For broad<br />
queries, the configuration defines if a specific date or date range and the station AE title shall be used. For<br />
patient based queries the user specifies the attributes (Patient's Name, Patient ID, Accession Number,<br />
Scheduled Performing Physician) which the remote application should use to query its worklist database.<br />
3.2.2.3.2 Proposed Presentation Contexts – Query Worklist of a remote AE<br />
The Presentation Contexts proposed by <strong>AIDA</strong> are defined in the following table:<br />
Table 3.2-2 SOP Presentation Context Table - Query Worklist of a remote AE<br />
Presentation Context Table<br />
Abstract Syntax<br />
Transfer Syntax<br />
Name UID Name List UID List<br />
Modality Worklist<br />
Information Model<br />
– FIND<br />
1.2.840.10008.5.1.4.31 Implicit VR Little Endian<br />
Explicit VR Little Endian<br />
Explicit VR Big Endian<br />
1.2.840.10008.1.2<br />
1.2.840.10008.1.2.1<br />
1.2.840.10008.1.2.2<br />
Role Ext.<br />
Neg.<br />
SCU None<br />
3.2.2.3.2.1 SOP Specific <strong>Conformance</strong> <strong>Statement</strong> – Query Worklist of a remote AE<br />
<strong>AIDA</strong> establishes an association to the remote AE, sends the C-FIND request and closes it after receiving<br />
the responses. <strong>AIDA</strong> uses the following query keys in the C-FIND request:<br />
Table 3.2-3 Modality Worklist Query Keys<br />
Attribute Name Tag Broad<br />
Query<br />
Patient<br />
Query<br />
Addition information<br />
SOP Common Module<br />
Specific Character Set (0008,0005) Y Y ISO IR 100 or ISO IR 192<br />
Modality Worklist Module<br />
Scheduled Procedure Step Sequence (0040,0100 Y Y<br />
Modality >(0008,0060) Y *) N<br />
Station AE Title >(0040,0001) Y *) N configurable option<br />
Vers.: BB - confidential - property of <strong>Karl</strong> <strong>Storz</strong> GmbH & Co. KG -11/31-<br />
11