Hello,
I want to block the storing of some outclinic patients with a defined ID.
Is this possible? The images for all images transfer runs automatically, for this I plan the blocking of certain patients.
Hello,
I want to block the storing of some outclinic patients with a defined ID.
Is this possible? The images for all images transfer runs automatically, for this I plan the blocking of certain patients.
May be possible in subsequent release with ImportConverters.
Marcel
this is kind of a neat idea, I never thought of Conquest as a possibility to block certain studies.
This option could turn out very useful, if it works .-)
greetz
Lambert,
It is a good idea to do a nightly treshhold cleanup of the first MAGdevice and filter the import to the second storage (MAGDevice1) by ID or Date, etc.
The problem is: when the second storage is large (forexample 1 TB), It will take a long time to regenerate the database into Conquest because the Conquest was installed in the directory of MAGDevice0.
So, my question is:
How can you auto-delete studies or do a nightly cleanup of MAGDevice 0 by Date?
Thanks
Hi,
It can cleanup below a certain amount of free disk space, and in principle it can can do that on date (see LRUSort). This options is new in 14.13, however, it is broken for all but dbaseIII.
Marcel
Marcel,
This is how I set up the MAGs:
# Configuration of disk(s) to store images
MAGDeviceThreshhold = 600
MAGDevices = 3
MAGDevice0 = F:\dicomserver1413\Data\
MAGDevice1 = c:\temp\
MAGDevice2 = c:\RECYCLER
NightlyCleanThreshhold = 0
NightlyMoveTarget = 0
ImportConverters = 1
ImportConverter0 = ifequal "%v0008,0020[0,3]", "2005"; storage MAG2
ExportConverters = 1
ExportConverter0 = forward to Kpserver
The problem is: Removed files by date from MAG0 and MAG2.
Any solution to this problem?
I guess a good feature would be to setup auto cleanup for each MAG separately. I will think about that.
Marcel
Don’t have an account yet? Register yourself now and be a part of our community!