18
HL7 Dropbox
An ‘HL7_Dropbox’ folder is also available at the same level as the Dropbox folder. The HL7
Dropbox will process any HL7 messages stored as text files that are copied into this folder in the
same manner as if the HL7 message were received via the gateway’s HL7 Listener. Valid HL7
messages are uploaded to the gateway’s account and deleted, while files that do not contain valid
HL7 messages are simply deleted.
Disk Management
The Disk Management component runs on a timer and removes unneeded gateway data when
appropriate. The run interval is configurable as are the retention times for data in the Storage and
Download folders. The default retention times are 4 hours each. Note that data maintained in the
Storage folder prevents duplicates from being processed and uploaded by the gateway, a common
problem at some sites. See the configuration section for a sample “disk_management” configuration
in json format.
Upload
The Upload component is responsible for uploading DICOM files to the grid. It takes a queue item
containing the location of a file to be uploaded to the Grid. The upload component, when invoked,
will capture this file and stream it up to the cloud. GZip compression is supported for uploads.
Download
The Download component is responsible for ensuring that the DICOM files of a study that has been
requested to be pushed to a destination are all available locally. Normally this means it retrieves
DICOM images from the grid via a download. However, in the case of a ‘local push’, the download
component identifies the local images in the Storage folder to be pushed and enqueues their
information onto the harvester.move_client queue for pushing.
UploadTranscode
The UploadTranscode component converts images into a desired transfer syntax prior to uploading
the image to the grid. The UploadTranscode queue is always utilized before the Upload queue
but only acts upon the DICOM images when it has been properly configured in the gateway
configuration “transcode tsns” (see DownloadTranscode below for sample configuration value).
The maximum number of concurrent upload transcoding threads can be set with the gateway
configuration “transcode_max_threads” (the default is 2). Setting “transcode_max_threads” to 0 or
less will disable the transcoding components entirely and block the normal flow of data through the
gateway. See the configuration section for a sample upload transcode configuration in json format.
To enhance upload performance, the UploadTranscode component is bypassed when upload
transcoding has not been configured.
DownloadTranscode
The DownloadTranscode component converts images into a desired transfer syntax just
prior to pushing the image to a destination. It effectively replaces the “pushtool” service.
The DownloadTranscode queue and the component itself is only enabled when the gateway
configuration “transcode tsns” contains at least one valid “download” section as shown below. This
configuration is very flexible, enabling both upload and download transcoding to and from any
supported transfer syntaxes, with conditional filtering based on any DICOM tag or the file size or
source AE Title (in the case of upload transcoding) or any DICOM tag or destination AE title (in the
case of download transcoding). The maximum number of concurrent transcoding threads can be
set with the gateway configuration “transcode_max_threads” (the default is 2). Setting “transcode_
max_threads” to 0 or less will disable the transcoding components entirely and block the normal
flow of data through the gateway. Note that either the “upload” section or the “download” section
of “transcode_tsns” can be left out if either of those components are to be disabled. See the
