Aging studies by modality and general age

diegog · Post by **diegog** » Sat Feb 15, 2014 8:23 pm

Hi,
Aging by modality apear do not work in my installation of Pacsone Premium even if general age (on Configuration page) works fine.
What is the relation of the two rutines?

Once you select general aging then the modality specific aging does not work?

Also I noted the general aging does not "erase" the study that are moved to LTS making very difficult the server administration (must verify each folder that is moved to the NAS and then erase on STS manually). Is this normal? Or must erase the files after sucessfully moved?

Pacsone service is runing with full administrator grants on a 64bits Windows 2012 foundation server.

Thanks!

Post by **pacsone** » Mon Feb 17, 2014 6:42 pm

Are you referring to the Automatic Aging feature, or the Automatic Purging of Storage Directory feature since these 2 are completely different?

1. The Automatic Aging feature involves the moving of raw Dicom image files from the Short-term Archive Directory (STS) to the Long-term Storage Directory (STS). If enabled from the "Configuration" page, PacsOne Server will move the raw Dicom image files from the STS to LTS, and update the database records to link to their new locations under the LTS. No database records will be deleted.

2. The Automatic Purging of Storage Directory feature is configured from the "Tools->Automatic Purge Storage Directory" menu, where PacsOne Server will find the Dicom studies matching with the defined purging criteria, e.g., Modality, Study Date, etc, then delete BOTH the database records AND the raw Dicom image files for all images contained within each matching study. This feature has nothing to do with the STS or LTS in the Automatic Aging feature above.

diegog · Post by **diegog** » Mon Feb 17, 2014 9:31 pm

Thanks for your replay. I didn't saw this functionality in my previous installations.

We setup a clinical PACS. We are storing new studies on server HD and moving them to a NAS after a week.

We need to preserve studies and records for ever in NAS devices and in pacsone database. We espect pacsone purge the DICOM studies remaining on the server HD after move them to the NAS. But this does not happens. If I setup " Purge Study Received More Than 30 days" + Delete patient record after all studies of the patient have been purged: NO --> this will erase images but no DB records?

Thanks,

Post by **pacsone** » Tue Feb 18, 2014 3:37 am

If you've checked the Delete Image Files radio button, then PacsOne Server will not only delete the database records associated with the matching studies, but also the raw Dicom image files for all instances contained within each matching study.

If you've checked the Move Image Files to Destination Folder: radio button and specified a Destination Folder for PacsOne to move the raw Dicom image files into, then PacsOne will NOT delete any database records associated with the matching studies. Instead, PacsOne will move the raw Dicom image files into the specified Destination Folder and update the database records to link to their new location paths under the Move Destination Folder.

diegog · Post by **diegog** » Tue Feb 18, 2014 6:53 am

OK, Thanks. Now I understand.
We don't need "age studies". Just Purge studies will do the job. Will move the old studies to the NAS and update the database everyday.
This will preserve the original folder name (date)? or will create a new folder with the date that is moved?
Thanks

Post by **pacsone** » Tue Feb 18, 2014 6:01 pm

It will create a new folder with the date when the move actually takes place.

diegog · Post by **diegog** » Mon Mar 03, 2014 10:40 am

Hi
After I set up "purge" I notice Pacsone is storing studies on the STS with format of the day/month/year as usual but also is storing studies on the NAS inside the LTS folder (defined in the "purge" menu) but grouped under AET name. For example all CT is on CT99 (AET of the CT), XRAYs under AET of XRay. In those folders even same day studies appear so is "dupicating" instead of purging at defined intervals.
Maybe something is bad configured?
Maybe there are some interaccions between differnt set-ups of the server?
Thanks,
Diego

Post by **pacsone** » Mon Mar 03, 2014 4:03 pm

The STS/LTS settings are only applicable for the automatic aging feature, which has nothing to do with the auto-purge feature you referred to.

So can you elaborate on the details of the problem, e.g., what have you configured (auto-purge or auto-age), what are your expectations, etc, what's the actual behavior, etc?

diegog · Post by **diegog** » Mon Mar 03, 2014 5:30 pm

Sorry for the missunderstood.
In my installation we have a local server hardisk that I call you STS and a NAS system that for me is the LTS.
No aging is setup (after you explain me that what we need is purge and not age).
Purge is configure to "Purge Study Received More Than 15 Days Ago" and Move Image Files to Destination Folder in the NAS. Delete patient record after all studies of the patient have been purged: NO.
What I suppose will happens is that every day at 12 AM the pacs will "move" files to a NAS directory and "erase them" on the server directory wich is default store directory for pacsone.
Instead what I'm getting is:
1-on the server default folder studies with more than 15 days disapear as I exspected
2- on the NAS directory I setup on the autoPurge page one folder per each modality connected to the pacs with the name of the AE and inside each study in a folder named with study instance UID. I see studies that were received even today.
Is this normal?

Post by **pacsone** » Tue Mar 04, 2014 3:38 pm

diegog wrote: 2- on the NAS directory I setup on the autoPurge page one folder per each modality connected to the pacs with the name of the AE and inside each study in a folder named with study instance UID. I see studies that were received even today.

The new studies received today should NOT be stored under the LTS/NAS unless you've explicitly configured the LTS/NAS as the Short-term Archive Directory for that Source AE. So can you pick any newly received study that was stored under the LTS/NAS like you said, find the Source AE from which PacsOne received that study, then check the Dicom AE page to see what's the Short-term Archive Directory currently configured for that Source AE.

