22.07.2014 Views

scanora 5.0 dicom conformance statement - Soredex

scanora 5.0 dicom conformance statement - Soredex

scanora 5.0 dicom conformance statement - Soredex

SHOW MORE
SHOW LESS

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

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

SOREDEX<br />

SCANORA <strong>5.0</strong><br />

DICOM CONFORMANCE STATEMENT<br />

Digital Intra-oral X-ray Image Storage – For 1.2.840.10008.5.1.4.1.1.1.3 Yes No<br />

Presentation<br />

Digital Intra-oral X-ray Image Storage – For 1.2.840.10008.5.1.4.1.1.1.3.1 Yes No<br />

Processing<br />

CT Image Storage 1.2.840.10008.5.1.4.1.1.2 Yes No<br />

Enhanced CT Image Storage 1.2.840.10008.5.1.4.1.1.2.1 Yes No<br />

Secondary Capture Image Storage 1.2.840.10008.5.1.4.1.1.7 Yes No<br />

Multi-frame Grayscale Byte<br />

1.2.840.10008.5.1.4.1.1.7.2 Yes No<br />

Secondary Capture Image<br />

Storage<br />

Multi-frame Grayscale Word<br />

1.2.840.10008.5.1.4.1.1.7.3 Yes No<br />

Secondary Capture Image<br />

Storage<br />

Multi-frame True Color<br />

1.2.840.10008.5.1.4.1.1.7.4 Yes No<br />

Secondary Capture Image<br />

Storage<br />

VL Photographic Image Storage 1.2.840.10008.5.1.4.1.1.77.1.4 Yes No<br />

Storage Commitment SCU<br />

Storage Commitment Push Model 1.2.840.10008.1.20.1 Yes No<br />

4.2.3.2 Association Policies<br />

Same as in chapter 4.2.1.2 Association Policies.<br />

4.2.3.3 Association Initiation Policy<br />

4.2.3.3.1 Activity – Send Store Request<br />

The Storage SCU activity of Storage SCU AE is used as an alternative for the Storage SCU activity of Client<br />

AE. See chapter 4.2.1.3.1 Activity – Send Store Request. The same behavior applies to this activity.<br />

4.2.3.3.2 Activity – Requesting Storage Commitment<br />

4.2.3.3.2.1 Description and Sequencing of Activities<br />

The sequence of interactions is shown in the sequence diagram below:<br />

37 / 55

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!