Working with DICOM Images

[MIPAV_titleVolume1.html ]

[MIPAV_ImageBasics.html ]

[MIPAV_ConnectingToSRBBIRN.html ]

[MIPAV_Glossary.html ]

---

3

Working with DICOM Images

In this chapter . . .

[MIPAV_DicomImages.html#1146910 "Understanding how MIPAV works with DICOM images" on page 86]

[MIPAV_DicomImages.html#1424960 "Browsing DICOM images" on page 88]

[MIPAV_DicomImages.html#1425270 "Sending and retrieving DICOM images" on page 94]

[MIPAV_DicomImages.html#1163161 "Testing the connection" on page 105]

[MIPAV_DicomImages.html#1000958 "Posing queries and retrieving images" on page 106]

[MIPAV_DicomImages.html#1162301 "Receiving and sending image files" on page 110]

[MIPAV_DicomImages.html#1002780 "Displaying and editing DICOM tag information" on page 113]

[MIPAV_DicomImages.html#1003305 "Protecting patient privacy using Anonymize" on page 118]

[MIPAV_DicomImages.html#1174707 "Converting non-DICOM image files to DICOM format" on page 125]

Digital Image Communication in Medicine (DICOM) defines a standard method of transmitting digital medical-image information between devices, such as computers, servers, or imaging equipment. The standard not only prescribes how to communicate with other imaging equipment and databases, but also how to store images.

This chapter discusses how MIPAV works with DICOM images. It also explains how to browse DICOM images and send and retrieve DICOM images, which includes the following tasks:

Setting up a hosts table to indicate where you want to send images ([MIPAV_DicomImages.html#1147719 "internet protocol (IP) address: A numeric ID that is used to identify your computer on a Transmission Control Protocol/Internet Protocol (TCP/IP) network. An example of a TCP/IP network is the Internet." on page 96])

Testing server connections ([MIPAV_DicomImages.html#1163161 "Testing the connection" on page 105])

Posing queries and retrieving DICOM images ([MIPAV_DicomImages.html#1000958 "Posing queries and retrieving images" on page 106] and [MIPAV_DicomImages.html#1162301 "Receiving and sending image files" on page 110])

Sending DICOM images to another device ([MIPAV_DicomImages.html#1431451 "To send image files" on page 111])

It also explains how to edit DICOM tags, protect patient privacy by removing DICOM tag information from images, and convert image formats, such as Analyze or TIFF, to DICOM format.

Understanding how MIPAV works with DICOM images

You can use MIPAV to access images and information that were generated by DICOM-compatible imaging equipment. Some researchers at NIH use MIPAV to access DICOM-compatible archive systems, such as the Kodak Cemax-Icon Picture Archiving and Communication System (PACS), which includes the AutoRad devices located in the NIH clinical center. The PACS system consists of software, hardware, and networks. PACS provides the means for medical specialists to digitally acquire images, transmit the images and image-related data using a communications network, display and interpret images, and store and retrieve images. PACS also provides an interface to other systems that contain patient data.

Note: The DICOM standard is detailed in the 16-part documentation set Digital Imaging and Communications in Medicine (DICOM) Standard (refer to Appendix B, DICOM Conformance Statement.) MIPAV is DICOM version 3.0 compliant. Compliance information appears in Appendix B of this document.

[MIPAV_DicomImages.html#1424954 Figure 56] shows the communication pathways between MIPAV, the Internet, a DICOM-compatible server, a patient database, an imaging device, and a remote MIPAV workstation.

Digital images are acquired on a medical imaging device, such as a Computed Tomography (CT) scanner. The image can remain on the device or be transferred via a DICOM-compatible server to a patient database or other archive media. Once the image is acquired and stored, you can then use MIPAV to query and retrieve, receive, or send DICOM image files.

Figure 56. Communication pathways between MIPAV and DICOM

{| align="center"

|}