Dragon Medical 360 Network Edition. Version 1.0 Service Pack 6. Release Notes

Transcription

1 Dragon Medical 360 Network Edition Version 1.0 Service Pack 6 Release Notes

2 Copyright Copyright Nuance Communications, Inc. All rights reserved. Nuance, ScanSoft, the Nuance logo, the Dragon logo, Dragon, DragonBar, NaturallySpeaking, NaturallyMobile, RealSpeak, Nothing But Speech (NBS), Natural Language Technology, Select-and-Say, MouseGrid, and Vocabulary Editor are registered trademarks or trademarks of Nuance Communications, Inc. in the United States or other countries. All other names and trademarks referenced herein are trademarks of Nuance Communications or their respective owners. Designations used by third-party manufacturers and sellers to distinguish their products may be claimed as trademarks by those thirdparties L /26/2014

3 Contents What's new in Dragon Medical 360 Network Edition 1.0 SP6 1 Overview of system requirements for DM360 Network Edition, version 1.0 SP6 1 About DM360 Network Edition Logging and Protected Health Information 2 Dragon Medical 360 Network Edition and Citrix 2 Known issues and bug fixes 2 Installing and upgrading to Dragon Medical 360 Network Edition, 1.0 SP6 3 Upgrade Installer updates 3 When to use the Upgrade Installer: 3 Windows XP Support 4 Known s and fixes in Dragon Medical 360 Network Edition 5 Known s and fixes in Dragon Medical 360 Network Edition, 1.0 Service Pack 6 5 Product build numbers 10 DM360 Network Edition Version 2.x Releases 10 DM360 Network Edition Version 1.x Releases 10 How to find the build number of a DM360 Network Edition component 12 iii

4 What's new in Dragon Medical 360 Network Edition 1.0 SP6 This section covers the newest release of Dragon Medical 360 Network Edition, Nuance's leading speech-recognition and reporting solution for medical professionals. This release provides new features, updates, and enhancements for providers and administrators. Dragon Medical 360 Network Edition1.0 SP6 is available on DVD and from: the isupport site. For details, visit and view article Overview of system requirements for DM360 Network Edition, version 1.0 SP6 Item Description Software provided: DM360 Network Edition version 1.0 SP6 Client (including vsync/minitracker), build number Update Installer (An abbreviated client including : vsync MiniTracker vsync Restorer Dragon Client for Remote Desktop The Update Installer version of the software does not include updates for language or acoustic models.) See Upgrade Installer updates on page 3 for more information. For additional software versions, see the Build Number Table at the end of this document. Where to download: isupport Solution Supported upgrade paths: On-premise and cloud-based installations and upgrades: - 1 -

5 Item Description Client-only upgrade from DM360 Network Edition 1.0 SP3 and newer. Supported Nuance Management Server versions Minimum version of the Dragon client supported by Nuance Management Server 3.0: DM360 Network Edition vsync in this release supports Dragon clients from: NMS 2.0 NMS 3.0 DM360 Network Edition 1.0 SP3 (build number ) DM360 Network Edition 1.0 SP3 (build number ) and newer, without uninstalling. Note that generally the vsync Mini- Tracker component on all Citrix servers must be equal to or greater than the highest version of the vsync client component installed on the Dragon workstations. About DM360 Network Edition Logging and Protected Health Information The default logging settings in Dragon Medical products produce log data that complies with privacy standards. Dragon Support may instruct you to change these logging settings to produce logs that provide more information. In this case, the log data may include patient relevant data, for example, patient name. To remain compliant to local privacy standards, you should only use these logging settings in a test environment, or with test patient data. Dragon Medical 360 Network Edition and Citrix If you are publishing DM360 Network Edition SP6 on Citrix servers, you must update the version of DM360 Network Edition Client Update for Citrix that is installed on your workstations. To update the client, uninstall the old version, and install the latest version using the following executable: vddnspatch.exe located in the Citrix Client Update directory of the full installation. Known issues and bug fixes s fixed in DM360 Network Edition - 2 -

6 Installing and upgrading to Dragon Medical 360 Network Edition, 1.0 SP6 Upgrade Installer updates The Upgrade Installer installs product updates as a software patch. These updates do not include updates for language or acoustic models. You use the Upgrade Installer provided with DM360 Network Edition 1.0 SP6 to upgrade the entire Dragon client at one time, including the vsync components on the client machine. You can also use the Upgrade Installer to upgrade many Dragon clients quickly and simultaneously. The Upgrade Installer upgrades Dragon clients to DM360 Network Edition 1.0 SP6 from version 1.0 SP3 and newer. You can obtain the Upgrade Installer zip file from the isupport site. For details, visit and view article The Upgrade Installer zip file, DMNE10ServicePack6.zip, contains the following files and directories: DMNE10ServicePack6.exe: the Upgrade Installer MiniTracker.exe : vsync for the Citrix server vsyncrestorer.exe : for restoring vsync support after updating a Citrix client Dragon Client for Remote Desktop: Contains software that allows you to use a PowerMic II over remote desktop. Note: The Update Installer does not include the latest version of vddnspatch.exe. Use the full install if you will be publishing DM360 Network Edition on Citrix. See Dragon Medical 360 Network Edition and Citrix on page 2 You can view messages about Upgrade Installer updates on Nuance Management Console. In the Nuance Management Server Administrator Guide, see the following sections for more information: 'Receiving notifications from the Update Server' 'Purging messages.' When to use the Upgrade Installer: If Dragon is installed: on a workstation on a Citrix server Use the Upgrade Installer or the full Dragon installer to upgrade Dragon (and if applicable, vsync client component) to DM360 Network Edition 1.0 SP6. Repair vsync after installing or upgrading the Citrix client - 3 -

