The first sticky note is accompanied by an email explaining that an Ultrasound modality was recently installed and already tested in the Test environment. The next step is to configure it to the PACS Production environment and ensure it can retrieve the worklist and store images to PACS.

You'll need to know a few things. But we don't have much time. We have doctors waiting on us. Let's quickly refresh our memory on the basics.

DICOM Back to Basics

DICOM (Digital Imaging and Communications in Medicine) is a standard for storing, transmitting, and sharing medical images and associated data between healthcare systems. It ensures interoperability between imaging devices, PACS, and other medical software by defining formats, communication protocols, and networking guidelines. Devices that communicate with each other on a TCP/IP network using the DICOM protocol are called Application Entities.

Transfer Control Protocol / Internet Protocol Network

A TCP/IP network is a communication system that uses the TCP/IP protocol suite to transmit data between devices, ensuring reliable, organized, and error-checked data delivery across interconnected networks. Think of TCP/IP like a postal service for the internet. When you send a letter (data) to a friend (another computer), you use an address (IP address) to make sure it reaches the right place. TCP is like the postal worker that makes sure each part of the message arrives in order and undamaged. If any part of the message gets lost, TCP requests it again, ensuring it all arrives safely and correctly—just like double-checking that all pages of a letter are there before delivering it.

The Application Entity (AE)

An Application Entity (AE) in DICOM is a uniquely identifiable software component or device that initiates or receives DICOM communications for tasks such as image transfer or query/retrieve operations. The AE is identified by the AET (Application Entity Title), IP address, and Port number. The 3 values establish communication between two devices in a medical imaging network, such as PACS, modalities (like CT or MRI), and workstations. These components must match correctly for DICOM communication to work as expected. Here's why:

1. AET (Application Entity Title)
   The AET is a unique identifier for each device or software that participates in the DICOM network. It is used to identify the source and destination during DICOM operations (e.g., sending or retrieving images). Every DICOM device (e.g., CT scanner, PACS, or workstation) has an AET that acts as its "name" in the network. The AET is case sensitive and has a 16 character limit.
   
   
2. IP Address
   The IP address identifies the specific device or server on the network. Just like in any other network protocol, the IP address ensures that data is sent to the correct device. Can be referred to as Host when inputting configuration parameters on a modality or PACS settings.
   
   
3. Port Number
   The Port is the network port on which the DICOM service is listening for incoming connections. A DICOM device or service might listen on a specific port (e.g., 104 or 11112), and this must be set correctly for communication.

An Ultrasound (US) modality is a medical imaging device that uses high-frequency sound waves to produce real-time images of the body's internal structures for diagnostic purposes.

A DICOM modality worklist is a system that provides medical imaging devices with patient and procedure information directly from the original order. This alleviates any manual entry of metadata.

DICOM store is the process of transmitting medical images and related data from one DICOM-compliant device, such as a modality, to another, such as a PACS, using the C-Store DICOM operation.

Technologists use imaging modalities like X-rays or Ultrasounds to send DICOM images to PACS. Radiologists use PACS to view the images and create a final report based on their clinical findings.

Test vs Production Environment

A test environment is a controlled setting where new software updates, configurations, and workflows are tested without affecting real patient data or hospital operations. The production environment, on the other hand, is the live system used for actual patient care, where all changes and configurations must be stable and fully functional to ensure patient safety and compliance.

That should have explained all the technical terms in that first sticky note.

In summary, our task is to:

Configure the AET, IP and Port on both the PACS and US modality. This should allow technologists to use the modality to query PACS for a worklist of patients. Then send captured images to PACS