Nuance Healthcare

Dragon Medical One Desktop Application 5.0 Service Release 1

Release notes, 19.2.5246.1926

What's new | Improvements | Solved issues | Known issues | System requirements | Product life cycle | Release history

What's new

New functionality for application providers: Microsoft .NET Text Control SDK

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.


Improvements for end users


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.

Dragon Medical Advisor

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.

Improvements for application providers

Runtime memory consumption for Epic

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.

Solved issues


Application support

Cerner Millennium

Dragon Medical Advisor

Troubleshooting data

Known issues

Standby mode

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.

Grundig device button support

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.

System requirements

For more information on supported infrastructure and text control support, see the Dragon Medical One Installation and Administration Guide.

System requirements

Virtualized environments

Product life cycle

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  

Third-party environments

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.

Release history

Dragon Medical One 5.0

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

Dragon Medical One 4.0 Service Release 1

Dragon Medical One 4.0 Hotfix 1

Dragon Medical One 4.0

Dragon Medical One 3.6