Lossy compression service and delete the originals uncompress studies
Gustavo Pérez
I work in a university public hospital
in Uruguay, and we used dcm4chee for several years ago. Today
modality are more, studies are bigger and video are sending to Pacs
too.
We would want change for a scheme with three levels of storage:
* Online, with a more access and recent studies (one year at first), without lossy compression.
* Nearline, with a less access or more ancient studies but with less than three years, without lossy compression.
* Lossy compression storage, for studies with more than three years in a cheap storage sata SAN.
Our problem are, that when we setting lossy compression service with one storage file group origin and the lossy group for destiny, this work ok, but when configuring deleting rules at origin file group for eliminate files that was copied for Lossy group this don't work. These studies keep in both file store group, at the origin group and Lossy group.
In source file group we had setting delete studies for archived files, but when compression service copied files to lossy file group, these studies didn't were selected for elimination.
Our configuration for compression service is:
SourceFileSystemGroupID java.lang.String RW ONLINE_STORAGE
DestinationFileSystemGroupID java.lang.String RW LOSSY_STORAGE
TaskInterval java.lang.String RW 12h
CompressionRules java.lang.String RW
ComputedRadiographyImageStorage:*:HC_PACS:1m:0.75:JPEG Lossy Compression with quality=0.75:5.0:64
DigitalXRayImageStorageForPresentation:*:HC_PACS:1m:0.75:JPEG Lossy Compression with quality=0.75:5.0:64
DigitalXRayImageStorageForProcessing:*:HC_PACS:1m:0.75:JPEG Lossy Compression with quality=0.75:5.0:64
DigitalMammographyXRayImageStorageForPresentation:*:HC_PACS:1m:0.75:JPEG Lossy Compression with quality=0.75:5.0:64
DigitalMammographyXRayImageStorageForProcessing:*:HC_PACS:1m:0.75:JPEG Lossy Compression with quality=0.75:5.0:64
CTImageStorage:*:HC_PACS:1m:0.75:JPEG Lossy Compression with quality=0.75:5.0:64
MRImageStorage:*:HC_PACS:1m:0.75:JPEG Lossy Compression with quality=0.75:5.0:64
UltrasoundImageStorage:*:HC_PACS:1m:0.75:JPEG Lossy Compression with quality=0.75:5.0:64
UltrasoundMultiframeImageStorage:*:HC_PACS:1m:0.75:JPEG Lossy Compression with quality=0.75:5.0:64
UltrasoundImageStorageRetired:*:HC_PACS:1m:0.75:JPEG Lossy Compression with quality=0.75:5.0:64
UltrasoundMultiframeImageStorageRetired:*:HC_PACS:1m:0.75:JPEG Lossy Compression with quality=0.75:5.0:64
SecondaryCaptureImageStorage:*:HC_PACS:1m:0.75:JPEG Lossy Compression with quality=0.75:5.0:64
XRayAngiographicImageStorage:*:HC_PACS:1m:0.75:JPEG Lossy Compression with quality=0.75:5.0:64
XRayRadiofluoroscopicImageStorage:*:HC_PACS:1m:0.75:JPEG Lossy Compression with quality=0.75:5.0:64
NuclearMedicineImageStorage:*:HC_PACS:1m:0.75:JPEG Lossy Compression with quality=0.75:5.0:64
SourceAETitle java.lang.String RW DCM4CHEE (default)
----
For source file group storage (for example ONLINE or NEARLINE),
CheckStorageFileSystemStatus boolean RW ------> true
CheckFreeDiskSpaceMinimalInterval java.lang.String RW ---> 10s
DeleteStudyOnlyIfCopyOnFileSystemOfFileSystemGroup java.lang.String RW --> LOSSY_STORAGE
DeleteStudyOnlyIfCopyArchived boolean RW-->true
ScheduleStudiesForDeletionInterval java.lang.String RW --> 7:10GB
All rest of deleted criteria were disabled, we have less than 10Gb in partition that we want enable deleted files.
My dcm4chee is dcm4chee-2.17.3-mysql, it's running over linux OS (ubuntu) and run with java 1.6.0_26-b03.
Thanks in advance
Gustavo Pérez