DCV Data Manager / DM Forwarding Server / DM TLS Server

Published 2022-10-04

Subject to changes and corrections.

Version 3.3 (Build 24) (Released 2020-05-11)

Beta Release 2018-09-25

• Option added to resubmit “general failures”. (F3839)
• New INI validation. (F3832)
• Add new audit trail code for purged images. (F3728)
• Add MiPACS image tooth number support for importing DICOM. (F3700)
• Allows querying of multiple modalities. (F3675)
• Support for new Apteryx registration and Token based registration. (F3625)

Version 3.3 (Build 23) (Released 2018-01-03)

Beta Release 2017-10-04

• Added ability to resubmit failed DICOM stores to a different DICOM server. (F3556)
• Added option to disable generation of stamp files under database path menu. (F3405)
• Option added under wildcard searching to query both ID and Other ID fields. (F3281) 4
• Will automatically resubmit “missing UID” failures. (F3145)
• Optimized speed of “Select Images for Purging” display. (F3139)

Version 3.3 (Build 22) (Released 2017-01-06)

Beta Release 2016-05-17

• Corrected issue where a daily stop time prior to start time on a forwarding schedule would conflict. (B1260)
• Ability to now manually enter start/stop times in a forwarding schedule. Will now accept 24hr format, 12hr formats with AM and PM, and “noon”, “midnight”. (F3120)
• Added ability to specify multiple accepted or exclusion for image routing in DICOM server definition. Multiple values can be separated by ‘;’. Exclusions can be specified by having a ‘!’ specified as the first character of a value. (F3036)
• New text added to EULA. (F3015)

Version 3.3 (Build 20) (Released 2016-01-14)

Beta Release 2015-05-14

• Added separate log files for “changed” and “skipped” images during mass data correction. (F2742)
• Improved handling of invalid dates when importing a mass data correction file. (F2605)

Version 3.3 (Build 19) (Released TBD)

Beta Release 2014-12-30

• Added ability to strip any trailing tab characters from input lines in the mass data correction. (F2604)

Version 3.3 (Build 18) (Released TBD)

Beta Release 2014-07-17

• Confirmed DICOM tags are being carried over correctly when dental modalities are mapped to CR for forward to some PACS. (F2442)

Version 3.3 (Build 17) (Released TBD)

Beta Release 2014-04-24

• Updated functionality for Advanced Data Merge to match and merge patients with missing DOB and/or Gender. (F2347)
• Updated database creation to add breed information for patients. (F2357)
• Corrected issue that caused erroneous ‘Image is no longer in the database’ error if images were written to the ToStore while others were forwarding. (B1036)

Version 3.3 (Build 16) (Released TBD)

Beta Release 2014-03-14

• Corrected issue where receiving sockets could be opened on DCV Forwarding Manager. (F2238)
• Updated drawing and fonts. (F2263)

Version 3.3 (Build 15) (Released TBD)

Beta Release 2013-12-12

• Corrected issue with hash table lookup of patient ID’s, if patient ID was updated it was not immediatly searchable until application was closed and reopened. (F2060)
• Corrected issue where original attributes tag may have contained modified data rather than original. (F2061)
• New date and string handling to the Mass Data Correction. (B1008)

Version 3.3 (Build 14) (Released TBD)

Beta Release 2013-10-03

• When importing files status now updates every 100 files. (B978)
• Added ability to handle images that filename differs than the UID. (F1948)

Version 3.3 (Build 12) (Released TBD)

Beta Release 2013-04-18

• Add version check for leadtools dll’s. (F1255)
• Does not add images to ToStore that do not meet image routing requirements. (F1723)
• Corrected issue for deleted images not being removed from ToStore. (F1724)
• Corrected possible issue by disabling exclusive db locking when caching is enabled. (F1741)
• Added ability to perform periodic storage commitment checks. (F540)
• Optimized update database function. (F1851)
• DICOM revisions are now added to Original Attributes Sequence, 0400:0561. (F1824)
• Changed directory selection dialog. (F1735)
• Added tool to seperate different patients with same Study UIDs caused by computers with same disk ID. (F1784)
• Added optimazations for DICOM Forward of large volumes. (F1819)
• Improvements in image import speeds. (F1856)

Version 3.3 (Build 11) (Released TBD)

Beta Release 2013-01-10

