Nuance Healthcare
Important information | What's new | Improvements | Solved issues | Known issues | System requirements | Product life cycle | Release history
Dragon Medical One now uses Microsoft Edge WebView2 to display richer content with improved usability in the Dragon Medical One personalization and help window. To support this improvement, you must deploy the Microsoft Edge WebView2 runtime component to machines that host Dragon Medical One. Failing to do so will not impact the core functionality of Dragon Medical One but will potentially impact end users interacting with content displayed in the Dragon Medical One personalization and help window. To deploy Microsoft Edge WebView2 to machines hosting Dragon Medical One, install the Microsoft Edge WebView2 Evergreen Standalone component; for more information, see Webview2 - Microsoft Edge Developer.
Currently, some Citrix environments exhibit issues that can cause the Microsoft Edge WebView2 runtime process to fail working as expected, leading to the Dragon Medical One personalization and help window not displaying properly, and to sometimes terminate with a message visible to end users. As a workaround, you can apply a configuration change to Citrix to disable the Citrix Special Folder Redirection feature (SfrHook) for the Microsoft Edge WebView2 runtime process. To do so, add the following registry keys to your Citrix environment configuration:
[HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\CtxHook\AppInit_DLLs\SfrHook\msedgewebview2.exe]
[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Citrix\CtxHook\AppInit_DLLs\SfrHook\msedgewebview2.exe]
For Citrix documentation on the registry keys, see: How to Disable Citrix API Hooks on a Per-application Basis
Configuration of 'PressHotkey' actions in the configuration file has been consolidated with the configuration of these actions on the Dragon Medical One UI. To configure hotkeys in the configuration file, they must be specified using the same key press sequence as if they were typed on the keyboard.
To verify whether your configuration file requires an update, open the SoD.exe.config file, search for 'PressHotkey' and review the hotkey configured. If the hotkey requires a combination of keys pressed with a modifier key, such as 'Shift', 'Ctrl' or 'Alt', make sure that the configuration is stating the full key press sequence including modifier keys.
For example, to configure a microphone button to press the '!' character on an English US keyboard, the hotkey must be specified as 'Shift+1' in the configuration file:
<setting name="Microphone.FastForward" serializeAs="String" isLocked="False">
<value>PressHotkey(Shift+1)</value>
</setting>
Dragon Medical One now requires Microsoft .NET Framework version 4.7.2 or higher. Machines that do not have this version installed will not be able to start Dragon Medical One. The Dragon Medical One MSI installer will verify that .NET Framework 4.7.2 is installed on the machine prior to installation and will abort if the correct version of the .NET Framework is not installed. Please make sure that your environment is updated.
Starting with Citrix Virtual Apps and Desktops 2109, the 'Virtual channel allow list' policy setting will be enabled by default. This means that custom/third-party virtual channels will no longer work with the default configuration.
The following options are available:
Disable the 'Virtual channel allow list' policy setting to allow all virtual channels again.
Add the Nuance virtual channels to the allow list; for more information, see the Citrix documentation.
For more information, contact Nuance Technical Support.
End users can now document at the cursor into Cerner MPages Workspace.
Dragon Medical One has improved reliability when executing steps in Epic Hyperspace Web to ensure synchronization with the EHR. The improvement is enabled for Epic Hyperspace Aug 21 and higher (a Hyperspace SU is available for Aug 20 and higher; please contact Epic TS and reference SLG 5923141). Previously, the Dictation Box opened or step-by-step commands required additional wait time to work around synchronization issues. No user change is required to benefit from this feature.
End users can now reset their Dragon Medical One password and no longer need to contact their administrator to change it in the Nuance Management Center (NMC). Note that end users can only reset their password from within Dragon Medical One if Dragon Medical One is configured to use the native authentication method and an email address is registered for the end user in NMC.
End users can now document at the cursor into Cerner Millennium rich text editors based on TX TextControl X19 for .NET available in Millennium v. 2018.10 and above.
End users can now use shorter and more direct voice commands to manage the speech focus. The primary anchoring voice commands have changed from anchor speech focus and release speech focus to anchor dictation and release dictation, respectively.
Administrators can now configure Basic Text Control for applications hosted in Google Chrome. Basic Text Control can now be enabled for specific URLs in Google Chrome; once enabled for a URL, Basic Text Control will override natively built-in support for dictation at the cursor for all HTML elements for the specific URL. For more information on how to configure Basic Text Control, see the Dragon Medical One Installation and Administration Guide.
Addressed an issue that caused text transfer from the Dictation Box to the target application, when using the 'Simulate keystrokes' transfer option, to take longer than expected. Text is now transferred twice as fast as in previous versions. [DMOCE-846]
Addressed an issue that caused Dragon Medical One to fall back to the 'Microphone off' recording state when disconnecting and reconnecting to a Citrix session while the recording state was 'Standby' in environments where Citrix native audio is used instead of deploying the Nuance Virtual Extensions. Dragon Medical One will now maintain the 'Standby' state when reconnecting in those scenarios. [SOD-33216]
Addressed an issue that could lead to end users updating from Dragon Medical One versions older than 2021.2 to not being able to log on to Dragon Medical One 2021.2 or later when having configured a 'PressHotkey' step for a microphone button that intends to press a special character like '.' or ';'. [SOD-33743]
Addressed an issue that led to an error message when attempting to transfer text from the Dictation Box to the target application after having opened and closed the personalization and help window and not having explicitly moved the focus to the target application again. [SOD-33734]
Addressed an issue that led to the Dictation Box opening when attempting to dictate into the target application after having opened and closed the personalization and help window and not having explicitly moved the focus to the target application again. [SOD-33733]
Addressed an issue that triggered the 'Apply All' button when creating a new auto-text and pressing the 'Enter' key to enter a new line in the auto-text content field. It is now possible to type new lines in the auto-text content again. [DMOCE-1204]
Addressed an issue that could lead to Epic Hyperspace displaying an error message, indicating that the EDManagerSelector component is not responding. [DMOCE-1001]
Addressed an issue that could lead to patient context meta information not properly displaying when documenting into Epic Hyperspace. [SOD-34428]
Addressed an issue that led to Dragon Medical One terminating because of an 'out of memory' exception after having documented into applications, requesting advice and continuing to work for extended periods of time in the same document. The memory leak was addressed and Dragon Medical One will no longer terminate in those scenarios. [DMOCE-1082]
When the Grundig virtual server device drivers are deployed to a virtual server environment and you encounter issues with device support, install the latest version of the Grundig device drivers.
When switching microphones via the DragonBar menu while Dragon Medical One is in standby mode, Dragon Medical One cannot be woken up using the wake word until the microphone has been activated manually first.
When having Nuance PowerMic Mobile selected as input device and repeatedly logging off and on again to Dragon Medical One, Dragon Medical One might terminate unexpectedly. After Dragon Medical One has terminated, the end user is able to log on again within a few seconds.
When having VMware Horizon Agent 8 installed, Dragon Medical One might not start again after the application has been closed. The issue has been confirmed by VMware and is expected to be fixed with the next Horizon Agent 8.4 release.
When using voice commands to cut/copy/paste text while having the voice focus anchored to a text control, the application hosting that text control is brought to the foreground and focused.
For more information on supported infrastructure and text controls, see the Dragon Medical One Installation and Administration Guide.
Operating systems:
Microsoft Windows 8.1
Microsoft Windows 10
Microsoft Windows Server 2012 R2
Microsoft Windows Server 2016
Microsoft Windows Server 2019
Runtime: Microsoft WebView2 (Evergreen)
Citrix:
Citrix XenApp & XenDesktop 7.15 or higher
Citrix Virtual Apps and Desktops 1808 or higher
Citrix Workspace app 1912 or higher
VMware Horizon View 7:
VMware Horizon View Agent 7.6 or higher
VMware Horizon View Client 4.9 or higher
Virtual server operating systems:
Microsoft Windows Server 2012 R2
Microsoft Windows Server 2016
Microsoft Windows Server 2019
Runtime:
Microsoft .NET 4.7.2
Nuance Virtual Extensions 121.4.136.2138
Nuance PowerMic 121.4.136.2138
Note: Audio extensions are backwards compatible up to a year. However, to take advantage of new functionality, we recommend you upgrade.
If your environment does not meet the minimum requirements outlined, Nuance's ability to assist may be limited. This means that most functionality questions continue to be addressed, but if a bug is suspected or you are running into an issue that requires a technical investigation beyond known issues and fixes, we will recommend that you upgrade to the latest supported version. The following products fall into this best-effort support framework (this list is not comprehensive):
| Version | Status | End of support | End of life |
|---|---|---|---|
| Dragon Medical One 3.4 | End of life | January 01, 2019 | October 01, 2019 |
| Dragon Medical One 3.5 | End of life | March 01, 2019 | October 01, 2019 |
| Dragon Medical One 3.6 | End of life | July 01, 2019 | December 01, 2019 |
| Dragon Medical One 4.0 | End of life | March 01, 2020 | October 01, 2020 |
| Dragon Medical One 5.0 | End of support | May 01, 2021 | May 01, 2022 |
| Dragon Medical One 2020.1 | Supported | October 01, 2021 | June 01, 2022 |
| Dragon Medical One 2020.2 | Supported | March 01, 2022 | June 01, 2022 |
| Dragon Medical One 2020.4 | Supported | June 01, 2022 | September 01, 2022 |
| Dragon Medical One 2021.1 | Supported | October 01, 2022 | January 01, 2023 |
| Dragon Medical One 2021.2 | Supported | October 01, 2022 | January 01, 2023 |
| Dragon Medical One 2021.4 | Supported | December 01, 2022 | March 01, 2023 |
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 2021.1 Service Release 1
Dragon Medical One 2020.4 Hotfix 2
Dragon Medical One 2020.2 Service Release 1