6
custom_queue_retry_coefficient
JSON array of key/value pairs where the key(s) are “queuename_retry_coefficient”. The decimal
value for each key sets a factor used to determine the delay in seconds before subsequent retry
attempts. The retry delay is determined by the number of attempts cubed times the retry coefficient
value; i.e.: [retry delay] = [retry count]**3 x [retry coefficient]. Defaults to 10 for all queues not
specifically set.
All possible queue names:
download•
downloadtranscode•
hl7client•
hl7upload•
move•
queryclient•
retrieveclient•
upload•
uploadtranscode•
Sample:
{
‘hl7upload_retry_coefficient’:’10’,
‘download_retry_coefficient’:’5’,
‘queryclient_retry_coefficient’:’20’
}
destination_push_rules
JSON hash of all custom settings for pushing studies to specific destinations. Used to give fine-
grained control over what images get pushed to a destination during subsequent pushes of the
same study. If the given AE, port and IP address match the study’s destination AE, port and IP
address, then these custom settings are applied to the push. Not set by default, which results in
the default values listed below being used to push the study to the destination’s AE, port and IP
address.
All possible settings for each defined destination (All are required. Any missing or invalid settings
for a destination will result in default settings for all values for that destination):
address: IP address of the destination•
port: Port of the destination•
aetitle: AE Title of the destination•
automated_study_push_cutoff_in_minutes: For automated (via routing rules) study pushes to this•
destination, this is the decimal cutoff time in minutes after the initial study push determining
whether the “automated_before_cutoff” or the “automated_after_cutoff” behavior should
be enforced for subsequent pushes of the same study. Default is 2 minutes.
user_requested_study_push_cutoff_in_minutes: For manual or user requested (via web) study•
pushes to this destination, this is the decimal cutoff time in minutes after the initial study
push determining whether the “user_requested_before_cutoff” or the “user_requested_after_
cutoff” behavior should be enforced for subsequent pushes of the same study. Default is 2
minutes.
automated_before_cutoff: Behavior to be enforced for automated (via routing rules) subsequent•
pushes of the same study to this destination BEFORE the cutoff time defined by “automated_
study_push_cutoff_in_minutes” has been reached. Default is “REPUSH_UPDATES_ONLY”.
automated_after_cutoff: Behavior to be enforced for automated (via routing rules) subsequent•
pushes of the same study to this destination AFTER the cutoff time defined by “automated_
study_push_cutoff_in_minutes” has been reached. Default is “REPUSH_UPDATES_ONLY”.
user_requested_before_cutoff: Behavior to be enforced for manual or user requested (via web)•
subsequent pushes of the same study to this destination BEFORE the cutoff time defined by
“user_requested_study_push_cutoff_in_minutes” has been reached. Default is “REPUSH_