Also, you should click through the Image Thumbnails page for that study, then click the URL link underneath any of the thumbnail images displayed which will display the full path to the raw Dicom image file for that particular image. You can then verify if it's indeed stored under the LTS/NAS as you suspected.

diegog · Post by **diegog** » Thu Mar 06, 2014 8:20 am

Using the jpeg images as you told me I see studies are stored on the system configuration local disk.

On DICOMAE page for all 6 modalities no Long-Term Archive Directory or Short-Term Archive Directory is setup. So I don't know why still the server save todays-received-studies on the Purge/Move directory.

Any idea?

Thanks

Diego

Post by **pacsone** » Thu Mar 06, 2014 4:28 pm

So this has nothing to do with the Automatic Aging feature, as you just ran the Automatic Purging of Storage Directory tool with the "Move to Destination Folder" enabled as the LTS folder. Is that correct?

If so, it does not appear the auto-purge had moved the raw Dicom image files, because you said the full path displayed after you clicked on the URL link underneath the thumbnails still shows the STS folder?

If that's the case, you should check the following:

1. Make sure the user/group account PacsOne Server service is currently running as has sufficient security permissions to modify/delete files under the STS folder, because PacsOne will try to delete the existing image files under STS after having copied them into the auto-purge destination folder (LTS) successfully, but if PacsOne could not delete the existing image files under STS, then it will NOT update the database records to link to the new paths under the LTS folder.

2. Can you double-check and verify that study whose raw Dicom images stored under STS according to the URL link underneath the thumbnails page has indeed been copied into the destination/LTS folder by the auto-purge?

diegog · Post by **diegog** » Sun Mar 09, 2014 4:07 pm

Hi,
Pacsone is runing service with logon as administrator.

Found an autopurge error:
Sun Mar 09 00:03:41 2014 INFO - AUTOPURGE: Moving Study [1.2.392.200036.9125.2.1841721115719316.64738003312.27761299] received on [2014-02-12 10:43:00]...
Sun Mar 09 00:03:41 2014 INFO - AUTOPURGE: Moving Study [1.2.392.200036.9125.2.1841721115719316.64738004421.27761304] received on [2014-02-12 11:01:25]...
Sun Mar 09 00:03:41 2014 INFO - AUTOPURGE: Moving Study [1.2.392.200036.9125.2.1841721115719316.64738006175.27761308] received on [2014-02-12 11:30:52]...
Sun Mar 09 00:03:41 2014 INFO - AUTOPURGE: Moving Study [1.2.840.113619.2.55.3.1716700133.578.1391526747.596] received on [2014-02-12 11:36:12]...
Sun Mar 09 00:03:41 2014 ERROR - AUTOPURGE: Cannot access file [C:/DICOM_STUDIES/2014-02-12-WED/1.2.840.113619.2.55.3.1716700133.578.1391526747.603.1] for instance 1.2.840.113619.2.55.3.1716700133.578.1391526747.603.1
Sun Mar 09 00:03:41 2014 ERROR - AUTOPURGE: Cannot access file [C:/DICOM_STUDIES/2014-02-12-WED/1.2.840.113619.2.55.3.1716700133.578.1391526747.603.2] for instance 1.2.840.113619.2.55.3.1716700133.578.1391526747.603.2
Sun Mar 09 00:03:41 2014 ERROR - AUTOPURGE: Cannot access file [C:/DICOM_STUDIES/2014-02-12-WED/1.2.840.113619.2.55.3.1716700133.578.1391526747.603.3] for instance 1.2.840.113619.2.55.3.1716700133.578.1391526747.603.3[/img]

Post by **pacsone** » Sun Mar 09, 2014 5:56 pm

diegog wrote: Sun Mar 09 00:03:41 2014 ERROR - AUTOPURGE: Cannot access file [C:/DICOM_STUDIES/2014-02-12-WED/1.2.840.113619.2.55.3.1716700133.578.1391526747.603.1] for instance 1.2.840.113619.2.55.3.1716700133.578.1391526747.603.1
Sun Mar 09 00:03:41 2014 ERROR - AUTOPURGE: Cannot access file [C:/DICOM_STUDIES/2014-02-12-WED/1.2.840.113619.2.55.3.1716700133.578.1391526747.603.2] for instance 1.2.840.113619.2.55.3.1716700133.578.1391526747.603.2
Sun Mar 09 00:03:41 2014 ERROR - AUTOPURGE: Cannot access file [C:/DICOM_STUDIES/2014-02-12-WED/1.2.840.113619.2.55.3.1716700133.578.1391526747.603.3] for instance 1.2.840.113619.2.55.3.1716700133.578.1391526747.603.3

Can you check and verify if those files actually exist on this server?

C:/DICOM_STUDIES/2014-02-12-WED/1.2.840.113619.2.55.3.1716700133.578.1391526747.603.1
C:/DICOM_STUDIES/2014-02-12-WED/1.2.840.113619.2.55.3.1716700133.578.1391526747.603.2
C:/DICOM_STUDIES/2014-02-12-WED/1.2.840.113619.2.55.3.1716700133.578.1391526747.603.3

diegog · Post by **diegog** » Mon Mar 10, 2014 1:53 pm

I checked and the file 1.2.840.113619.2.55.3.1716700133.578.1391526747.603.2 does not exist in any place, not in STS, nore in LTS. The folder 2014-02-12-WED also was erased from the STS.