Dragon Medical One 4.0 Hotfix 1 addresses an issue that prevented Dictation Box text transfers from a local Dragon Medical One instance to a published application.
Transferring text from the Dictation Box now works correctly from a locally-deployed Dragon Medical One instance into an application published from a virtual server session. [SOD-12622]
Have a Dragon Medical One instance running locally on the end point and an application published from a virtual server session.
Open the Dictation Box.
Say the patient complains of chest pain.
Focus the published application.
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.1||End of life||14 Jul 2017||14 Oct 2017|
|Dragon Medical One 3.2||End of life||20 Oct 2017||20 Jan 2018|
|Dragon Medical One 3.3||End of support||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|
|Dragon Medical One 4.0||Supported||13 Feb 2019||13 May 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.
Dragon Medical One 4.0
Dragon Medical One 3.6