Nuance Healthcare
Overview | What's new | Improvements | Solved issues | System requirements | Product life cycle | Release history
Dragon Medical One 3.6 includes stability improvements for existing workflows and new functionality improving Dragon Medical One's interoperability, specifically for applications and text controls that are not enabled for speech input by default, allowing end users to dictate into these applications using a reduced feature set.
Administrators can now configure Dragon Medical One to use an alternative input method (Basic Text Control) to allow dictation into text controls that are not enabled for speech input by default. This enables end users to dictate directly into the application instead of the dictation box, but with a reduced feature set. When using basic text controls, end users cannot use correction or navigation functionality and text is inserted at the active insertion position without proper text formatting applied.
For more information on enabling basic text controls for specific applications, see the Dragon Medical One Installation and Administration Guide.
The preferred documentation workflow for unsupported text controls is still via the dictation box; this provides Dragon Medical One's full feature set.
Administrators can now configure Dragon Medical One to automatically open the Dragon Medical Advisor window once per day or once per logon session the first time Dragon Medical Advisor generates advice via auto-processing. Administrators can also restrict this behavior to a specific number of days. For more information, see the Dragon Medical One Installation and Administration Guide.
In addition to user-level step-by-step commands, end users can now run shared (organization-, site- and group-level) step-by-step commands via a hotkey or microphone button. To look up and assign shared step-by-step commands, end users can switch the scope of the search window from "user level" to "shared" during the assignment process.
Compared to previous versions of Dragon Medical One, the accept defaults voice command now completes faster for applications hosted in Internet Explorer and for applications using RichText, TX TextControl or TER text controls.
Applications utilizing WPF TextBox controls are now supported without the need to install the Dragon Medical One TSF plugin. If your end users have issues documenting into WPF TextBox class text controls in your application, install the Dragon Medical One TSF plugin. For more information, see the Dragon Medical One Installation and Administration Guide.
Addressed an issue that caused the dictation box to open when attempting to document into a supported text control after having anchored the voice focus to a text control that was closed or destroyed. [SOD-8300]
Addressed an issue that caused a notification message to appear if pairing between Dragon Medical One and the Nuance PowerMic Mobile app was lost during recording; the application will now no longer display a notification message in this case. [SOD-11078]
Addressed an issue that prevented the end user help from opening. [SOD-11261]
Addressed an issue that caused Nuance PowerMic device buttons to stop working after upgrading Dragon Medical One from version 3.5 SR1 to a newer version using the MSI installation package. [SOD-11266]
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.0 | End of life | 31 Mar 2017 | 30 Jun 2017 |
| Dragon Medical One 3.1 | End of life | 14 Jul 2017 | 14 Oct 2017 |
| Dragon Medical One 3.2 | End of support | 20 Oct 2017 | 20 Jan 2018 |
| Dragon Medical One 3.3 | Supported | 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 | 14 Nov 2018 | 14 Feb 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 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 and Nuance's end-of-life policy. This means that issues that are a combination of the vendor’s component and the Nuance solution cannot be supported.