• Ignores stamp files when performing database update and/or image imports. (F1442)
• New option to allow users to set type of compression applied to images. (F1234)
• Corrected issue where internal record count was not updating on first time run with a new database. (B795)
• Corrected issue where blocked images, specified in image routing, were being continuosly resubmitted. (B802)
• Added critical locking to prevent potential problems with logs during overnight switch overs. (F1488)
• Added auto resubmit feature for failed forwards. (F1427)
• Added a Patient ID Mapping utility. (F1623)
• Optimized forwarding by changing so DM loads local list into memory prior to sending. (F1594)
• Corrected possible memory leaks in DM. (F1599)
• Added option to remove DOB requirement when running Patient ID Mapping Utility. (F1668)
• DICOM transfer will now do all files rather then one at a time. (F618)
• Optimized ToStore and FailedStore handling. (F1601)
• Added CGET support for DICOM communications. Requires Calling Client to also support CGET. (F1580)
• Added additional fields to the Email Message Options for more detailed error reporting.(F1115)
• Updated display of SQL status windows.(F1474)
• Removed RLE DICOM transfer support. Replaced with JPEG Lossless. (F1493)
• Corrected issue when receiving an HL7 patient update message, all DICOM files were updated instead of just the correct patient. (B794)
• Added option for promiscuous image reception from multiple server AE title (F1467)
• Added ability to store Multiframe CT Studies, store as Singleframe. (F1428)
• Added Scheduled Station AE title as an available query option for worklist query field. (F1596)
• Added blocked tag functionality to WORKLIST transfers. (F1585)

Version 3.3 (Build 10) (Released 2012-03-15)

• Changed and optimized DICOM queries to file list queries. (F1307, F1309)
• Added utility to create image stamp files for entire database. (F1278)
• Added ability to send stamps back to server when created via DICOM query (F1276)
• The anonymous database file now encrypts the patient demographic information. (F1153)
• DCV Forwarding Data Manager, a forwarding only hybrid of DCV Data Manager, created. (F1399)
• DCV TLS Data Manager with TLS encryption support created. (F1215)

Version 3.3 (Build 9) (Released 2011-11-28)

• Added start/stop times to schedule for image forwarding (F930)
• Added digital signature so if launched across network will no longer recieve “publisher not verified” (F1141)
• Audit Trail now writes for actions performed within the Data Manager. (F1113)
• New utility added for the mass assignment of “Branch of Service” tag to preexisting data in the database. (F977)
• Added new schedule increments of 2,3,4,5 and 6 days for the image purging utility as well as 1 day and 1 week image age increments. (F1146)
• Fixed ‘invert gray-scale’ issue where inversions were tracked but not being saved in the image. (B624)
• Mass Data Correction Import / Export feature added. (F1108)
• Optimized memory usage for large databases. (F1071)
• Added Advanced Database Merge feature. (F1063)
• Improved handling of DICTEMP files in threaded functions. (F1125)
• Added list of sockets open by software to the interface. (F1148)
• Added ability for TLS encryption. (F1187, F1214)
• HL7 server support added. (F1070)

Version 3.3 (Build 6) (Released 2011-07-27)

• Added utility that will strip punctuation from patient ID’s. (F1056)
• Added ability to eliminate the forwarding of ghosted and retaken images. (F998)
• Optimized performance for large tostore database forwarding. (F933)

Version 3.3 (Build 5) (Released 2011-03-31)

