Nuance Healthcare
Release overview | Important information | What's new | Improvements | Solved issues | Known issues | System requirements
Dragon Medical One 2022.1 is the first Dragon Medical One GA release based on the improved architecture. It provides better user experience, broader platform support and future EHR support. Target clients include those who use Dragon Medical One with Epic or Cerner EHRs; it is compatible with their next generation offerings, specifically Epic Hyperdrive/Cerner WebView2, and their current offerings such as Epic Hyperspace/Cerner Millennium. For clients who use EHRs other than Epic and Cerner, we will continue the current Dragon Medical One 2021.4 service releases to provide the best support.
When deploying Dragon Medical One 2022.1, make sure you use the Dragon Medical One 2022.1 configuration file template; failing to update the configuration file template for your deployments might result in functionality not working properly.
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
Starting with Citrix Virtual Apps and Desktops 2109, the 'Virtual channel allow list' policy setting will be enabled by default.
This means that Nuance custom virtual channels will no longer work with the default configuration. The policy setting for virtual channels must be disabled (preferred), to allow all virtual channels again, or configured to allow Nuance virtual channels. For more information, contact Nuance Technical Support.
Running the MSI installer will create a new entry called 'Dragon Medical One 2022' in Apps & features, side-by-side to any older versions of Dragon Medical One. Automatically upgrading from an older version is currently not supported.
Dragon Medical One now supports dictation into applications hosted in Microsoft Edge. To enable support for applications hosted in Microsoft Edge, deploy the Dragon Medical One Web Extension to your Microsoft Edge clients via the Microsoft Edge Add-ons page.
While Dragon Medical One 2022.1 provides documentation support for Microsoft Edge, some known issues and limitations are present in the current release, including the following:
The undo and redo voice commands do not work for dictated text.
Formatting voice commands are not supported.
Dragon Medical Advisor use cases are not supported in applications based on Microsoft Edge.
Dragon Medical One now provides support for the Cerner CoPath 2019 application, including protected sections in Cerner CoPath 2019 documents.
Dragon Medical One now supports deployment to end points based on Microsoft Windows 11.
Dragon Medical One now provides support for the Nuance PowerMic 4 microphone device, including Nuance PowerMic 4 coherence mode. For more information, see https://nuance.com/powermic.
End users can now select the user interface and speech recognition language during logon.
Dragon Medical One now provides support for the rapid navigation feature in Cerner, Epic Hyperspace and the Dictation Box. Please note that rapid navigation is not yet supported for other applications.
WebView2 support in Cerner Millennium is now available via MSI installation.
Microsoft Edge WebView2 support in Cerner Millennium has been improved; the Citrix session now closes properly after all the applications have been closed.
The following known issues are present in the current release:
When dictating in the Cerner WebView2 application and saying new line or new paragraph, the voice command is recognized but the cursor position is not always updated as expected.
When the port for the communication hub is not available, the hub launcher service does not start and the dictated text is written to the Dictation Box instead of the WebView2 control.
When WebView2 support in Cerner Millennium is enabled, two more log files (SoD.CommunicationHub_yyyymmdd.log and SoD.HubLauncher_yyyymmdd.log) are generated when using Dragon Medical One with WebView2 controls in Cerner Millennium.
The default log level is DEBUG.
In a virtual desktop/application environment, we recommend configuring a writable folder as the log file location:
Specify the location of the communication hub log file in the path setting of the appsettings.json file.
Specify the location of the Hub Launcher log file in the path setting of the launcherappsettings.json file.
Dragon correction menu support has been improved; the correction menu now closes properly when the cursor focus is moved to another edit control.
Addressed an issue that caused Dragon Medical One to sometimes go into standby mode after having trained a word, without saying go to sleep. [SOD-39961]
Addressed an issue that caused two new auto-texts to be created when saying make that an auto-text or create auto-text. [SOD-3951, SOD-39384]
Addressed an issue that caused configurations in the 'Text Input' pane of the Dragon Medical One 'Options' dialog box to revert back to the default settings after logging out of Dragon Medical One. [SOD-38919]
Addressed issues that caused Dictation Box use cases (opening the Dictation Box, resizing the Dictation Box) to stop working after having maximized or closed the Dictation Box. [SOD-39383, SOD-39066]
Addressed an issue that caused text inserted into the Dictation Box via the 'Insert selected text from the target application' functionality to be inserted at the end of the text in the Dictation Box instead of at the current insertion position. [SOD-39581]
Addressed an issue that caused Dragon Medical Virtual Assistant Text-to-Speech to miss speaking some parts of phrases and that prevented Dragon Medical One from properly transitioning back to standby mode. [SOD-39363, SOD-36527]
Addressed issues that caused Dragon Medical One to sometimes terminate while logging off or exiting from Dragon Medical One. [SOD-38904, SOD-38781, SOD-38595, SOD-38594, SOD-36432]
Addressed an issue that prevented end users from continuing dictation in virtualized environments after having locked and unlocked their client end point. [SOD-39926]
Addressed an issue that caused Dragon Medical One to sometimes terminate when disconnecting and reconnecting to a virtual server session when using Nuance PowerMic Mobile as input device. [SOD-39500]
Addressed an issue that caused the Dictation Box to open when opening the personalization and help window or the Dragon Medical Advisor window and continuing dictation. [SOD-38954 , SOD-33810, SOD-39525]
Addressed an issue that caused Dragon Medical One to terminate when clicking 'Record' on the DragonBar while having the microphone's record button configured to "Microphone On/off" and using Nuance PowerMic II or Nuance PowerMic III as input device in virtual server environments. [SOD-36423]
Addressed an issue that prevented end users from selecting all text in the Dictation Box by saying select all. [SOD-36436]
Addressed an issue that inserted square brackets into the auto-text body when creating an auto-text from the current selection when the current selection included 'new line' and 'new paragraph' characters. [SOD-36455]
Addressed an issue that prevented end users from logging on to Dragon Medical One when using Nuance PowerMic Mobile after having previously logged off. [SOD-40528]
Addressed an issue that prevented end users from formatting text that was previously dictated in Cerner applications. [SOD-38079]
Addressed an issue that caused Epic Hyperspace to terminate when trying to delete a protected SmartLink by saying delete that. [SOD-37574]
Switching the microphone from the DragonBar menu
Microsoft Windows voice commands to copy and paste text
Fields that are supported for dictation at the cursor but requiring key press simulation for full functionality
Section 508 compliance
Text control mapping
Basic Text Control with URL support
Dragon Medical Virtual Assistant with PowerMic Mobile support
Dragon Medical One Java Integration SDK
Dragon Medical One .NET Integration SDK
WPF
TX30
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 VMware Horizon 2111 (Version 8.4) release.
When working with a Philips SpeechMike or Nuance PowerMic 4 device, the screen saver is not displayed after the configured period of inactivity when recording is in standby mode.
To disable this behavior, press and hold the left mouse and touchpad buttons on the recording device for five seconds. When the firmware setting has been changed successfully, the device provides visual and audio feedback. This setting is stored on the device and needs to be changed individually on each device.
When dictating into a supported application and saying what can I say, the personalization and help window is sometimes displayed larger than expected, occupying the whole screen or more.
When deactivating the 'Start Dragon in standby mode' option but leaving the 'Enable wake word feature' option activated in the 'General' pane of the 'Options' dialog box, Dragon Medical One still starts in standby mode the next time it is opened.
When configuring a hotkey for the 'accept defaults' action in the SoD.DefaultOptions section of the Dragon Medical One configuration file, using the 'Hotkeys.AcceptDefaults' setting identifier, the defined value is not displayed in the 'Hotkeys' pane of the 'Options' dialog box.
On a virtual machine, when configuring the 'General.EnableHandsFree' and 'General.StartInStandbyMode' settings in the SoD.DefaultOptions section of the Dragon Medical One configuration file to 'True', these settings are not reflected in the 'General' pane of the 'Options' dialog box.
When working in unsupported applications with Basic Text Control enabled, the microphone icon is sometimes not updated to indicate Full Text Control when switching to a supported application.
When adding new auto-texts or step-by-step commands, the related voice commands are not available until the user logs off and on again.
When having the Dictation Box open and with the 'Anchor the speech focus when recording is started' option enabled in the 'General' pane of the 'Options' dialog box, putting the cursor into a supported text control and starting recording will not close the Dictation Box on the first attempt and the Dragon Medical One user interface will reflect the change of the recording status only with a delay of several seconds.
When dictating in the Dictation Box, any selected formatting options (for example 'Bold') will not be applied to the first dictated phrase but only to subsequent ones.
When dictating in Cerner PowerNote with TX25 controls, patient context information will not be displayed for dictated text.
When dictating in Epic Hyperspace and switching between fields, the dictated text is always inserted in the first field.
When dictating with the dictation anchored to Epic Hyperspace and closing the application, Dragon Medical One sometimes becomes unresponsive.
For more information on supported infrastructure and text control support, see the Dragon Medical One Installation and Administration Guide.
Operating systems:
Microsoft Windows 8.1
Microsoft Windows 10
Microsoft Windows 11
Microsoft Windows Server 2012 R2
Microsoft Windows Server 2016
Microsoft Windows Server 2019
Runtime:
Microsoft .NET 4.7.2
Microsoft WebView2
Citrix:
Citrix XenApp and 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.121.2132
Nuance PowerMic 121.4.121.2132
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):
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.