Nuance Healthcare
What's new | Improvements | Solved issues | System requirements | Product life cycle | Release history
Dragon Medical One can be configured to automatically log an end user off if they have not interacted with the application for a specified period of time. By default, an end user is never logged off automatically. To configure timeout for end users, add the AutoLogOffTimeout
setting to the configuration file; the timeout is specified in minutes and the value range is 5 to 120 minutes.
<setting name="AutoLogOffTimeout" serializeAs="String"
<value>TIMEOUT_IN_MINUTES</value>
</setting>
Addressed an issue that caused device button events to be ignored when the button focus was switched from a locally-deployed instance of Dragon Medical One to an application published via Citrix Receiver. Device buttons are now handled properly when the focus is switched back to a locally-deployed application. [SOD-13508]
Addressed issues that caused the Dictation Box to be displayed at the wrong position on the screen when hiding and showing the DragonBar. [SOD-12442, SOD-12757]
Addressed an issue that caused the correction menu to be displayed at the wrong position when documenting into applications hosted in Microsoft Internet Explorer. [SOD-12645]
Addressed an issue that prevented administrators from configuring hotkey combinations that included Shift as the only modifier, even if setting the same hotkey combinations via the Options dialog box worked. [SOD-11984]
Addressed an issue that caused Dragon Medical One to respond with significant delay when attempting to start recording or interacting with an EHR in virtual server environments which hosted a large number of active users and running processes on a specific virtual server instance. [SOD-13307]
Addressed an issue that caused Dragon Medical One to have increased impact on CPU usage in virtual server environments which hosted a large number of active users and running processes on a specific virtual server instance when deploying Dragon Medical One with support for Dragon Medical Advisor. [SOD-13607]
Addressed an issue that could cause Dragon Medical One to terminate when documenting into EHRs running as 64-bit processes. [SOD-12259]
Addressed an issue that required end users to manually place focus back into an unsupported application text field to transfer the content dictated in this unsupported application to the Dictation Box. This issue led to documentation being finalized in the Dictation Box if the end user was actively correcting in the Dictation Box (by applying manual selection or text changes). [SOD-13564]
Addressed an issue that could cause the target application to terminate when documenting into TE Edit Control text controls and having more than 2000 characters in the text control. [SOD-11114]
Addressed an issue that could cause the target application to terminate when documenting into text controls hosted in Microsoft Internet Explorer. [SOD-13694]
For more information on supported infrastructure and text control support, see the Dragon Medical One Installation and Administration Guide.
Version | Status | End of support | End of life |
---|---|---|---|
Dragon Medical One 3.1 | End of life | 14 Jul 2017 | 14 Oct 2017 |
Dragon Medical One 3.2 | End of life | 20 Oct 2017 | 20 Jan 2018 |
Dragon Medical One 3.3 | End of support | 17 Jan 2018 | 17 Apr 2018 |
Dragon Medical One 3.4 | Supported | 11 Apr 2018 | 11 Jul 2018 |
Dragon Medical One 3.5 | Supported | 15 Aug 2018 | 15 Nov 2018 |
Dragon Medical One 3.6 | Supported | 16 Nov 2018 | 16 Feb 2019 |
Dragon Medical One 4.0 | Supported | 13 Feb 2019 | 13 May 2019 |
Support for third-party environments is only valid as long as they are supported by the corresponding vendor and might be subject to other restrictions. Please contact Nuance Technical Support for details. For more information, see the documentation delivered with the third party product and supporting Nuance documentation.
When standard support by the vendor has stopped, Nuance will continue support if an issue is specific to the Nuance solution, within the limitations of the vendor’s standard end-of-life and Nuance's policy. This means that issues that are a combination of the vendor’s component and the Nuance solution cannot be supported.