15.12.2012 Views

Digital Imaging and Communications in Medicine (DICOM)

Digital Imaging and Communications in Medicine (DICOM)

Digital Imaging and Communications in Medicine (DICOM)

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

168<br />

Chapter 7 <strong>DICOM</strong> SOPs: Basic<br />

(Fig. 51), our digital archive (typically considered a server) SCP for CT scanner<br />

plays the role of a CT image storage SCU (typically considered a client) when<br />

it sends images to another CT image storage SCP (such as workstation). As <strong>in</strong><br />

nearly all <strong>DICOM</strong> SOPs, the SCU <strong>in</strong>itiates the communication <strong>and</strong> the SCP<br />

replies to it; therefore, we cannot so easily assign the client/server labels as we<br />

might like.<br />

For another example, th<strong>in</strong>k about a PACS archive application us<strong>in</strong>g <strong>DICOM</strong><br />

as its <strong>in</strong>ternal language. To f<strong>in</strong>d an image <strong>in</strong> its database, it will issue a C-F<strong>in</strong>d-<br />

Rq to itself <strong>and</strong> will reply to it with a C-F<strong>in</strong>d-Rsp, thus be<strong>in</strong>g a C-F<strong>in</strong>d SCU <strong>and</strong><br />

SCP at the same time.<br />

Another popular expectation is that SCP is somewhat more advanced than<br />

SCU <strong>and</strong> <strong>in</strong>cludes SCU as a subfunction. This is not at all the case. SCPs <strong>and</strong><br />

SCUs can often rival <strong>in</strong> functional complexity, <strong>and</strong> be<strong>in</strong>g one does not imply<br />

be<strong>in</strong>g the other; once aga<strong>in</strong>, they are really two <strong>in</strong>dependent roles that any<br />

<strong>DICOM</strong> device can play. As a result, each <strong>DICOM</strong> unit can be SCU, SCP, both,<br />

or none with respect to any particular SOP Class. The <strong>DICOM</strong> Conformance<br />

Statement for the unit should provide exact specifications on this matter.<br />

This br<strong>in</strong>gs us to our f<strong>in</strong>al observation. The concept of SOPs, SCUs, <strong>and</strong><br />

SCPs is the most essential for any practical implementation of <strong>DICOM</strong>. Only<br />

SOP SCUs <strong>and</strong> SCPs def<strong>in</strong>e exactly how any <strong>DICOM</strong> entity should <strong>in</strong>teract,<br />

what it should process, <strong>and</strong> what <strong>in</strong>formation it should supply to other entities<br />

over the <strong>DICOM</strong> network. SOPs def<strong>in</strong>e the <strong>DICOM</strong> profile of any <strong>DICOM</strong>compatible<br />

device, from the largest CT scanner to the smallest <strong>DICOM</strong> file<br />

viewer. Consequently, any <strong>DICOM</strong> Conformance Statement issued by a device<br />

manufacturer for its <strong>DICOM</strong> device or application is noth<strong>in</strong>g but a list of supported<br />

SOPs <strong>and</strong> their SCU/SCP roles. Traditionally, read<strong>in</strong>g the conformance<br />

statements is the po<strong>in</strong>t where many PACS adm<strong>in</strong>istrators get really lost. In fact,<br />

most do not read them at all, <strong>and</strong> are overly trust<strong>in</strong>g of <strong>DICOM</strong> manufacturers<br />

that “it is gonna work okay for me, right?”.<br />

Fig. 51 <strong>DICOM</strong> application roles: digital archive act<strong>in</strong>g as C-Store SCP <strong>and</strong> SCU<br />

at the same time

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

Saved successfully!

Ooh no, something went wrong!