Workflow Services

The radiology workflow depends on the modality receiving the right patient and procedure context before the exam starts. Modality Worklist is the bridge between upstream scheduling and the device that actually acquires images.

View full size

Source: IHE Radiology Technical Framework Volume 1Last verified: 2026-03-11

The local swimlane is easier for first-pass learning, but this official IHE actor view is the interoperability contract teams actually end up testing against. It makes the order placer, scheduler, modality, archive, and viewer responsibilities concrete.

If worklist integration fails, the downstream consequences are rarely local to the modality. Patient mismatches, accession-number drift, and delayed reporting often start with poor order-context handling at acquisition time.

DICOM workflow services do more than move pixels. They also describe the procedure state and confirm archive responsibility. That distinction matters in downtime, retry, and data-loss investigations.

That separation is why downtime procedures and retry logic should track both dimensions. A procedure may be complete from the modality perspective while custody confirmation is still outstanding for a subset of instances.

Query/Retrieve is not one operation. C-FIND locates matching studies, series, or instances. C-MOVE tells the archive to send the matching objects to a destination AE. C-GET returns them over the same association that requested them. Those differences drive real network design choices.

That is why many modern viewers and cloud services favor DICOMweb for retrieval even when the acquisition side still depends on DIMSE. The standard services remain important, but the network consequences are very different.

In routed environments, C-MOVE also creates an operational dependency on destination AE registration and return-path reachability. C-GET avoids that second outbound association, but it shifts more state and transfer load onto the original session.