eRAD
PACS Server
eRAD
PACS Server
When the user changes some settings, a session refresh updates those settings so they take effect immediately. Changing the assigned viewer was missing from this list of settings. As a result, changes to the applicable viewer didn’t occur until the user initiated a new web session.
Successive merges create a series of moveto flags so late arriving objects end up in the appropriate merged study. After deleting the merged study, resends of all but the last merged study failed to register due to mishandling the study identifier. This has been resolved.
Global restrictions were unintentionally blocking non-study related data from the Logs page. This has been resolved.
The setting to send a notification to a web services device when a study is deleted was not getting saved when edited from the Devices page. The wrong event handler was incorrectly applied. This has been resolved.
The user account lock status and the login details reported incorrect information when the user selected the account by checking the selection check box at the beginning of the row. The information was also inconsistent when multiple accounts were selected. This has been resolved.
When loading a dashlet, an exception could occur after login due to failure to check for an initialized variable. This has been resolved.
A client side exception occurred when the user logged out before the worklist could display immediately after logging in. This has been resolved.
When a worklist refresh occurs (manual or automatic) while editing a report in the patient folder on a worklist on which a study disappears, reordering the worklist rows refreshed the report edit page as well, clearing report data that might have been entered. This has been resolved.
Autocorrecting studies to orders using patient name as matching criteria and a patient name containing an apostrophe resulted in a search exception and a failure to autocorrect. This has been resolved.
Uploading attachments to studies or orders completed without error but the attachment was not saved. This was due to a corrupted environment variable extended by the MCS component’s control script. This has been resolved.
The hyperlink in a notification email that launches the images in the web viewer was missing the login prompt. If a browser did not have a valid session cookie already, the web viewer failed to load images. This has been resolved.
When requesting to clear the cache from the Tech View page very quickly after loading the web page, a maintenance procedure might fail to complete before starting clearing the cache, resulting in an error and the cache data remaining in the repository. This has been resolved.
The dotcom validation tool reported an error when it detected empty and NULL values in the same database column. This error message has been suppressed.
While an empty email address is appropriate in some notification email configurations, it is required when the list owner is the system account. In these cases, users are prevented from activating the action until an email address is provided.
When a user-initiated task-related action, such as changing the priority of a scheduled task, incurred an error, the return code was mischaracterized, leaving a lock in place. As a result, new tasks would not run. This has been resolved.
The user name filter drop down menu used the user name and user ID interchangeable, both in display and database query, leading to confusing results. The field permits users to enter user names and both the user name and user ID are displayed, but when the command is invoked, the value applied is the user ID. This has been resolved.
When some non-visible characters, such as the left and right arrows, were entered into a user name field drop down panel, such as when filtering on the user name, the web page triggered an unnecessary call to search the database. This has been resolved.
Some default items in the user name drop down menus are supposed to remain, even when the type-ahead string is applied, but they were filtered out. This has been resolved.
On the manual forward setup page, the user name field (when forwarding to a folder) could become obstructed by the popup menu. This has been resolved.
When clicking out of a text entry field when configuring the default user in a web services device edit page, the stylesheet was cleared and when clicking back into the text field, the user’s custom color setting was not applied. This has been resolved.
The report selection tools in the report view in the worklist’s patient folder were functioning incorrectly: the color scheme was hardcoded to dark theme; the report component icons failed to select the corresponding report component; and the delete button was highlighted instead of the report component icon. In addition to resolving these issues, a new button, Open All Reports, was added to load all the report components into a single view.
REVERSIBILITY NOTICE: To downgrade, the plugin license(s) must be regenerated.
The mammography, volume 3D and fusion plugins’ short names changed from the ones used in v7 so after upgrading, the plugin license was not recognized. This has been resolved.
A couple webpages determined to be vulnerable to SQL injection threats have been secured.
Multiple collapsed prepStudy tasks could exist in the task queue at the same time due to a racing condition when creating these tasks. This has been resolved.
prepStudy tasks in the retry queue could not be terminated by the post-collapse cleanup function. This has been resolved.
A change to the filter construction was not applied to the user account page’s Last Seen, Sign in, and Sign out fields causing a format exception when attempting to filter on the field’s value. This has been resolved.
A change to the time’s short format handler did not handle requests for negated search criteria. This has been resolved.
The tag list available when configuring calculated fields was unsorted, making it difficult to locate a specific tag. This has been resolved.
Images having an aspect ratio other than 1:1 caused the technology view page’s carousel to show partial images and the scrolling tools to fail. They also rendered the page’s thumbnail image size options useless. This has been resolved.
When toggling between the Security Settings page and other server configuration pages, the security page contents may refresh and overwrite the other page’s data because an asynchronous call might have taken too long to complete. This has been resolved.
In a dotcom where the master is the child server, a report edit could get processed on the child and propagated to the parent before the parent registered the original report. If a report notification event arrived at the parent before the report was registered, the event notification failed to trigger before all the fields were updated. This has been resolved.
After correcting the importation of custom worklist layouts when upgrading from v7.2 to v8, the action buttons and lock indicator were dropped because v7.2 does not store them in the worklist configuration. By default, upgrades include the default v8 worklist action buttons.
The method used to open the help pages in a new window blocked pop-ups by default. The setting has been changed to allow the new tab to open without user acknowledgement.
The Study Changed field did not recognize saving report objects. As a result, the study fingerprint wasn’t updated and the change state remained untouched. This has been resolved.
When creating or modifying a DICOM device entry using a duplicate AE Title and the user decides to ignore the warning and save it anyway, the software failed to apply the change because the override flag was ignored. This has been resolved.
If a saved worklist contains conditional coloring on a hidden column, an error occurs because the coloring tool cannot locate the column and the worklist appears as an empty list. This has been resolved.
A user account’s password settings could be applied after making temporary changes to the account’s LDAP settings, even when the account was configured to use an LDAP authentication agent. This has been resolved.
Report view templates using a field with the VR of SI, such as the Interpretation Status ID field, would log errors and display no data because support for the VR type was removed. This has been resolved.
When a DICOM AE requests a study using a DICOM Retrieve request, the forward tasks could fail to apply the soft edit changes causing the data to be sent without the latest updates. This has been resolved.
When using the local MCS service from a worklist server to create DICOM media containing studies from two or more different hub servers, the temporary directory names created on the hub servers did not always match the directory names on the worklist server. If the names were not unique, the conflict resulted in missing files. Additionally, the MCS started constructing the DICOMDIR file after the transfer from the first hub server completed, without waiting for transfers from all hub servers to complete. This has been resolved.
An insufficient lock timer caused studies to be left in a bad state when references were being deleted by the system. This has been resolved.
After upgrading Chromium (used by Chrome, Edge, Safari and other browsers) to Version 106.0.5249.103 or later, some of the browser’s drag and drop features such as applying a worklist filter from a column header or column value corrupted the web page contents resulting in a disorganized layout. This has been resolved.
The length of enumerated values assigned to a database field were not checked and resulted in unexpected values and results. The length is defined on the setup page and values lengths are enforced before saving them. This has been resolved.
Worklist filters for name fields, study size and multi-value fields have been updated to support features available in earlier versions, including the ability to search on individual name components. This has been resolved.
Some operations could be copied from the browser’s network panel and invoked from another browser by a user with different permissions, allowing users to perform unpermitted operations. The missing permission check has been applied. This has been resolved.
Some operations could be copied from the browser’s network panel and invoked from another browser by a user with different permissions, allowing users to perform unpermitted operations. The missing permission check has been applied. This has been resolved.
Some operations could be copied from the browser’s network panel and invoked from another browser by a user with different permissions, allowing users to perform unpermitted operations. The missing permission check has been applied. This has been resolved.
Insufficient checking of a return code permitted some system lists (ie, owned by the @system account) to appear on a non-admins saved filter list. This has been resolved.
Some operations could be copied from the browser’s network panel and invoked from another browser by a user with different permissions, allowing users to perform unpermitted operations. The missing permission check has been applied. This has been resolved.
After upgrading the DICOM toolkit, the server’s connection timeout handling failed to recognize the configured timeout values and applied the default instead. This has been resolved.
The delete confirmation page was missing the lock icon indicating which studies were locked and unable to be deleted. This has been resolved.
When a hub server is backed up, the command to purge an order across the dotcom after correcting it to an image failed to propagate. As a result, the study could not be opened from the RIS because the search for the study returned multiple items (the study and the lingering orders). This has been resolved.
The system ignored global restrictions when selecting the next/previous study. If the user does not have permission to view the study selected, he/she ends up with an invalid study error. This has been resolved.
When a registered viewer device issues a cache state request to the server and the server does not have an explicitly defined prior study cache state setting, the parsing algorithm misinterprets the parsing results and registers an unnecessary exception in the log file. This has been resolved.
Newly created document types failed to show up on the document type configuration page until after a browser page refresh. This has been resolved.
Uncaught exceptions coming from Internet Explorer were not handled properly, resulting in a web page exception. This has been resolved.
When a study update and study acquisition event occur within the same period, the study acquisition notification message could be suppressed due to the message reduction process. Now, study acquisition events are no longer collapsed with study update events. This has been resolved.
DEPENDENCY NOTICE: This fix loads the page but does not display images when using Internet Explorer to load the Tech View page from the RIS. A change in the RIS is required. The version containing that fix is undefined at this time. Use Edge or Chrome browsers instead. The RIS uses an IE control to embed the Tech View page into its web page that does not support the PACS page’s javascript. As a result, the web page did not load when using the IE browser. This fix allows the web page to load, but images still do not display because IE does not support the necessary technology needed to decompress cw3 data. This solution will be in the RIS (31775)
The delete button was not available from the patient folder if the study contained more than one report object (i.e., there was an addendum to the main report). This has been resolved.
Viewer sessions were not recognized after restarting Apache, causing the cached data fields (eg, Percent Loaded) to report no data until the user logged out and back in. This has been resolved.
A system lock failed to be released because of a missing constructor. The constructor has been added to avoid the stuck lock. Also, when a user attempted to break the system lock, which is not permitted, the user received no explanation of why the lock remained. Now the user is informed he has no permissions to break a system lock.
Searching a worklist using a date value in the quick filter field that would result in a query qualifier exception returned an error message and no data because the date filter was improperly encoded in the database search request.
When using a custom port to launch the web viewer, the server would mishandle parsing the URL to locate the host name, causing the request to fail. This has been resolved.
If the tasks page’s filter panel was open when the user called up a different web page, the filter panel was not closed and remained on the screen. This has been resolved.
Back-end support for forwarding studies from the patient folder was incomplete, resulting in no action when the button was clicked. This has been resolved.
Identifying the email address offered as the default when configuring a Notify action failed for internally-defined accounts, such as the system account. In this case, the default comes up empty, requiring the user to explicitly declare the email recipient. This has been resolved.
User accounts with empty passwords, which is not a valid state, could not be corrected because the missing password was not handled and caused an error when editing. This has been resolved.
Parsing the date-time values in patient folder notes assumed a 12-hour clock rather than a 24-hour clock.
Correcting a study to an order might fail because orders don’t have an owner hub, which is required to determine where the combined study resides. As a result, manual corrections from the GUI reported a failure to the user. This has been resolved.
When a DICOM query response contains no Retrieve AE Title or multiple Retrieve AE Title values, the server fails to retrieve any data. In the case of no AE Title, the server attempts to retrieve the data from the same AE that responded to the query request. When multiple AE Titles exist, the server attempts to retrieve the data from the first AE in the list having an entry in the Devices table configured as a Q/R provider.
TIFF file uploads were not checked for multiple pages, resulting in uploading the first page only. This has been resolved.
When configured to use the stream server for the web viewer image transfers, a mismanaged pointer was released after the first image in the study was transferred, causing subsequent image transfers to fail. This has been resolved.
Updating the study status when saving a report locked the PbR file unnecessarily, causing the report saving process to wait until a timeout expired before completing the operation. As a result, the entire report saving effort took five seconds longer than necessary. This has been resolved.
Depending on the timing of PbR edits received from local and remote devices (eg, the RIS), it was possible that exports requiring soft edit merges could use a temporary instance of the PbR that did not contain the latest edits, causing some edits to be missing in forwarded objects. This has been resolved.
Updating a password in User Preferences resulted in an error. This has been resolved.
Obsolete columns displayed on the Logs page’s details panel have been removed, and a missing column, Peer Device, has been added.
Media creation initiated from a worklist server using the original media creation engine (i.e., not the MCS) could time out if the resulting data file was very large. This has been resolved.
When configured to use the local MCS, a worklist server was leaking tomcat and hermes threads when collecting progress information, causing the system to hit the process limit and stop creating new threads. This has been resolved.
The peer device field on the Logs page is filled in only when the device ID is registered on the server serving up the Logs page. This has been resolved.
The canned report macro has been added to the built-in default report edit template.
There was no limit to the worklist filter’s text box. Criteria exceeding the database field’s defined length were truncated, without warning, leading to unexpected results. Truncation also occurred when upgrading v7.2 filter definitions to v8. When detected, the import for the filter is aborted and an error is written to the log file and console.
The type-ahead feature in the user profile field used when creating DICOM media failed to detect changes to the default value if the backspace key was not used, causing the system to ignore some matching IDs.
V7.2 servers upgraded to v8.0.22 or later and containing a large number of entries in the archive log database table would encounter slow archive log searches. For searches spanning one year or more from the current date, the views combining log archive tables are handled directly and not through the database because the database (MySQL) does not support the specified indices.
Creating a report for orders which were a) created on a worklist server which is not the topmost server in the dotcom and b) in the Completed state could not be saved for a number of reasons, including no support for checking locks on complete orders, ownership issues for orders not owned by the top-most server, and failure to lock a study with no images.
Attachments whose filename used upper case letters in the file extension failed to upload because the file type validator is case sensitive. This has been resolved.
Discontinued actions, including the fax action, were not ignored when converting the user database during an upgrade to v8. These actions are now ignored and log entries are created when detected.
If the stream server is processing an image for one study when it receives an instruction to start processing a different study, the stream server could crash due to an invalid reference. This has been resolved.
If the worklist does not include the lock status column, the lock status tool on the floating toolbar fails to indicate the study’s lock state. This has been resolved.
Partial deletes, including deleting reports from a Store server, failed to process the delete request, leaving the objects registered and accessible. This has been resolved.
Acknowledging notification popups that happens immediately after login could cause an exception that prevented the initial worklist from drawing. This has been resolved.
The system failed to recognize an auto-retrieve device was configured offline (ie, “downed”), causing the patient folder and relevant priors page to load slowly as it checked for priors. This has been resolved.
Series and image level DICOM query requests proxied from an objectless parent (CWL) server to the owner (hub) server failed because a recent change to the default object state setting caused the owner server to incorrectly ignore the request. This has been resolved.
When deleting a study, the options to delete the entire study throughout the dotcom (i.e., delete “immediate”) and to keep the report object are mutually exclusive. If the user selects one, the check box for the other is automatically disabled. This has been resolved.
The worklist’s Open buttons on Worklist servers were enabled for unsupported (incomplete) order states. When unsupported orders are included in a group selection, the open tools are disabled.
When logged into a child server and retrieving a study from a remote archive connected to the parent, the data was retrieved from the archive but never transferred from the parent server to the child server. This has been resolved.
Worklist filters converted during a v7.2 to v8.0 upgrade and containing at least one filter with a single, untagged criteria defined would get corrupted after being manually edited and saved from the (v8.0) worklist page. This fix applies to filters converted during an upgrade from v7.2 or v8.0.8 and earlier. This fix does not correct filters corrupted by this bug.
V7.2 servers upgraded to v8.0.22 or later and containing a large number of entries in the archive log database table would encounter slow archive log searches. The search performance is corrected for searches spanning less than one year from the current date. Searches for archive log entries older than one year will take some time to complete and place a load on the system.
The system ignored the parameter to add the viewer to the media created by a standalone, remote MCS server, always including it. This has been resolved.
When the stream server created missing cw3 files, it ignored the compression flag settings and always created the intermediate raw files. This has been resolved.
When the post-process action processes late-arriving options, the system ignored the compression flag settings and created cw1 and raw files, and never cw3 files. This has been resolved.
When updating the log after forwarding a study, a bad log table ID posted an unwarranted error message in the log file. The error was unwarranted because the system figures out the correct ID. This has been resolved.
Accented characters appearing in date fields on the report panel/page displayed incorrectly because the HTML encoding macros mishandled the data. This has been resolved.
After appending an existing dictation from the report panel after having played the wav file from the report page, listening to the dictation from the report page played back a cached version rather than the amended dictation.
The escape character, backslash, used in coercion rules failed to work on itself, preventing a rule from inserting a backslash character into an attribute’s value.
When setting up a purge action to delete select study objects from an object-less worklist server running in a mixed mode environment, the system could not identify the selected objects because it expected them in the local object table. As a result, it failed to remove the objects when the action ran. This has been resolved.
When using a remote MCS server, if the user initiating the media creation job does not exist on the MCS server, an exception occurred and an empty report file was included on the media. Note that if the user initiating the job does not exist on the MCS server, the MCS uses the system default user account and it’s settings to create the media.
The XML layout customization pages have not been updated to use v8 technology. As a result, some features might result in an exception when applied, such as previewing a customized template page.
The user group fields in the action table were case insensitive while user and group IDs are case sensitive, causing two users with the same ID, except for case, to see and affect each other’s assigned actions.
A required v7.2 redictation component was missing from v8, causing attempts to redictate a report to encounter a java exception. This has been resolved.
The coercion syntax checker has been added when configuring coercion rules for Edit actions.
If multiple Compress Data actions on saved lists contain the same studies, and a study is processed for each at exactly the same time, and the system receives a report object (eg, from the RIS) while both studies are being compressed, the report object could be deleted because the compress action used a non-unique temporary file name. This has been resolved.
When configured to skip raw file creation, the system still created them when the user manually reprocessed a study (by clicking the tool on the tech view page). This has been resolved.
When searching for non-empty values (“is not empty”) in a customer field configured as a list of enumerated values, the search failed to handle the negation properly and returned the list of records with empty values.
A user’s permission to edit reports didn’t consider whether the server was licensed to use the reporting tools until the user attempted to save a report, at which time the request failed. Now, the report editing features are disabled if the server is not licensed to create reports.
The web viewer’s development framework, GWT, failed to handle two-finger scroll requests applied to a trackpad. The GWT feature has been bypassed with a custom handler.
Changes to text fields on the Server Settings pages, including Local IPs and User Actions, were uploaded incorrectly and therefore were not saved. This has been resolved.
After adding the new configuration levels, changes made to the data format settings (date, time, name, etc.) on the Server Settings page failed to take effect because the old level values were left in the cache. This has been resolved.
Removing a time component, such as seconds, from the time format setting was misinterpreted to mean use the default, which includes most of the time components.
The name format setting was not applied to names exported from the worklist page, causing exported records to use the built-in default name format.
When using Dragon (Medical One) with a plain text report panel, the user encountered a script error because the Evo Viewer was not updated to support Internet Explorer 11 plain text. This has been resolved.
The correct number of attachments was overwritten with an incorrect value when uploading a PDF document or scanning a JPEG image. This has been resolved.
When an action was configured to run at a defined time each day, it completed successfully but disabled itself and didn’t run again unless manually re-activated. This has been resolved.
List pages failed to show the available fields from the filter panel for users without layout edit permission. This has been resolved.
If a user account exists but has never been used to log in, the account is uninitialized, causing a problem collecting folders. As a result, the Folders page would show no folders, for any users. This has been resolved.
The option to cancel an archive move request was missing. It has been added to the curtain (page).
A confusing label for the displayed time zone setting has been clarified.
The system allows each field to exist only once as a worklist filter but users were not prevented from adding the same field multiple times. Now when a user attempts to add a field that is already specified, focus goes to the existing item.
During a recent change to protect against forwarding orders unnecessarily, the forward tool was disabled in the toolbar available from the worklist’s patient folder. It has been restored.
Date-time fields, such as DATE, inserted into notification templates displayed an empty value because the feature failed to handle compound fields. This has been resolved.
A lock status refresh could return a status of unknown. This value was interpreted and applied (as unlocked) rather than ignored. Depending on the lock state, this might cause the lock indicator to blink. This has been resolved.
Web services clients could not create media if the study had a report and the request requested it be included, and the request was issued from a different device (IP) than the last request. This has been resolved.
Compound lists could be saved using the same name as one of its component lists, which created a loop that resulted in an error. This has been resolved.
Uploading studies to a worklist server should always redirect the request to a hub server. If the system is unable to identify the correct target hub server, it informs the user of the situation and will not upload the study until the user selects a target hub.
The target group account ID was mishandled when using the Copy Profile tool to copy settings to a group, resulting in the creation of a new group and identifier whose ID is preceded by two pound (#) characters. This fix does not remove these unintended groups. They must be cleaned up manually.
The system did not require a target device when configuring a forward action. With no target, these actions failed. Existing actions with no target need to be corrected manually.
Orders are not meant to be opened in the viewer so the Open button on the worklist has been disabled.
Deleting a device while it is disabled failed to remove the downed file. If a device was later created using the same name, the recollect function reported an error. This has been resolved.
Importing a user’s v7.2 web viewer settings stores the data correctly in the database but at startup, medsrv updates the configuration settings file from a conversion file, not the database. As a result, the web viewer does not use the imported settings. This has been resolved.
If some objects are deleted from a study (from the Tech View page) and the last two are processed simultaneously, the release handler can be called twice but it doesn’t lock the resources, resulting in a calculation error in the reference counter. This has been resolved.
Conditional row formatting on the worklist page failed if the matching criteria was set to an empty value because empty values were ignored and always returned a success status. This has been resolved.
Very old objects could not be edited because they were missing a private DICOM attribute the system inserts in the object. Handling objects without this data is now supported and edits complete
successfully.
When opening a completed order from an objectless worklist server, the viewer’s patient folder fails to load because completed orders don’t have owner devices, like imaged studies, and when the patient folder collection process looked for the owner device, none existed.
When patient matching queries contain non-unique data, such as an empty patient name or accession number, the system places a hard limit on the number of matches returned. This limit is 500. It is configurable on the GUI, at Admin/Server Settings/System/Set matching criteria/Patient Matching Hard Limit. If this limit is exceeded when searching local studies, no search is performed to find remote studies. Also, the system assesses the query criteria and 1) if the query criteria match a list of configured filters and values, such as a NULL patient ID, either aborts the query or skips the filter. In these cases, a single match is returned and the user is notified partial results are displayed. Rules can be configured from Admin/Server Settings/System/Set matching criteria/Patient Matching Field Rules.
Study merging is performed by the owner device. If studies in the merge request were owned by different child servers, the merge request failed. Now, the merge request will be performed by the hub server.
A possible security vulnerability affecting Apache Tomcat (CVE-2020-1938) has been eliminated.
The web services call to create users failed to check for an empty string user ID, allowing the system to create a user ID it was unprepared to support. This has been resolved.
The compress data action unintentionally updated the Receive Date. The original Receive Date is now preserved.
After deleting a parent device from the Devices table, the list of device types was not updated to include Parent again, until medsrv was restarted. This has been resolved.
The tool tips displayed on the patient folder used data from multiple sources which contained different values, resulting in different labels at different times. This has been resolved.
The private SR object containing the herpa (blue line) data which is stored on exported media showed up on the CD viewer’s study list as a separate study. This occurred when the MCS started to prepare the study for the media before the MINSOPInstance object was fully registered. This has been resolved.
Error messages displayed when setting up an MCS server were not cleared when dismissed by the admin because the data needed to clean up the error condition and clear the message was missing. This has been resolved.
Unnecessary separators have been removed from the email address field on the user account details page.
When a retrieve Action is performed on an order that no longer exists (canceled or corrected to a study), the state was marked to retry and the action was attempted again during the next cycle. This has been resolved.
Collapsing registration tasks called a cleanup function that removed the task references for all objects in the collapsed task, even the ones that were not registered.
In a worklist/hub environment, displaying a report in the worklist’s patient folder disabled the buttons to display the web viewer, attachments and notes due to a cross site scripting error introduced to check that the report’s iframe wasn’t being edited. This has been resolved.
A free text filter panel on the user accounts page was used for session date fields, including Last Seen, Sing On and Sign Off.
The timed-out sign off event’s date was saved in the database using a date format inconsistent with other saved dates. This has been resolved.
Editing a study with soft edit enabled always updated the Receive Date value because it stopped checking if the modified object was the MinSOPInstance as a result of a change in medsrv-8.0.32. This has been resolved.
Report web pages were missing some standard and optional settings because a function was not upgraded to include the settings in its output. This has been resolved.
If the separator fields in the date format setting were empty, the parser missed them and the resulting date strings were incorrectly formatted. This has been resolved.
The results of a repository validation ignored the applied color scheme, displaying the results in black text even when the selected background color was dark. This has been resolved.
Using a web services call to both create a session ID and launch the viewer failed to launch the viewer if the user did not have admin privileges because a call to collect basic user information mistakenly required the right. This has been resolved.
A media PACS device created on an MCS server did not default to a DICOM Q/R SCP and a Storage SCU and would not save the AE Title because the function to save the data was not called for this device type. This has been resolved.
When copying user settings from one user account to another, the saved lists making up a compound list referenced the source user’s saved list rather than the new user’s saved list, resulting in invalid compound lists. This has been resolved.
Attempts to update study details (eg, patient name, MRN from the PbR) while also updating details about the representative object (ie, the one used to baseline a study’s data in the database) could be done in the wrong order, leading to incorrect data stored in the database. This has been resolved.
A prefetch service function was locked so a single client’s request could be completed without interruption, but if the locked request included a long query, other clients could time out, leaving large numbers of threads unavailable waiting for timeouts to free them. This has been resolved.
The latest version of DCMTK included a change enabling TCP’s nagle algorithm (used to improve efficiency by reducing the number of packets sent) which impeded DICOM transfer performance. The feature has been disabled.
Studies a user does not have direct access to but are opened because they are priors to studies a user has access to fail to load the report because the system checked the permissions based on the user’s main access list. This has been resolved.
Rich text from Microsoft Word containing style tags were not processed correctly when pasted into a report panel. The result was the style command parameters appeared as normal text in the report. This has been resolved.
The account type for the existing web service default user was not set correctly during upgrade, preventing the admin from assigning the default user to newly created web service devices. This has been resolved.
The color selection panel in the Preferences section of the user account edit page was missing on the first display attempt. This has been resolved.
Menu items with no dedicated web page, such as importing media, failed to check permissions prior to invoking the request, allowing users without media import rights to import studies. This has been resolved.
Saved Archive page lists have been added as a group to the Other Lists page.
Applying negative search criteria to an enumerated value field, such as State, displayed the correct results but the criteria displayed on the page was incorrect. This has been resolved.
The batch edit function on the Group Accounts page failed to collect all the selected groups IDs, editing only the first selected group. This has been resolved.
Permissions have been assigned to some dashlets. Users must have administrator rights to create and view dashlets showing system statistics. Users must have support rights to create and view dashlets that can edit database records or issue custom database queries.
Corrected exceptions to the rules in which compound worklist filters cannot be created from compound filters, and all filters in a compound filter must be owned by the user creating the compound filter.
When adding a device, the list of supported SOP classes defaults to the system default list but failure to check for an empty list in addition to an uninitialized list caused the default to support no SOP classes. This has been resolved.
The batch selection tool on some pages (Other Lists, User Accounts, Group Accounts) failed to select all studies. This has been resolved.
The select all option in the batch select tool on the User Account and Group Account pages failed to collect all the matching entries, resulting in editing only some of the selected accounts. This has been resolved.
Due to a browser’s secure cookie management, switching the system’s security setting from HTTPS to HTTP prevented the user from establishing a new session (manifesting as login failures) until the browser removed or invalidated the secure cookie. This has been resolved.
Copying a hanging protocol from one user to another user who has no hanging protocols defined, not even the built-in defaults, resulted in a crash because the system failed to handle the empty list. This has been resolved.
If the parent server is using HTTPS and the child is configured to use HTTP, requests to upload attachments failed due to a mixed context error. This has been resolved.
The DICOM media target appeared on the Forward setup page, and was active, when the user did not have permission to create DICOM media. This has been resolved.
Two internal fields were not included in a hidden field list and showed up on the Other Lists table, unlabeled and uneditable. This has been resolved.
An unnecessary warning indicating a media upload request has been redirected to a (hub or child) server configured to store data has been eliminated when the server is capable of storing the data itself.
The fields available for display on the Archive page are limited to those available in DICOM query responses.
The tool used to select all the user accounts in the system was modified to update the check boxes after collecting all the data, improving the time for the selection to complete, particularly on systems with thousands of user accounts.
The format of study log entries has been restored to their original format, restoring some missing fields and allowing third party scripts to work again.
When the correction source is defined as the RIS, and the data in the order matches the data in the image object, the value could be removed from the PbR object when auto-correction completes, causing the study to register an empty value and appear blank on the worklist. This has been resolved.
The Series Number value was misinterpreted as a hexadecimal value and erroneously converted to a decimal value on the Tech View page. This has been resolved.
When locking a study, the worklist’s lock indicator displayed in red, indicating the study is locked by another user, rather than yellow, indicating you locked it. This has been resolved.
Duplicate names are rejected when creating and editing device categories.
The hyperlink used to download desktop apps did not apply custom port configuration settings, preventing users from installing these services. This has been resolved.
Displaying the Server Information page from a worklist server took a long time to collect the study volume information when it hadn’t been collected recently and when large log files existed. The process now collects baseline information during an off-hour cron job and the web page uses this information rather than collecting it on-demand from the log files. This has been resolved.
Patient matching criteria set to use subsets (e.g., the first three characters) from more than two name components failed because the resulting database query didn’t account for trailing data in the name values. This has been resolved.
When a web services command is using the default web services user account, the missing credentials was interpreted as an error, resulting in a failed login log entry for every command. This has been resolved.
Multiple failed login requests that occur in the same second resulted in a single error log file entry because the log entry ID value used seconds and would not be unique. This has been resolved.
A recent bug fix intending to verify a worklist filter satisfies the query qualifier’s unbounded query criteria failed to work on newly created filters because it attempted to use the filter by name before it was saved. This has been resolved.
When a delete action is defined to keep the report and execute the purge (as opposed to simply mark eligible studies, a feature used internally), the rule set is empty and the purge action would not run. This has been resolved.
The original, jetty-based streaming technology used by Evo viewers and the web viewer failed to release websockets when the study being downloaded changed and the underlying thread encountered an exception when terminating. This has been resolved.
Renaming old folders failed because the check for an existing folder with the same name referenced the wrong field. This has been resolved.
If a user with a custom default worklist filter created a folder, it disappeared from the folders and forward page after an apache restart because all folders with list description tags are moved to the list section of the user’s configuration file during restart. Note that the folders need to be recreated, but the content in those folders is unaffected.
When importing data from DICOM media, failure to create a DICOMDIR file due to invalid data on the media resulted in a silent failure. Now the user receives a notification indicating the media could not be imported.
Web services commands to edit a report issued to a worklist server in a multi-level dotcom failed because the RMI command sent to the child server did not use the RMI-specific session mechanism, resulting in permission failures. This has been resolved.
When a log or archive page query results are truncated because the number of total matches exceeds the applied limits, a partial results warning is displayed but only when there are more results to display. The warning was missing on the last page of the results. This has been resolved.
The viewer failed to display the notice informing a user that they lost the study lock because of a formatting error in the message the server sent to the viewer. This has been resolved.
If the user issues a quick search after editing the layout of the worklist, the results might appear using the original layout and not the modified layout settings. This has been resolved.
If in the process of configuring a compound worklist one of the source lists got deleted, the system failed to notice and saved the compound list, resulting in an exception when applying it. This has been resolved.
The rename and delete options on the Other Lists page are disabled for group lists unless the user has the required admin rights.
Non-urgent broadcast messages did not record the last update time and therefore would not appear in the message panel or dashlet. Additionally, when the only messages in the queue were non-urgent broadcast messages, the missing timestamp caused inconsistent list details, resulting in a logged exception. This has been resolved.
After creating and then editing an order via web services commands, some fields would not appear updated on the worklist because group order handling treated them as new orders (in the group) rather than modifications of the existing order. Edits that apply to an existing procedure step, based on the procedure step ID, are now treated as edits and not new orders in a group order.
The media creation server (MCS) always used the primary IP address of the server when constructing the download URL. If the certificate does not include this IP address, an error occurs when attempting to download the media file. A configurable server address and redirection rules have been added to accommodate environments running under these conditions. See Media_Creation_Server
Maintaining a list of studies open in web viewers was not thread safe. Simultaneous requests to load studies in a web viewer corrupted the list, causing an exception to subsequent web viewer open requests and a 104 error page displayed in the browser window. This has been resolved.
The error message displayed when attempting to log in with a non-existent user ID provided too much details about the login failure. The updated message is more generic and secure.
When upgrading from v7 to v8, worklist layouts that contain no customizations were inserted into the database as NULL entries, resulting in an exception when applied. Empty layouts are converted during upgrade and existing layouts are detected and handled correctly.
All logs pages consisting of more than one page of records indicated the results were “partial”, even when this wasn’t the case. This message should only appear on the logs page when collecting logs from other servers in a dotcom.
Web services calls were not updating the session, allowing the session to expire sooner than the inactivity timer specifies.
While taskd was stopped, order updates received via HL7 or web services were treated as new orders, resulting in duplicate orders in the PACS worklist. This has been resolved.
The object-matching settings for a Purge action did not list the configured attachment types, meaning users could not set up an action to purge select attachments. Additionally, the system failed to check the attachments type when matching attachments to the purge criteria. This has been resolved.
Filter macros using the format $$<COLID>$$ were not recognized, causing the filter criteria to return no results. The literal filter value defined appears in the filter criteria panel but the resolved macro value appears in the filter box at the top of the results. This has been resolved.
Web pages saved as Favorites by users with access to them could be viewed by other users who do not have the necessary permissions. Now, if a restricted page is requested, the user’s default start page appears. Note that data restrictions, if applicable, were enforced correctly.
Editing the system’s (user account) auto-unlock timeout setting attempted to update the value for each user account across all servers in a dotcom. The unlock time has changed so one value is applied to all user and group accounts regardless of the server from which the user logs on, allowing the system to propagate a single system setting instead.
Some user and group settings fields did not enforce value length limits, causing unintended truncation when saving. All input fields now enforce the field length limit.
Some system and prefetch sessions were checked for inactivity even though these sessions never time out. If a study matching an order arrived after the inactivity timer expired, the auto-correction failed to complete. This has been resolved.
The auto-correction log entry was missing a space, combining text and a study UID value. This has been resolved.
If the user edited the Radiologist field on the report panel and the value is empty or does not match a defined radiologist’s name, an unnecessary exception pops up when the user saves the report. This has been resolved.
If there is no license or there’s an error in the license, the server unintentionally initializes as a media creation server, whose built-in defaults might be different that those of a PACS server. This has been resolved.
After deleting a default worklist label from the list menu, the group or system default list should appear but did not because the list was not refreshed. This has been resolved.
The button controls on some curtain pages failed to close the popup panel, leaving the popup panel
visible after the operation was completed or canceled.
When replicating a study from the consolidation server, the target folder was created but the redirection request failed due to a call to a retired page. This has been resolved.
Login requests from web services calls or when reading location was specified failed to check the lock state of the user account.
Actions assigned to groups whose ID was 20 characters were ignored because the last character was truncated from the identifier saved in the action database table, meaning it didn’t match any registered group when actions ran. This has been resolved.
The recent fix to handle double quotes in patient matching criteria fields introduced a parsing bug when patient matching including initial matching parameters. This has been resolved.
Actions, with the exception of the Notify Action, cannot be assigned to group accounts, but the user interface failed to enforce this restriction. Existing actions assigned to group accounts disabled at first restart. Admins are notified if any Actions are disabled.
Spaces are not permitted in group IDs, but this was not enforced when creating new groups or when importing groups during upgrades. Existing group IDs containing spaces will be modified by replacing the space with an underscore.
Some remaining web pages were not defined to use UTF-8 by default. In this specific case, flat report text containing accented characters was not handled correctly when sent via HL7. This has been resolved.
After moving list management to the database, Action study lists were not sorted, which could result in processing a study multiple times and, less likely, missing a study completely. This has been resolved.
Displaying a list’s properties from the Other Lists page had some formatting issues that truncated the filter’s details. This has been resolved.
When deleting a folder, the system removed the container but failed to check for and remove study references assigned to the folder. If a folder is not empty when deleted, the user is prompted before the study reference is removed. This has been resolved.
When creating media with two or more studies that do not yet exist on the media creation server, the download of one might be delayed. For example, it might need to be retrieved from an archive, or it is still propagating up a dotcom from a child server. The system was not always waiting for all studies to arrive before building the media file. This has been resolved.
If a web services API link could not complete, the response was hard coded to report an authorization failure. Now it prompts the user for credentials.
If prompted to enter user credentials after issuing a web services API link without a valid session ID, a failed first attempt lost the intended API target (page) and the user ended up on an unexpected web page. This has been resolved.
If a field used in the patient matching criteria contained double quotes, the patient folder panel would not open because the system failed to escape the met character. This has been resolved.
UPGRADE NOTICE: This fix does not remove existing system default worklists. If a system default worklist was created as a result of this bug, it must be deleted manually. The factory default worklist was incorrectly saved as the custom system-level default if no system default worklist existed.
Servers configured with a database set up for latin-2, or any character set other than latin-1, mishandled some collation details, resulting in a failure to manage some saved worklists, including deleting them. This has been resolved.
When moving worklists and actions to the database (medsrv-8.0.21), empty action study lists were interpreted as a disabled action. As a result, after the upgrade, the action was disabled. Note that this fix does not restore actions disabled by the bug. These actions must be re-enabled manually.
The database length of group list names failed to account for a character appended by the system software, causing errors when using a group list whose label was exactly 20 characters long. This has been resolved.
After moving saved worklists to the database, worklist actions failed to remove non-matching studies from the managed list of studies, causing the database table to grow large. This has been resolved.
Resetting the auto unlock time setting unintentionally changed the lock period for explicitly-locked accounts, allowing them to be reset by the user. This has been resolved.
Some dependencies were not cleared when a saved worklist filter was deleted or renamed, including removing Actions and updating compound lists. This has been resolved.
The saved worklist delete button was present in the list menu for users without the necessary (Create View) permission. This has been resolved.
The password characteristics were enforced when updating a password but not when creating the user account. This has been resolved.
The hierarchy used to select the data loaded into the patient folder’s view area by default was incorrect. Displaying a final report has precedence over an attachment. This has been resolved.
The application that draws annotations on key images on a report page could fail when applying the annotation. While the image and unaffected annotations appear in the report page, some annotations might be missing. This has been resolved.
Worklists including conditional row colors formed an invalid query request, causing non-matching entries to appear in the results. This has been resolved.
Some secondary capture object references, specifically for attachments, were hardcoded to suppress tagging, yet the thumbnail references followed the viewer’s preference. When the viewer requested tagged references, the inconsistency could cause the viewer to hang. This has been resolved.
An inherited page size limit used when collecting the objects for an ISO file truncated the list, resulting in missing objects on the media. This has been resolved.
An incorrect permission check permitted users with the right to approve a report to open it for editing even when they had no report editing permission, displaying an error warning in the process. This has been resolved.
If a retired database field, Scheduled Order Number, contained data, attachment uploaded to orders would fail. This has been resolved.
The database index has been restored to the study table’s FOLDER field, and a default statistics file has been added.
An issue with the way calls were made to a handler prevented some functions from completing, including the one displaying key images and another hiding the image size selector on a print-friendly report. This has been resolved.
Support for displaying content from third party SR objects on a report page or panel has been ported to v8.
Restrictions have been applied to disable LDAP’s support for password-less login attempts.
Studies with presentation states created by the eRAD viewer encountered an error when the MCS converted those objects to DICOM-compliant PS objects and copied them to the output folder. This has been resolved.
The image tagging solution the viewer uses to request the server reprocess an image object interfered with displaying annotations on key images and presentation states in some versions of the viewer. The solution was to disable tagging unless the viewer version indicates it supports the feature.
When a presentation state object was missing from the processed directory, the web viewer failed to initiate the just-in-time processing and then didn’t handle the missing file, preventing the whole study from loading in the web viewer. This has been resolved.
When saving a worklist filter, the query qualifier was not checked, allowing a user to save a poorly defined or unbounded query filter. This has been resolved.
The system failed to create a log entry when a non-image file (e.g., a document) was uploaded and attached to an order. This has been resolved.
A change to system user names got around a check meant to prevent system users from breaking locks. As a result, some system-initiated commands, such as study split, study merge, report saving and ownership passing, could be invoked multiple times, duplicating data. This has been resolved.
File uploads initiated at a worklist server and redirected to a hub server completed successfully but logged an error when it attempted to parse the command to see if further redirection was necessary. This has been resolved.
The delay and retry task information displayed on the task management page did not match the data in the database because some tasks weren’t removed from the Info Object tree. This has been resolved.
System and group default lists for the user accounts page and logs page were not being applied. This has been resolved.
The Author Observer (report author) name was saved using HTML encoding, which was inconsistent with all other names in the report. This has been resolved.
Access to system worklists are supposed to require Admin permissions but this restriction was not applied, making them visible to all users. This has been resolved.
Applying a saved, default Archive page filter containing more than one filter would not issue the query and no list was presented. Additionally, the system default Archive page filter contained a null filter value, resulting in an error and no list was presented. This has been resolved.
After saving a worklist filter with a text field using “is not empty”, applying the filter and then opening the filter criteria field to edit it, the contents contained an unwanted character that, if not cleared, would be applied when the query was run. This has been resolved.
Worklist filters created in previous versions and updated during the upgrade to PACS Evolution do not contain an explicit setting to show or hide the worklist header. They are supposed to show the header by default, but were not. This has been resolved.
Requests to create DICOM media using the MCS service failed if issued from a worklist consolidation server (a parent to a collection of worklist servers) because the software only collected data from neighboring hub devices. This has been resolved.
If a saved worklist filter results in a query qualifier warning, the resulting list layout ignores the saved filter’s layout and applies the default layout. This has been resolved.
The DICOM toolkit inherits character sets differently when editing and creating objects. When creating a new report object, the default (ASCII) character set was used, causing names such as the reading physician to ignore accented characters. This has been resolved.
The Prefetch and Stop Sending Updates action icons could not be filtered on from the Other Lists page. This has been resolved.
If the worklist filter configuration file was created as a favorite (starred) worklist, it would remain in the dashlet panel after it was purged from the system. This has been resolved.
A change in the way browsers handle iframes loaded from a different server ignored the cookie presented and reported a non-existent or expired session. As a result, loading a report in the web viewer’s report panel displayed an expired session error message instead. This has been resolved.
When attempting to update the study data from the document scanning page, the system attempted to save some retired scanning settings, causing the request to fail. This has been resolved.
Some browsers won’t pass along an access control parameter when redirecting web viewer open requests to a child server. As a result, the web viewer reported an error and would not load the data. This has been resolved.
Attempts to filter the Other Lists table returned no matches because the filter mechanism overhaul completed for v8 had not been applied to the action data. This has been resolved.
Outbound web service messages were sent twice because the event handler was registered twice during startup. This has been resolved.
When the viewer’s patient folder checked for study updates, the result was compared to the wrong data causing a refresh every time. This has been resolved.
The web service command to delete DICOM media files after they have been downloaded failed to pass along the media session ID, causing the request to fail and the data to remain until the system purged it when the timeout expired. This has been resolved.
User-scheduled tasks (from the GUI) resulted in a deadlock condition when checking for new tasks from the unprocessed queue occurred before first checking if the system can start new tasks. This has been resolved.
Support for customizing the default filter type for worklist fields has been added. See Customize Labels Settings
Some DICOM server and study operation settings appeared editable, but weren’t, for admin users who didn’t have the required support rights. This has been resolved.
When exporting a worklist, the system expanded the DICOM enumerated value for sex and then attempted to localize that word to the applied language. The translation effort failed, causing the export error. The DICOM value for sex is included in the exported data without expansion or translation.
When LDAP is not configured, the security settings page hid a field. When the user edited a security setting, the hidden field was checked and since it was empty, an error result was displayed, even though the edit was correctly applied. This has been resolved.
The frequency with which the server attempts to renew its license has changed to avoid creating a processing burden.
Attempting to save a worklist layout did not offer the current user as an option in the list owner menu if the currently applied layout is a system-owned (default) layout. This has been resolved.
The heading on the user account batch edit panel was incorrect. The panel was updated to display the list of all user accounts selected for the batch edit.
The Storage AE and Archive Query AE fields on the settings page could be edited by Admins who didn’t have support rights.
A change in the way browsers handle iframes loaded from a different server ignored the cookie presented and reported a non-existent or expired session. As a result, loading a report from a child server when batch approving on a worklist server failed.
When launching the web viewer without an active user session, the user is prompted for credentials. While the login succeeded and returned a cookie with the necessary session ID, subsequent calls did not use it, causing them to do nothing or repeatedly prompt for credentials. This has been resolved.
If there is no number in the input string, the calculated field’s number() macro is supposed to return ‘0’. Instead, it returned the input string. This has been resolved.
Updates to report printing necessary for supporting wkhtmltopdf failed to include the title value when converting from PDF to postscript. This has been resolved.
Notification actions using the system’s built-in email template failed to generate email messages because two macros used by the template were removed in medsrv-8.0.10. This has been resolved.
The Safari browser does not support wildcard values in the access control origin header. The wildcard value has been replaced with the referrer host value.
Opening multiple studies in the web viewer when web sockets is unavailable, causing the web viewer to downgrade image download to use HTTP, texture blocks were resized when they shouldn’t be and data chunks could override each other causing missing data blocks. This has been resolved.
Some document type settings (default document type, modality and study date) were not applied to the scanning and upload user interfaces when the panel initialized. This has been resolved.
Log entries showing a change in plugin rights failed to identify the original permission setting. This has been resolved.
Some empty date fields, including Scheduled Date, were not assigned the default date, causing a java exception and an empty worklist. Additionally, searching on an empty date value returns all records with no date value rather than all records, as was the case before. This has been resolved.
A change in the WSDL moved the location of a file that was needed when sending orders and reports to web services devices. This has been resolved.
The filter type value in saved worklist filters was dropped when upgrading m8.0.8 systems, causing worklist filters to ignore the filter. This fix does not correct saved filters that have already been converted during an upgrade. This has been resolved.
A parsing error prevented the viewer from displaying the customized list of available speech recognition options if more than one option was included in the configuration file. This has been resolved.
Patient name and other field queries containing an apostrophe (') in the search criteria returned zero matches regardless of the data. This has been resolved.
The query qualification check was not activated when loading a saved worklist. This has been resolved.
The study date value stored in the database's log table and displayed on the log page did not include the time component. This has been resolved.
Unsuccessful requests to add or edit a device did not always notify the user the operation failed. This has been resolved.
Image-type attachments uploaded to an order from a worklist server are supposed to be stored on the hub server. It also changes the order to a study. All other attachment types are supposed to be stored on the worklist server. (They move to the hub server when the image objects arrive.) These attachments were mistakenly stored on a hub server causing a broken study if the images arrived at a different hub server. This has been resolved.
If a web services client creates a new user account set to change the password upon first login, the user was not required to change his/her password. This has been resolved.
When the same objects is resent multiple times and the queues are not empty, taskd might start multiple registration tasks for the same object at the same time. The object was successfully registered but errors were logged and one of the tasks might end up on the retry queue without the ability to complete when rescheduled.
After adding outbound notifications when modifying a study's instance UID (eg, after splitting or merging studies), error handling changed and releasing the lock upon error was unintentionally dropped. This has been resolved.
When exporting annotations saved as a presentation state, the server converts the internal representation of the data to DICOM Presentation State objects. Support for rotated ellipses and freehand ROI graphics was not included and these graphics would not be exported. This has been resolved.
Inserting a segment into a report template from the template editor resulted in a java crash. This has been resolved.
This bug prevented admins from customizing the viewer's patient folder template. This has been resolved.
System unable to support more than 32k users
File system limitations prevented the system from having more than 32K user accounts. This has been resolved.
When a series- or instance-level C-Move request was issued to a non-objectless consolidation (CWL) server, the resulting database query was invalid and failed. This has been resolved.
Web services calls to retrieve study information returned incorrect image and series counts if the number was greater than 15. This has been resolved.
The tool to assign filter criteria to a Q/R device was missing some features: warning about the effects of the filter; access to all database fields; and logging edits to a filter. Some presentation inconsistencies were also corrected.
When a spatial registration object is registered for a study currently open in an active viewer session, the server notifies the viewer so it can retrieve the new object.
Internet Explorer issues an incorrect event when dragging a scroll bar in a dropdown box (in this case, the canned report selection list), causing the dropdown list to close before selecting an item. This has been resolved.
Scheduled Procedure Step ID values defined in an order creation message failed to show up in the database (and worklist). This has been resolved.
The study edit page failed to list values for fields in the DICOM object but not stored in the database. This has been resolved.
The study forward page would take a long time to load when the system contained many (tens of thousands) user accounts. This has been resolved.
The edit report page, launched from the patient folder, would take a long time to load when the system contained many (tens of thousands) user accounts. This has been resolved.
The report approval page would take a long time to load when the system contained many (tens of thousands) user accounts. This has been resolved.
The Message dashlet's recipient list and the dashlet's configuration page would take a long time to load when the system contained many (tens of thousands) user accounts. This has been resolved.
Auto-retrieving priors from the archive to the hub server failed if the study was registered on a child server. This has been resolved.
Locked studies would not unlock after the lock period expired if the user's session had timed out first. This has been resolved.
New user accounts using IDs of deleted user accounts would be notified of multi-level authentication requirements even when the feature was disabled. This has been resolved.
Displaying the report approval web page was very slow on systems with a large number of user accounts due to an inefficient database query. This has been resolved.
The option to set a report to Final was unavailable if the user had permission (the Approve right) to approve a report. This has been resolved.
Objects that arrive at a server after the post process or compress data actions have been applied to the study are automatically processed.
If an archive was an independent eRAD PACS system, the retrieve and forward tools on the Archive page failed because the archive expected a user session ID from it's own dotcom. This has been resolved.
Web services requests to create DICOM media performed an invalid check of the requested compression and media type parameters, thereby ignoring the requested settings and always uncompressing the data. This has been resolved.
Displaying a report of external origin using a template that does not contain an areagroup for handling external reports resulted in a crash. This has been resolved.
Secondary capture and presentation state objects sent to the worklist server after being created in a viewer session were propagated to their owner device but remained on the worklist server. This has been resolved.
When the viewer sends new objects to the server when it also sends a report, the study's State Changed value was updated to indicate the study changed. This has been resolved.
The viewer's patient folder study list was misaligned due to a position calculation error when collecting the data, and neglecting to account for the separator spaces in the connector bar. This has been resolved.
If the patient folder is configured to automatically load data into the view area, and the area is already populated when the patient folder is opened, the background refresh changes the data already displayed in the view area. This has been resolved.
Studies that are no longer included in the filtered worklist were checked for updates when the page refreshed, causing excessive log entries because no lock state existed.
When using Internet Explorer 11, the Rights section of the user account edit page extended outside the boundaries of the browser window, with no scroll bar to reposition the options. This has been resolved.
Uploading a non-image attachment to an order from a worklist server didn't push the data to the selected hub server. As a result, the data was not visible on the Tech View page or in the patient folder.
Web services commands issued to a server and forwarded to an owner device for execution failed the session validation if the web service user was not the registered default user for the device issuing the call. This has been resolved.
Correction messages that propagate up a dotcom to the server that is configured to send a notice to a web services client (eg, to a RIS) before the image objects arrive and get registered will fail, but the task did not get added to the retry queue. As a result, the client never received the correction notification. This has been resolved.
Workstation prefetch requests resulting from a Forward Action didn't include the instruction to expand the list and therefore failed to include relevant prior studies. This has been resolved.
A recent change to handling date and time filters affected the birth date field, causing the exact match needed to grant access to restricted studies to fail. This has been resolved.
When opening a PDF attachment from the Technologist View page in a multilevel dotcom, a java dump appeared on the screen because the redirection failed to include the session ID. This has been resolved.
When a presentation state object specified an annotation on an image that was not present in the data set, the web viewer would fail to load the study or report an error. This has been resolved.
The units for the media export download timeout setting (on the Server Settings/Study Operation page) have changed from days to hours. Existing settings are automatically adjusted.