7 To repair vsync on workstations where the Citrix client has either been updated or re-installed, use the vsync Restoration Patch, vsyncrestorer.exe, included in the Upgrade Installer zip file. Update vsync on a Citrix server To update the vsync component on a Citrix server that publishes applications, use MiniTracker.exe, included in the Upgrade Installer zip file. In this configuration, Dragon is installed on a workstation and not on the Citrix server. Windows XP Support The 2.x versions of DM360 Network Edition will be the last versions of the product to support Windows XP. DM360 Network Edition 1.0 SP6 continues to support Windows XP

8 Known s and fixes in Dragon Medical 360 Network Edition Known s and fixes in Dragon Medical 360 Network Edition, 1.0 Service Pack 6 In-Depth Description The MyCommands Protection Utility tool's The MyCommands Protection Utility tool's documentation for the documentation for the required syntax is missing required syntax is missing quotes. quotes. The tool's /help file and the client's help file indicate the syntax should be: protectcmds.exe <dat-file-path> <vendor-name> [<vendor-contact-info>] however the correct syntax requires quotes be included as follows: protectcmds.exe "<dat-file-path>" <vendor-name> [<vendor-contact-info>] Workaround Use the following syntax: correct syntax requires quotes be included as follows: DM360 Network Edition with Cerner: Cursor jumped or lost focus after replacing the text from correction menu DM360 Network Edition with Epic 2012 and Citrix: Cursor jumps. protectcmds.exe "<dat-file-path>" <vendor-name> [<vendor-contact-info>] When using DM360 Network Edition with Cerner, the cursor jumped or lost focus after replacing the text from correction menu. New Behavior The jumping cursor issue has been resolved. Jumping cursor when using DM360 Network Edition with EPIC 2012 and Citrix

9 In-Depth Description Cursor synch problem with Cerner when using vsync. The jumping cursor issue has been resolved. Cursor out of synch when using Cerner with vsync in the following workflow: DM360 Network Edition SP6 Clients do not write session ends data to audit events Audio devices not responding properly after upgrading from Windows XP to Windows7 while keeping the same machine name. 1. The user opens a free text area of Cerner and inserts a template. 2. The user begins dictating, navigating to an area with delimiters (for example: []) with no issue. 3. The user navigates away from the window displaying the template, opens the dictation box, and puts it in hidden mode. 4. The user goes to another part of the chart and dictates into the hidden dictation box as he reviews the chart. 5. The user then goes back into the original free text area and opens the dictation box to fix anything that needs to be fixed. He focuses the cursor in the location he wants to insert the text and then does a transfer text. Any navigation after this point inserts the cursor into the wrong location. The synchronization issue is resolved. DM360 Network Edition SP6Clients do not write session ends data to audit events. DM360 Network Edition SP6 Clients now write session ends data to audit events. After upgrading from Windows XP to Windows7 while keeping the same machine name, DM360 Network Edition does not update the audio.ini file properly, causing audio devices to respond improperly

10 In-Depth Description DM360 Network Edition now updates the audio.ini file properly, and audio devices respond as expected. Workaround For users who have already upgraded and are seeing this issue, a utility is available that will edit audio.ini files in profiles of users whose workstations have been upgraded from Windows XP to Windows 7. Visit and view isupport Solution to download the utility and for additional information It is difficult to clean up old profiles in the Deleted, POTemProfiles, and Bad folders. It is difficult to clean up old profiles in the Deleted, POTemProfiles, and Bad folders. Solution A new profile clean up tool allows users to clean up deleted, temporary, and bad profiles located in the following folders: 9021-When used within Practice Partner, DM360 Network Edition with vsync failed to insert text and has a jumping cursor issue DM360 Network Edition with Cerner Power- Note: Cursor loses focus. Deleted POTempProfiles Bad Visit and view isupport Solution to download the tool and for additional information. When used within Practice Partner, DM360 Network Edition with vsync failed to insert text and has a jumping cursor issue. The failure to insert text and jumping cursor issues with DM360 Network Edition with vsync in Practice Partner are now resolved. When dictating into Cerner PowerNote, the cursor jumps or disappears, causing the dictation to not be entered into the window, or to appear in a different location

