CMOVE

CMOVE refers to the C-MOVE operation in the DICOM (Digital Imaging and Communications in Medicine) standard. It is a network command used to instruct a destination device to retrieve and transfer DICOM objects from a source device within a medical imaging workflow, such as within a PACS (Picture Archiving and Communication System).

How it works: An application acting as the C-MOVE service class user (SCU) issues a C-MOVE request to a C-MOVE service class provider (SCP). The request includes a query/retrieve dataset that identifies the data to be moved (for example, at the PATIENT, STUDY, or SERIES level) and a Move Destination, specified by its AET (Application Entity Title). The SCP responds with a status and subsequent sub-operations. To effect the move, the SCP initiates one or more C-STORE operations to the destination AET to transfer the actual DICOM objects. The result is that the specified imaging data are copied to the destination system while the source may retain copies depending on the workflow.

Context and use: C-MOVE is commonly used to migrate data between PACS servers, deliver studies to a clinician’s workstation, or reorganize data within a hospital’s imaging infrastructure. It operates over existing DICOM associations and is subject to network bandwidth, storage availability, and security requirements, such as TLS encryption and proper access controls.

Relation to other DICOM operations: C-MOVE is one of several query/retrieve mechanisms, alongside C-FIND and C-GET, with C-STORE handling the actual transfer of objects. CMOVE is widely supported but can involve complex coordination if multiple destinations or large datasets are involved.

See also: DICOM, PACS, C-FIND, C-GET, C-STORE.