Core DICOM Services: The Foundation of Medical Imaging

Understanding core DICOM services is essential for building medical imaging applications. These services form the backbone of all DICOM communication.

DICOM Storage (C-STORE): Sending Images

What it does: C-STORE is the fundamental operation for transmitting medical images from one system to another. Think of it as “DICOM email” for images.

Real-World Usage

C-STORE is used in numerous clinical scenarios:

C-STORE Use Cases
=================

Modality → PACS
  CT scanners, MRI machines, ultrasound devices
  send images to PACS immediately after acquisition

PACS → Workstation
  Radiologists' diagnostic workstations retrieve
  images from PACS for interpretation

Hospital → Hospital
  When patients transfer between facilities,
  their imaging studies follow via C-STORE

EMR Integration
  Referring physicians' EMR systems receive
  relevant images for patient care

Example Scenario

When a patient undergoes a chest CT scan:

1. Patient is scanned on CT scanner
2. Scanner acquires 300+ images
3. Scanner uses C-STORE to send all images to PACS
4. Transfer completes within seconds of scan completion
5. Images appear in PACS for radiologist review

DICOM Query/Retrieve: Finding and Fetching Images

DICOM provides two complementary approaches for locating and retrieving images.

C-FIND: The Search Engine

What it does: C-FIND queries DICOM servers to search for studies, series, or images based on criteria like patient name, date, modality, or accession number.

Real-World C-FIND Usage

Example: An orthopedic surgeon searches for “John Doe MR Knee” to review pre-operative imaging before surgery.

C-MOVE vs. C-GET: Two Ways to Retrieve

These services retrieve images but work differently:

C-MOVE (Traditional Approach)

What it does: Instructs the PACS to send images to a third location (not necessarily back to you).

Key characteristic: Requires the destination to have a receiving service (Storage SCP) running.

Best for:

• Working with legacy systems (more widely supported historically)
• Routing images to different destinations dynamically
• Operating in complex multi-system environments

Example: A radiologist requests PACS to send images to their reading workstation.

C-GET (Modern Alternative)

What it does: Directly retrieves images back to the requesting application.

Key characteristic: Simpler - no need to run a separate receiving service.

Best for:

• Building modern applications with simpler architecture
• Retrieving images directly to the requesting system
• Working behind firewalls where opening ports is challenging

Example: A tablet-based viewer retrieving images for mobile viewing.

When to Use Which

C-ECHO: The Heartbeat

What it does: C-ECHO verifies that a DICOM connection is working - it’s the equivalent of a network “ping”.

Real-World Usage

C-ECHO Use Cases
================

System Monitoring
  IT staff verify DICOM connectivity between systems

Troubleshooting
  When images aren't arriving, C-ECHO determines
  if it's a network or configuration issue

Installation
  During new equipment setup, technicians use
  C-ECHO to validate connectivity before
  sending real patient data

Automated Health Checks
  PACS monitors modality connectivity and
  alerts when devices go offline

Example Scenario

After installing a new MRI scanner:

1. Biomedical engineers configure AE Title, IP, and port
2. Run C-ECHO to test connection to PACS
3. C-ECHO succeeds: Connection verified
4. Send test images before clinical use
5. Scanner is cleared for patient imaging

Service Summary

Understanding these core services provides the foundation for all DICOM development. In the following sections, we’ll explore implementation details and code examples for each service.