Reject Expired Studies

Overview

• Configure a Study Retention Policy for rule based application of a retention period for study/series.
• Expired studies/series may be rejected or moved/exported automatically using a scheduler as explained below. If Move Expired Studies before Rejection is configured then objects will not be directly rejected first but will be rather moved/exported to a destination or storage system and only once the export has been successful, will they be rejected.
• Once these expired studies/series are rejected, optionally one can also delete automatically such rejected instances and rejection notes

Configuration

Using Archive UI

• Go to Menu->Configuration, then on Devices page, Edit the dcm4chee-arc device. Edit Extension of Device Extension, then Edit Extension of Archive Device.
• Configure values for mandatory fields Reject Expired Studies Polling Interval, Reject Expired Studies AE Title (ensure that you have an Application Entity with Archive AE Extension created with this value, for Rejection of expired study/Series to work) and optional fields Reject Expired Studies Fetch Size, Reject Expired Series Fetch Size and Expire Series Individually as needed. You may or may not change value of field Allow Rejection For Data Retention Policy Expired and Save.

Note :

• Upto version 5.16.0 Reject Expired Studies Polling Start Time shall be configured.
• Version 5.16.0 onwards the use of Reject Expired Studies Polling Start Time is discontinued and instead one or more Reject Expired Studies Schedule shall be configured.

Using LDAP

One may either

• create a LDIF file (e.g.):

    version: 1
    dn: dicomDeviceName=dcm4chee-arc,cn=Devices,cn=DICOM Configuration,dc=dcm4che,dc=org
    changetype: modify
    add: dcmRejectExpiredStudiesPollingInterval
    dcmRejectExpiredStudiesPollingInterval: P1D
    -
    
    dn: dicomDeviceName=dcm4chee-arc,cn=Devices,cn=DICOM Configuration,dc=dcm4che,dc=org
    changetype: modify
    add: dcmAllowRejectionForDataRetentionPolicyExpired
    dcmAllowRejectionForDataRetentionPolicyExpired: EXPIRED_UNSET
    -
    
    dn: dicomDeviceName=dcm4chee-arc,cn=Devices,cn=DICOM Configuration,dc=dcm4che,dc=org
    changetype: modify
    add: dcmRejectExpiredStudiesFetchSize
    dcmRejectExpiredStudiesFetchSize: 10
    -
    
    dn: dicomDeviceName=dcm4chee-arc,cn=Devices,cn=DICOM Configuration,dc=dcm4che,dc=org
    changetype: modify
    add: dcmRejectExpiredSeriesFetchSize
    dcmRejectExpiredSeriesFetchSize: 10
    -
  

Upto Version 5.16.0

    dn: dicomDeviceName=dcm4chee-arc,cn=Devices,cn=DICOM Configuration,dc=dcm4che,dc=org
    changetype: modify
    add: dcmRejectExpiredStudiesPollingStartTime
    dcmRejectExpiredStudiesPollingStartTime: 22:00:00

Version 5.16.0 onwards

    dn: dicomDeviceName=dcm4chee-arc,cn=Devices,cn=DICOM Configuration,dc=dcm4che,dc=org
    changetype: modify
    add: dcmRejectExpiredStudiesSchedule
    dcmRejectExpiredStudiesSchedule: hour=[22-23] 				

and import it to the LDAP Server by using the ldapmodify command line utility.

• or use the Add Attribute... and Add Value... function of Apache Directory Studio to add attributes on Device level (e.g.: dicomDeviceName=dcm4chee-arc) in the Archive Configuration.

One may refer to Archive Device
to understand the description of attributes.

Refer ISO-8601 Duration format for more know-how on Durations.

Go to the Control tab on Configuration page in archive UI and reload the configuration.