spectrIm-QMRS
Version 3.0.1 Alpha
DICOM workflow
spectrIm-QMRS can create DICOM Secondary Capture objects from the Clinical Viewer window or from selected local image files. The created objects are associated with the last loaded spectroscopy DICOM examination, so patient, study, and UID context remain tied to the examination being reviewed.
The clinical reason for sending spectroscopy results back as DICOM is introduced in the DICOM crash course for clinical spectroscopy.
Secondary Capture export is enabled only after a spectroscopy DICOM dataset has been loaded. This prevents orphan screenshots or local images from being sent without patient and study context. The loaded spectroscopy DICOM supplies the Study Instance UID, patient tags, and UID root used to derive new Series and SOP Instance UIDs for the Secondary Capture object.
The exported object uses the DICOM Secondary Capture SOP Class and Explicit VR Little Endian transfer syntax. The user can choose whether the object is sent to a configured DICOM node or saved to disk for later inspection.
After loading a spectroscopy DICOM examination and creating a result view, such as an NAA map in a tumour patient, press the 2 DCM screenshot toolbar button. spectrIm-QMRS captures the current Clinical Viewer window and prepares it as a DICOM Secondary Capture object using the last loaded spectroscopy DICOM context.
The application asks what should happen with the new DICOM file. Choose Send to DICOM node to transmit the Secondary Capture by DICOM networking, choose Save to disk to write it to the local file system, or cancel the action.
If Send to DICOM node is selected, the send dialog shows the configured DICOM nodes and a preview of the screenshot. Select a valid reachable node, for example a PACS entry with AE title, IP address, and port, optionally adjust the series description, and then send the DICOM object.
If Save to disk is selected, the standard file save dialog opens. The user chooses the target folder and file name, and spectrIm-QMRS writes the screenshot as a local DICOM Secondary Capture file for later inspection, archiving, or manual transfer.
The screenshot export remains disabled until a spectroscopy DICOM examination has been loaded, because patient, study, and UID context are required for a clinically meaningful DICOM object.
Local PNG, JPEG, BMP, or GIF files can be converted to Secondary Capture DICOM objects with the 2 DCM image toolbar button. The selected image files are still associated with the loaded spectroscopy DICOM examination; this action is not available without a loaded DICOM context.
Press 2 DCM image to open a multi-file image chooser. Select one image or several image files that should be DICOMized as Secondary Capture objects.
After selection, spectrIm-QMRS previews the image that will be DICOMized. The user can confirm the current image, skip it, cancel the remaining conversion, or use the checkbox to avoid being asked again for the remaining selected images.
For each confirmed image, the application asks whether the new Secondary Capture DICOM object should be sent to a DICOM node, saved to the local file system, or cancelled.
When sending is selected, choose a valid reachable DICOM node, such as a PACS entry, and then send the object. When saving is selected, the standard file save dialog opens so the generated DICOM file can be written to the local filesystem.
Mounted DICOM directories may already contain Secondary Capture series, for example screenshots or imported image captures created by spectrIm-QMRS. When such a series is double-clicked in the Patient/Study Browser, spectrIm-QMRS opens the captured image in a separate viewer frame instead of loading it into the spectroscopy processing workflow.
The separate frame shows the rendered image, series description, patient name, and source file path. Large captures are displayed in a scroll pane so the full image can be inspected.
Sending a Secondary Capture to PACS or another workstation requires a reachable remote DICOM node with correct AE title, host, and port settings. Hospital firewall and scanner/PACS registration rules still apply. The clinical background for these DICOM network requirements is summarized in the DICOM crash course.
Screenshots and imported images can contain patient identifiers or clinical annotations. Handle exported DICOM files according to local privacy and clinical-documentation policies.