Nuance Healthcare
What's new | Improvements | Solved issues | Known issues | System requirements | Product life cycle | Release history
Application vendors providing .NET-based applications can now enable Full Text Control support for their custom or otherwise unsupported text controls by integrating a new set of APIs in the Dragon Medical One .NET Text Control SDK. For more information, see the Dragon Medical One .NET Integration SDK Guide.
Improved behavior of Dragon Medical One in cases when back-end services become temporarily unavailable and improved communication with the end user when a requested operation cannot be completed due to the back-end service unavailability. The auto-text and step-by-step command managers will now properly communicate failures to the end user.
Improved Dragon Medical Advisor functionality by considering meta data of the documentation created by the end user for the Allscripts SCM, Meditech Expanse and Epic Hyperspace 2018 EHRs.
The runtime memory footprint of the Dragon Medical One interoperability components loaded into Epic has been improved. Components that are no longer actively used by Dragon Medical One will be unloaded more aggressively; the memory consumption of the Epic process will no longer increase.
Addressed an issue that caused Dragon Medical One to switch to microphone off from recording or standby mode after having documented into multiple documents or when closing the Options dialog box. [SOD-18889]
Addressed an issue that sometimes caused Dragon Medical One to terminate after opening the Dictation Box. [SOD-17561]
Addressed an issue that led to missing words from the recognition results and had impact on the speech recognition accuracy when documenting on computers that were connected to a power supply that was not externally grounded (causing magnetic interference and reducing the quality of the recorded audio stream). [SOD-17542]
Addressed an issue that caused the Dragon Medical One application UI to become temporarily unresponsive when recording was started while the window focus was in some Dragon Medical One application dialog boxes. [SOD-17503]
Addressed an issue that caused the text to be duplicated after selecting it manually and attempting to correct it via voice. [SOD-13386]
Addressed an issue that caused the text, which could not be inserted into Cerner Millennium, to not be inserted in the Dictation Box either. [SOD-21005]
Addressed an issue that could lead to incorrect insertion position while documenting into Cerner mPages. [SOD-20454]
Addressed issues that caused the Dictation Box to open when documenting into Cerner mPages. [SOD-19333, SOD-17184]
Addressed an issue that could lead to having to restart Cerner PowerNote to be able to document. [SOD-17483]
Addressed an issue that prevented the end user from selecting text via mouse. [SOD-16312]
Addressed an issue that prevented the end user from selecting text from the right to the left via mouse. [SOD-12942]
Addressed an issue that could lead to using the wrong patient context meta data when generating advice for documentation created in Cerner Millennium. [SOD-22587]
Addressed an issue that prevented patient context meta data from being correctly retrieved for documentation created in Athena. [SOD-16837]
Addressed an issue that caused some Dragon Medical Advisor-related functionality to be active, potentially interfering with the target EHR while Dragon Medical Advisor should have been disabled. [SOD-13644]
Addressed issues that could lead to performance issues when logging troubleshooting data to the local file system. The configuration file template was updated to restore the default logging level back to ERROR level logging. For more information on how to customize log levels, see the 'Setting the logging level' topic of the Dragon Medical One Installation and Administration Guide. [SOD-18896]
When roaming between endpoints in virtual environments while Dragon Medical One is in standby mode, the application may not properly stop recording or may become unresponsive when reconnecting to the virtual server session. If you encounter these issues in your workflow, stop recording before disconnecting from the virtual server session.
When waking up Dragon Medical One from standby mode, make sure to pause briefly after saying the wake-up phrase and then continue documenting.
When the Grundig virtual server device drivers are deployed to a virtual RDS server, Dragon Medical One using a Grundig device may become unresponsive when reconnecting to a session.
For more information on supported infrastructure and text control support, see the Dragon Medical One Installation and Administration Guide.
Windows Server 2008 R2
Citrix XenApp 6.5
Citrix Receiver < 4.3
Note: Audio extensions are backwards compatible up to a year. However to take advantage of new functionality, we recommend you upgrade.
| Version | Status | End of support | End of life |
|---|---|---|---|
| Dragon Medical One 3.4 | End of support | 01 Jan 2019 | 01 Oct 2019 |
| Dragon Medical One 3.5 | End of Support | 01 Mar 2019 | 01 Oct 2019 |
| Dragon Medical One 3.6 | Supported | 01 Jul 2019 | 01 Dec 2019 |
| Dragon Medical One 4.0 | Supported | 01 Mar 2020 | 01 Jun 2020 |
| Dragon Medical One 5.0 | Supported | 01 May 2021 |
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.
Dragon Medical One 4.0 Service Release 5
Dragon Medical One 4.0 Service Release 4
Dragon Medical One 4.0 Service Release 3
Dragon Medical One 4.0 Service Release 2