• Uppercase conversion (and invalid character removal “?*!#$%&+=|"<>?/“) added to image import, patient import, and worklist import. (F893)
• Data correction now changed to take into consideration case changes and patient name correction. (F893)
• Added Auto Correct Patient Names options that handles upper case conversion and invalid character removal. (F893)
• Modified audit trail to write data immediatly to file rather than in chunks. (B579)
• Anonymize feature added that wipes out patient demographic information set or imported to the server. (F743)

Version 3.3 (Build 3) (Released 2010-12-20)

• Resolved Issue with Dicom Element 0008:0005 containing blank character set. Now defaults to ISO_IR 100, or is not present. (Bug 488)

Version 3.3 (Build 2) (Released 2010-11-03)

• Resolved issue with zero dates being assigned to imported worklist entries. (Bug 459)

Version 3.2 (Build 7) (Released 2010-08-17)

• Components and environment updated for compliance with new versions of the software.
• Made correction to handling where forwarded images can have their VR changed to UR for the image modifications tag.
• Removed patient DOB restriction on edit image information dialog.
• Splitting of multiple modality series added.
• Added audit trail capabilities.
• Made several process/features into threaded functions (i.e. threads that do not block the main application interface).

Version 3.1 (Build 10) (Released 2010-03-12)

• Added ability of the server to return uncompressed images in response to a C-MOVE request even if the images are compressed in the database.

Version 3.1 (Build 9) (Released 2010-02-04)

• Added new logging when generating the purge file list.
• Reformatted the image purging options.
• Complete rewrite of the image purging functionality to make it easier to use and understand.
• New purge ages added.
• New defaults set for the various image purging options.

Version 3.1 (Build 4) (Released 2009-12-22)

• Made a correction for queried results where a patient may not have a DOB specified. In the specific case of a patient that does not have a DOB specified AND a similar patient was returned in a query by DCV, the patient list displayed in DCV may list a DOB for the patient that did not originally have a DOB specified. Once the user opened the patient and/or images, the DOB is not displayed because the patient did not have a DOB (it was simply a list display artifact).

Version 3.1 (Build 1) (Released 2009-08-21)

• Added new fields to the patient database. NOTE, this version will perform an update to the database!
• Added new fields to the image database. NOTE, this version will perform an update to the database!
• Added species and breed capabilities to data correction screen.
• Added new button in the data correction screen to allow changes to the patient demographic information to be taken from an entry in the patient database.

Version 3.0 (Build 90) (Released 2009-08-12)

• Added new features to PING for data servers when creating server definitions.
• Added new Auto-Discovery options. This enables DCV clients to automatically use Data Managers that appears on a network without having to manually create server definitions for the servers. This is primarily used for mobile environments and laptop computers which enable the user to coordinate with Data Managers on networks that may come and go. Security features exist to prevent just any DCV client from using any Data Manager.

Version 3.0 (Build 88) (Released 2009-07-21)

• Fixed the auto image purging.

Version 3.0 (Build 87) (Released 2009-07-13)

• Updated invalid date entry when modifying images.

Version 3.0 (Build 86) (Released 2009-07-09)

• Dramatically faster queries when specifying non-wild carded patient IDs.

Version 3.0 (Build 85) (Released 2009-03-14)

• Reformatted the Email options screen.
• SIGNIFICANTLY increased the speed of email generation from the application.
• Correction and enhancements made to the emailing of forwarding errors to the email list.
• If the user modifies the forwarding schedule for the current day (and that time has passed), the server no longer automatically starts a new forwarding session. This does not change the processing of images for a past time on the same day when restarting the Data Manager.

Version 3.0 (Build 84) (Released 2009-03-06)

• New Escape key tracking.
• If the database path is invalid at startup, the application now prompts the user to modify/correct the path. Previously the application displayed an error message and quit the application.
• Image imports now can handle importing of any DICOM images and DICOMDIRs. Previously, the import function only imported files that had the .DIC and .DCM file extensions.
• Data correction was updated in a prior release to work on multiple images at the same time.

Version 3.0 (Build 83) (Released 2008-12-02)

• 1. Data range query for both images and worklists have been added.
  2. Corrected worklist date queries. Previously it ignored any date associated with a query.

Version 3.0 (Build 81) (Released 2008-11-20)

• Made correction where the application would try and forward images to a Worklist only server. Now the software ignores Worklist only servers when trying to forward images.
• Corrected “12:30 am / 13:30” item to read “12:30 pm / 13:30”.
• SSN matching can now handle matching formatted and unformatted SSN numbers. Previously 111-22-3333 and 111223333 would not match as identical patient ID numbers.
• Popup menu controls are now automatically adjusted to be the correct size the first time they are displayed.

Version 3.0 (Build 79) (Released 2008-08-15)

• Ability to set new study and series UIDs when editing images.

Version 3.0 (Build 78) (Released 2008-08-12)

• Implemented new ghosting and retaken image types. New infrastructure, image editing, image data display and image drops implemented.

Version 3.0 (Build 77) (Released 2008-07-30)

• Added two new Decimate/Crop options to the DICOM Printer definitions. <AUTO DECIMATE> will automatically adjust the resolution of an image so that the image fits on the selected paper size if the image is too big to fit on the printed page (if it can fit, the resolution is left alone). <AUTO ZOOM TO FIT> will automatically adjust an image’s resolution so that the image will always print as large as possible on the selected paper size.

Version 3.0 (Build 76) (Released 2008-06-26)

• New tool added to strip the leading zeros from patient IDs that are not SSNs.

Version 3.0 (Build 75) (Released 2008-06-10)

• Reorganized menus for better layout and ease-of-use.
• Enhanced the image purging capabilities of the software. New options added to provide better functionality for purging images.
• Pop-up status window replaced with progress controls.
• Improved running as a service with Apteryx Servicer application.

Version 3.0 (Build 73) (Released 2008-04-17)

• Made a change during image move operations to better select a transfer syntax based on what the remote DICOM connection requested for transfer syntaxes for other abstracts.

Version 3.0 (Build 72) (Released 2008-03-26)

• Image modification checking now looks at custom revision DICOM tag.

Version 3.0 (Build 69) (Released 2008-01-11)

• Correct made for TEMP files remaining in the database when selecting several of the DICOM correction tools. These TEMP files are a safety mechanism that sometimes are not cleaned up.

Version 3.0 (Build 68) (Released 2008-01-08)

• Easy create database options added to the multiple database preferences. When enabled, the user can create databases simply by entering the database name (and possibly other information) and the databases are automatically created in the specified databases directory.
• Auto open new database option enabled to Edit Databases dialog (this dialog can be displayed from the Select Database dialog). When enabled, a new database is automatically selected and opened when the user creates a new database.

Version 3.0 (Build 67) (Released 2007-12-24)

• Multiple database support extended to allow the user to quickly switch between databases.
• Added options to prompt the user which database should be used when the application starts.
• Database naming added. Permits association of names, descriptions, contact information, addresses and notes with a database.
• Options added to automatically associate a database’s information to images when they are forwarded onto other DICOM servers. Overwrite protect can additionally be enabled or disabled.
• Title bar modified to display the name of the current database (if it has one).
• Preferences modified to permit more appropriate display and management of multiple database options.

Version 3.0 (Build 65) (Released 2007-12-21)

• Added tools to display what images will be forwarded.
• Added tools to remove images from the images that will be forwarded.
• Added new buttons at the bottom of the interface to display the image to be forwarded and to correct forwarding errors.
• Corrected artifacts that can be left behind from the pop-up status bar.
• Added “Auto fill in blank study descriptions” open in the Data Correction tools.
• Added Dental Modality mapping to map dental modalities to CR.

Version 3.0 (Build 61) (Released 2007-09-02)

• Additional optimizations to database interfaces.

Version 3.0 (Build 59) (Released 2007-05-17)

• Added SQL database support.
• Added new option to correct studies that have more than one patient saved under them.

Version 3.0 (Build 54) (Released 2007-03-07)

• Database directory structure checking optimized.

Version 3.0 (Build 53) (Released 2007-02-27)

• On edit image the study, series and image UIDs are now properly labeled.
• Merging database files together option added. Physically merges two DB files together without having to totally rebuild the database.
• Edit images dialog no longer wipes out any wildcards entered for the patient ID. Can now do wildcard searches on patient ID.
• Dates now prepend months and days with 0s.
• Worklist and patient lookup optmized.
• “Sex” changed to “Gender”.

Version 3.0 (Build 52) (Released 2007-02-12)

• Implemented database optimizations. Will require an initial database update when either the DCV or Data Server is started.

Version 3.0 (Build 51) (Released 2007-01-19)

• Made correction that permits image orientations, flips and inversions to be performed.

Version 3.0 (Build 50) (Released 2007-01-09)

• Added multiple image at a time correction capabilities.
• Added Done button to image correction screen.

Version 3.0 (Build 49) (Released 2007-01-08)

• Made modification to automatically handle when a target DICOM server no longer has a DICOM Server Definitions (i.e. User modified or deleted).
• Image tree modified to include additional information.

Version 3.0 (Build 47) (Released 2006-12-15)

• Corrects issues with aborting storage/forwarding of images when an invalid DICOM server is encountered (i.e. a DICOM server was renamed or erased). The new mechanism resubmits the image to all enabled servers when it finds an image destined for a non-existing DICOM server.

Version 3.0 (Build 43) (Released 2006-12-05)

• Added options and features to automatically age out and/or satisfy worklist entries stored on the server.

Version 3.0 (Build 41) (Released 2006-11-31)

• Significantly reduced the amount of time required to add images to the database.

Version 3.0 (Build 40) (Released 2006-11-30)

• Changed how patient information is updated in the pop-up auto-match lists when image information has been modified.

Version 3.0 (Build 37) (Released 2006-10-09)

• Made corrections to storage commitment to more accurately conform to the DICOM 3 standard.

Version 3.0 (Build 31) (Released 2006-10-03)

• Added features to permit the main database file and the images folders to be on different drives.
• Added features to permit generic IP addresses for returned CMOVE operations from remote DICOM servers.
• Addition of a Transaction UID to storage commitment DS.

Version 3.0 (Build 26) (Released 2006-06-15)

• Redesigned multiple thread support to reduce lockups experienced on heavily used systems.

Version 3.0 (Build 20) (Released 2006-05-31)

• Added enabling/disabling of database caching. When enabled it reduces database IO time but requires much more computer memory. Not required for computers that do not have heavy database IO.
• Implemented connection timeouts to kill off inactive DICOM connections.
• Redesign of communication handling.
• Possibly resource leak addressed when a remote DICOM connection terminates during and image retrieve.
• Interface freeze corrected. New thread generation implemented to circumvent a deadlock condition that could occur with Windows thread invocation.
• Can now close the server even when there are active DICOM connections (the user is prompted if they really want to close and terminate all live connections).
• Handle resource leak addressed.

Version 3.0 (Build 19) (Released 2006-05-11)

• Added support for modifying an images DICOM information.
• Added options for correcting invalid patient DOB.

Version 3.0 (Build 17) (Released 2006-05-09)

• Added support for compressed imported images.

Version 3.0 (Build 16) (Released 2006-04-25)

• Corrected a problem that existed in the copy images from DICOM server function and proxy image retrieval.

Version 3.0 (Build 15) (Released 2006-04-22)

• Logging for imported images into the Data Manager.

Version 3.0 (Build 14) (Released 2006-04-10)

• Integrated new status indicators.
• Copy images background corrected.
• Optimized image tree and image forwarding image selection.

Version 3.0 (Build 10) (Released 2006-03-16)

• Added new options that restricts the number of records that are returned in response to an image or worklist query. Defaults are 1000 image records and 100 worklist records.

Version 3.0 (Build 9) (Released 2006-03-15)

• Threaded DICOM query processing added. This significantly increases the response time from the Data Manager not only for multiple DICOM requests but for interacting with the interface while there are ongoing DICOM connections.
• Optimized database searching. Testing results indicated over a 85% speed increase in searches.
• Modified message that is displayed during image forwarding when the target server could not be reached.

Version 3.0 (Build 8) (Released 2006-03-06)

• Split DICOM server settings and accepted clients settings into different screens.
• Corrected several fields that were not disabled when DICOM server was enabled.
• XML implementation added for adding remote clients from the Configuration Manager application.

Version 3.0 (Build 7) (Released 2006-02-17)

• Added support for matching “O” sex to “M” and “F”. In other words, searching a sex of “O” will match “O”, “M”, or “F”; searching a sex of “M” will match “O” or “M”.

Version 3.0 (Build 6) (Released 2006-02-10)

• Added new memory handling routines for the database to counteract new problems encountered with various OS/antivirus updates.

Version 3.0 (Build 5) (Released 2006-02-03)

• New major version release.

Version 2.0 (Build 18) (Released 2006-01-25)

• Version info is now passed in XML information. This information is utilized the the Status Display Manager.
• Fixed problem when second DICOM server IP address is not specified. Leaving the field blank means that a second connection should not be opened (previous versions tried to open another DICOM server port even when this was left blank).
• The DICOM server definitions are reloaded if they are modified by a DEVAA/DCV client.
• “Copy images from” direct path specification added.

Version 2.0 (Build 17) (Released 2006-01-09)

• Strange memory anomalies corrected when various errors occur during DICOM communications.
• Update Database operations no longer adds the images to the “To Store” database.
• DBIT database is automatically deleted and reset if the user deletes the main application database without also deleting this file.
• Freeze display of error message removed when forwarding images to a DICOM server and that DICOM server is terminated in the middle of communications.
• During image forwarding, if NONE of the target DICOM servers can be reached for an image, the Image Forwarding operations terminates and waits for the next Image Forward cycle to start.
• If the user manually cancels an image forward, the software now prompts if the rest of the images should be forwarded.

Version 2.0 (Build 16) (Released 2005-12-30)

• Added multiple DICOM server port capabilities. The DICOM server now supports the ability to have two DICOM server IP address and/or ports available for DICOM requests.

Version 2.0 (Build 15) (Released 2005-12-27)

• Corrected selecting a modality for searching. Currently searched for “modality” tag; need to also search for “modalities in study” tag.

Version 2.0 (Build 14) (Released 2005-12-21)

• Corrected problem with pop-up menus of pop-up menus automatically being dismissed before the user can select an option.

Version 2.0 (Build 12) (Released 2005-12-19)

• Added new options for status utility to obtain more detailed information from this server. Detailed information retrieval requires XML interface to be activated on the server.

Version 2.0 (Build 10) (Released 2005-12-15)

• Corrected problem with focus issues with the popup graphic list controls.

Version 2.0 (Build 9) (Released 2005-12-15)

• Full DICOM server support added.
• Improved logging.
• Improved logging speed.
• Correction made where updating the interface could stall the application.
• Smaller database record size.
• New database format. Will require older databases to go through a rebuilding process.
• Correction made to CMove operation for certain patient/study/image specifications.
• New image routing tag specifications tab added to server definition.
• Wildcard matching level specification added.
• Cosmetic changes to interface and menus reorganized.
• Removed several options that are no longer utilized.
• Image forwarding added. Image forwarding now utilizes DICOM standard to forward images. Replaces the previous DM Synch features.
• Registration number is now required to run the application.
• DM Synch operations removed (replaced by image forwarding).
• “To be stored” and “Failed store” directories removed. They are no longer used; have been replaced by new image forwarding.
• XML protocol added for tertiary application interface to the application.
• XML logging added.
• Operation restrictions may now be specified for each DICOM client specified.
• Image tree improved.

Version 1.0 (Build 25) (Released 2005-10-20)

• Modified record handling in memory to prevent significant delay that can be encountered with large databases.
• New menu scheme.
• Boosted and optimized image tree functionality. Additionally, image information now contains more information about each image.
• File count status message added.
• “Updating Records” status dialog added.
• Column names have been changed.
• Logging connections added.
• New improvements and start of full DICOM server support are included in this build BUT SHOULD NOT BE USED.

Version 1.1 (Build 22) (Released 2005-08-19)

• Integrated new tree control view.

Version 1.1 (Build 20) (Released 2005-07-25)

• Optimization of size tracking added. Significantly speeds up the data base size tracking

Version 1.1 (Build 19) (Released 2005-07-07)

• Database I/O optimization added.
• Update database operation dramatically improved.
• UID error correction.

Version 1.1 (Build 17) (Released 2005-07-06)

• Added non-blocking support when a remote DICOM server abnormally terminates a completed DICOM operation.

Version 1.1 (Build 16) (Released 2005-06-13)

• DICOM print support added.
• Reformatted menus.
• Reformatted failed stores list.
• Interface changed to provide more information and feedback.
• DM Synchronization support added.
• Connection status list added to interface.

Version 1.1 (Build 14) (Released 2005-05-19)

• Added option for retrieving all images from a DICOM server.

Version 1.1 (Build 12) (Released 2005-05-06)

• Added option to allow importing images into the local database with additional option to allow submissions to DICOM servers.

Version 1.1 (Build 11) (Released 2005-04-11)

• Added additional options to determine a study date if one is not directly associated with an image.

Version 1.1 (Build 10) (Released 2005-04-07)

• Strange phenomenon corrected where an images reference existed in the database but the actual image file did not exist (several situations could result in this problem from file store errors to user intervention). To reduce the amount of file IO required to satisfy proxy requests, the DM only checked for the reference in the database and not for the existence of the actual image file. The DM now checks to be sure a file exists and adjusts accordingly.

Version 1.1 (Build 8) (Released 2005-01-25)

• Additional option added to prevent hanging connections with the MedWeb.

Version 1.1 (Build 7) (Released 2005-01-18)

• Store now option enabled.
• Data Manager now queues stores and retrieve requests separately to prevent multiple transfers from being invoked from the same IP to a DICOM server. This change is to correct problems with some DICOM servers that cannot accept multiple concurrent transfers from the same computer.
• New Apteryx DICOM UID added.
• Real time space utilization option added. This option ensures that disk space utilization numbers are always up-to-date instead of periodically updating; note that this feature will use additional computer resources.

Version 1.1 (Build 6) (Released 2005-01-11)

• Corrected a problem where it is possible for the DM to not automatically dismiss its storage dialog (thus hanging the server) when a certain storage error was returned by the target DICOM server.

Version 1.1 (Build 4) (Released 2005-01-10)

• Maintenance build.

Version 1.1 (Build 3) (Released 2005-01-08)

• Changed name on main dialog.
• Added patient name caching support.
• Enhanced “Update Patient Database” option to also update the patient cache.

Version 1.1 (Build 2) (Released 2004-11-23)

• Made modification to prevent the server from stalling when a detrimental failure is received from the DICOM server during image retrieval.

Version 1.1 (Build 1) (Released 2004-11-20)

• Proxy image retrieval support added.