11 In-Depth Description vsync timed out frequently because messages sent by minidragon could not be processed by the Citrix virtual channel thread After upgrading from DM360 Network Edition SP3 to SP6, user profiles with shared commands have a long initial load time Citrix takes the focus from target apps during the text transfer from dictation box in hidden mode. This issue has been resolved. vsync timed out frequently because messages sent by minidragon could not be processed by the Citrix virtual channel thread. vsync timeouts occur less frequently. After upgrading from DM360 Network Edition SP3 to SP6, user profiles with shared commands have a long initial load time. The initial load time for user profiles with shared commands is now < 1 minute. Citrix takes the focus from target apps during the text transfer from dictation box in hidden mode. The following steps reproduce the issue: 1. Launch Centricity via the Citrix client. 2. Start DM360 Network Editionand go to Tools > Options > Dictation box. 3. In "Dictation Box Open" option, select "Always hidden" 4. Start dictating and transfer the text into Centricity: a. Say "Open dictation box". b. Dictate something. c. Say "Transfer text". d. Say "New Line". e. Say "Open dictation box". 5. Repeat step 3a-3d few times. The Clipboard in use by another application warning appears. Workaround This is a Citrix issue; use the following steps as a workaround: - 8 -

12 In-Depth Description Field Complete only works properly when there are two spaces between each variable delimiter. 1. Once Centricity loses focus, switch to any other app by clicking on the app's window. 2. Come back to Centricity and say "transfer text". Field Complete only works properly when there are two spaces between each variable delimiter. "Field Complete" now functions as expected with a single space between each variable delimiter

13 Product build numbers The following table summarizes the Dragon, Nuance Management Server (NMS), Profile Optimizer Server (POS), and SDK builds that are part of different releases of Dragon Medical 360 Network Edition. DM360 Network Edition Version 2.x Releases Product version Product Component Build Number 2.2 Dragon client NMS POS Call Forwarder SDK Dragon client NMS POS Call Forwarder SDK Original product release (2.0) Dragon client NMS POS Call Forwarder SDK DM360 Network Edition Version 1.x Releases Product version Product Component Build Number Original product release Dragon client NMS POS

14 Product version Product Component Build Number SDK Hot fix 1 Dragon client Hot fix 2 Dragon client Hot fix 3 Dragon client Hot fix 4 Dragon client Hot fix 5 Dragon client Hot fix 6 Dragon client Hot fix 7 Dragon client Service Pack 1 Dragon client NMS POS SDK Service Pack 2 for NMS/Nuance Management Console/POS/SpeechNode/SDK, (Re-release of HF7 as a service pack) Dragon client NMS POS SDK NMS Service Pack Service Pack 3 Dragon client NMS POS SDK Service Pack 3.5 Dragon client Service Pack 3.5 Hot fix 1 Dragon client Service Pack 3.5 Hot fix 2 vsync Restoration patch Service Pack 3.5 Hot fix 3 Dragon Client

15 Product version Service Pack 3.5 Hot fix 4 Product Component vsync MiniTracker only Build Number Service Pack 5 Dragon client NMS POS SDK Service Pack 6 Dragon client How to find the build number of a DM360 Network Edition component Component Instructions Dragon client Method 1: On the DragonBar, click Help > About Dragon. Method 2: 1. In the Start Menu, select All Programs > Network Edition > Show Dragon Log, or, if you are running Windows 8 or newer, go to Win 8 Metros and click the "Show Dragon Log" icon. For this to work, you must be logged in to Windows under the Dragon user s account. 2. Open the dragon.log file. The build number is the value to the right of "Dragon Medical Version ". Method 3: -On a workstation, in Windows Explorer, on Windows Vista, Windows 7, Windows 8, or Windows Server 2008, look here: C:\Users\<WindowsUsername>\AppData\Roaming\Nuance\ NaturallySpeaking12\Dragon.log -On a workstation, in Windows Explorer, on Windows XP, look here: C:\Documents and Settings\<user_account_login>\Application Data\Nuance\ NaturallySpeaking12\Dragon.log

16 Component Nuance Management Server Instructions Method 1 (for an on-premise NMS): 1. On the NMS server, navigate to: C:\Program Files\Nuance\NMS Server- \Nuance.NAS.Server.exe. 2. Double-click Nuance.NAS.Server.exe. 3. In the Properties dialog box, click Version. The build number is the value to the right of "Dragon Medical Version". Method 2: 1. View the version number in the lower right corner of the Nuance Management Console login screen. SDK Method 1: 1. In the Nuance Management Console, in the Utilities ribbon, select Profile Optimizer Tasks. 2. Highlight a task and select DM360 Network Edition log. Method 2: On a Speech Node machine, find and open the Dragon log file. Profile Optimizer Server Method 1: 1. In the Nuance Management Console, in the Utilities ribbon, select Profile Optimizer Tasks. 2. Highlight a task and select View Speech Node Log. The build number is the value to the right of "assembly version=". Method 2: 1. On the POS server, find and right click POService.exe. 2. In the POService.exe Properties dialog box, click Version. The build number is the value to the right of "File version:"