Dragon Medical 360 Network Edition 2.3. Release Notes

Transcription

1 Dragon Medical 360 Network Edition 2.3 Release Notes

2 Copyright Copyright Nuance Communications, Inc. All rights reserved. To view and download the latest version of this document, visit: 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 third-parties 9/30/2014 L-3795

3 Contents What's new in Dragon Medical 360 Network Edition Overview of system requirements for DM360 Network Edition, version Installing or Upgrading DM360 Network Edition 2 About DM360 Network Edition Logging and Protected Health Information 2 Using the Power Mic with VMWare and the Dictation Box 3 Notes about acoustic models and user profiles and DM360 Network Edition, version Nuance Upgrade Training 3 What's new for administrators 4 What's new for providers 4 Known issues and bug fixes 4 Nuance Management Server Log Uploader 4 Upgrade Installer updates 5 When to use the Upgrade Installer: 5 Going from the DM 360 Network Edition 2.x to DM 360 Network Edition 2.3 version of the Citrix Client Extension 6 New in Dragon Medical 360 Network Edition, 2.3 for Providers 6 Windows XP Support 7 What's new in Nuance Management Server 8 Known s and fixes in Dragon Medical 360 Network Edition 11 Product build numbers 16 DM360 Network Edition Version 2.x Releases 16 DM360 Network Edition Version 1.x Releases 16 How to find the build number of a DM360 Network Edition component 18 iii

4 What's new in Dragon Medical 360 Network Edition 2.3 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 Edition 2.3 is available on DVD and from: the isupport site. For details, visit and view article Overview of system requirements for DM360 Network Edition, version 2.3 Item Software provided: Description DM360 Network Edition version 2.3 Client (including vsync/minitracker), build number Nuance Management Server version 4.3, build number and Profile Optimize build number Update Installer build number (An abbreviated client including : The Update Installer vsync MiniTracker vsync Restorer Dragon Client for Remote Desktop Citrix Extension (previously known as the Citrix Client Update) The Update Installer version of the software does not include updates for language or acoustic models.) See Upgrade Installer updates on page 5 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: Upgrade Installer and Full Install Server and Client upgrade from DM360 Network Edition 2.0 and newer Full Install Only Server and Client upgrade from DM360 Network Edition 1.0 SP3 (build number ) and newer Upgrade from Dragon Medical Enterprise 1

5 Release notes for Dragon Medical 360 Network Edition Item Description Edition version 10.x Upgrade from Dragon Medical Practice Edition version 11 Server and Client new installation Profile upgrade to version 2.x required: DM360 Network Edition SQL databases (NuanceMC and NuancePODB) changed? Minimum version of the Dragon client supported by Nuance Management Server 4.3: DM360 Network Edition vsync in this release supports Dragon clients from: If you are upgrading from the following versions of Dragon Medical, you must upgrade your user profiles to version 2.x as described in the DM360 Network Edition Installation Guide: Server and Client upgrade from DM360 Network Edition 1.0 SP3 (build number ) and newer Upgrade from Dragon Medical Enterprise Edition 10.x Upgrade from Dragon Medical Practice Edition version 11 Yes. Nuance recommends backing up the NuanceMC database prior to upgrading. DM360 Network Edition 1.0 SP3 (build number ) DM360 Network Edition 1.0 SP3 (build number ) and newer. 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. Installing or Upgrading DM360 Network Edition When you install or upgrade DM360 Network Edition, be sure to install or upgrade the server components (Nuance Management Server and Console, Profile Optimizer Server and Speech Nodes, and the SDK) before installing or upgrading the Dragon client. See the DM360 Network Edition Installation Guide for details on how to install the server and client components of DM360 Network Edition. 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. The Protected Health Information Warning Dialogs If you have changed your logging settings so that the logs may include PHI, warning dialogs will appear when you load a user profile, giving you the option to cancel these changes. If you click OK, PHI may appear in the logs. If you click Cancel, Dragon will shut down if you are in the Dragon Client, or will disable logging if you are in the EHR Synchronizer/MiniTracker. 2

6 Using the Power Mic with VMWare and the Dictation Box If you are using the Power Mic with VMWare and dictating into an unsupported edit control using the Diction Box (there will be a gray checkmark/dot next to the microphone meter on the DragonBar), note that the Power Mic button configuration will be set to use the "Transcribe" button to open the dictation box and the "Enter/Select" button to transfer text. Notes about acoustic models and user profiles and DM360 Network Edition, version 2.3 Note: Nuance recommends upgrading user profiles on multi-core machines for better throughput. Profiles upgraded on machines with a number of cores that is different than the number of cores on the speech nodes that run the profiles generates a warning message about recognition accuracy. For example, if you upgrade your profiles on a dual core machine but run them on a single core speech node, the warning message appears when the profile is opened. See the DM360 Network Edition Planning Guide for recommended hardware specifications. To prevent the warning message from appearing, use machines with the same number of cores to upgrade speech profiles and for the speech nodes. For example, if you upgrade the profiles on a dual core machine, run those profiles on dual core speech nodes. Keep the following points in mind about the DM360 Network Edition version 2.3 acoustic models and user profiles: If you are upgrading from DM 360 Network Edition version 1.0 (SP3 or newer)you will need to upgrade your user profiles to version 2.x. BestMatch IV and BestMatch V acoustic models on a dual-core machine are about 36 MB larger than BestMatch III acoustic models. When you upgrade a profile to DM360 Network Edition version 2.3, the Acoustic optimizer processes several.dra files. The processed.dra files are larger than the original.dra files. When you upgrade a profile to DM360 Network Edition, version 2.3 the upgrade process copies the full contents of the backup directory. The size of the folder depends on the size of the current folder that was present when the backup was made. Nuance Upgrade Training If you are upgrading from a version of Dragon software other than DM 360 Network Edition Version 2.x, DM360 Network Edition version 2.3 upgrade is complex. You will need to plan your upgrade carefully, taking your specific needs and environment into account. Nuance strongly recommends our Upgrade Training Package to help your IT team to transition to DM360 Network Edition version 2.3 with minimal disruption. This package provides web-based training for the IT personnel responsible for upgrading your system. It includes a 3-day engagement which ensures that all of the upgrade steps are performed correctly and in the right sequence. 3

7 Release notes for Dragon Medical 360 Network Edition Please contact your Account Executive for more information about this offering, or call If you do not know your Account Executive, Nuance can put you in contact with that person. See DM 360 Network Edition Upgrade Training to view the class agenda. If you are upgrading from DM 360 Network Edition Version 2.0 or newer, upgrade is much simpler, and you may not require upgrade training. What's new for administrators What's New in Nuance Management Server for Administrators What's new for providers What's New in DM 360 Network Edition for Providers Known issues and bug fixes s fixed in DM360 Network Edition Nuance Management Server Log Uploader The Nuance Management Server (NMS) Log Uploader allows you to upload and view logs on the NMS. The Log Uploader requires several prerequisites installed in the following order: Install/enable.NET framework. See the System Requirements page, Nuance Management Software Requirements section, of the DM 360 Network Edition Planning Guide, Installation Guide, or Administrator's Guide for supported versions. Citrix XenApp 5, 6 or 6.5 (an EHR synchronizer/minitracker) prerequisite. EHR synchronizer (MiniTracker). If you have already installed MiniTracker and the NMS Log Uploader is not working, take the following steps: Install/enable.NET framework. See the System Requirements page, Nuance Management Software Requirements section, of the DM 360 Network Edition Planning Guide, Installation Guide, or Administrator's Guide for supported versions. Uninstall EHR synchronizer (MiniTracker). Reinstall EHR synchronizer (MiniTracker). Configuring NMS Log Uploader To configure NMS Log Uploader, use the NMC to create a Dragon speaker with the following login: Username: MinitrackerLogUploader Password: MinitrackerLogUploader 4

8 Viewing Logs with NMS Log Uploader To view the uploaded minitracker.log files in NMC, click on the Utilities tab and then click the Client Logs option. 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 2.3 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 2.3 from version 2.x. You can obtain the Upgrade Installer zip file from the isupport site. For details, visit and view article The Upgrade Installer zip file, DMNE2DOT3.zip, contains the following files and directories: DMNE2DOT3.exe: the Upgrade Installer MiniTracker.exe : vsync for the Citrix server vsyncrestorer.exe : for restoring vsync support after updating a Citrix client Citrix Extension (previously known as the Citrix Client Update): Contains the Citrix Client update (vddnspatch2.exe or vddnspatch2.msi), as well as PowerMic extensions for the Citrix Client and Server. See the Citrix Administrator Guide for more information. Dragon Client for Remote Desktop: Contains software that allows you to use a PowerMic over remote desktop. You can view messages about Upgrade Installer updates for Dragon and vsync on a client computer. In the Nuance Management Server Administrator Guide, see: '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 2.3. Repair vsync after installing or upgrading the Citrix client 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 5

9 Release notes for Dragon Medical 360 Network Edition 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. Going from the DM 360 Network Edition 2.x to DM 360 Network Edition 2.3 version of the Citrix Client Extension If you are going from a 2.x version of the Citrix Extension (formerly known as Citrix Client Update) to the 2.3 version, take the following steps to upgrade: 1. On each machine where the Citrix XenApp client is installed, keep your current version of vddnspatch.exe or vddnspatch.msi installed. Install the new vddnspatch2.exe file on the XenApp client machine. 2. If you will be using a PowerMic, install the Citrix Client Extension. Navigate to the Citrix Client Extension directory in your installation files and double-click the PowerMic Citrix Extension Client.msi file. 3. Repeat steps 1 and 2 until vddnspatch2.exe and the Citrix Client Extension are installed on all of the XenApp client machines. 4. On the XenApp Server, upgrade DM 360 Network Edition to version 2.3. If you will be using a PowerMic, install the Citrix Server Extension. Navigate to the Citrix Server Extension directory in your installation files and double-click the PowerMic Citrix Extension Server.msi file. 5. (Optional) Uninstall the old version of vddnspatch.exe or vddnspatch.msi from the XenApp client machines. New in Dragon Medical 360 Network Edition, 2.3 for Providers Description Connection Center updates. Dragon Bar status message updates. User Profile import improvements. New voice commands for setting visibility percentage for Hidden Dictation Box. Feature The Connection Center is updated to make connection states and statuses easier to understand. See the Connection Center topics in the Dragon Client help for more information. The Dragon Bar connection status messages have been updated to make connection states and statuses easier to understand. In the Extended Dragon bar, a new button allows you to see the current connection status and easily open the Connection Center for additional information on the connection. See the Connection Center topics in the Dragon Client help for more information. Imported user profiles default to the same name as the user profile they are replacing, so that Profile Optimizer can be run on the imported profile without any additional changes. You can use new voice commands to set the visibility percentage of the Hidden Dictation Box. For example: "dictation box set visibility to 75%". See the Hidden Dictation Box topics in the Dragon Client help for more information. 6

10 Description Feature Smooth Roaming improvements on XenApp 6.5 (PowerMic connection carries over). There are Smooth Roaming improvements on XenApp 6.5; the PowerMic connection now carries over. XenDesktop 7.1 support DM 360 Network Edition now supports XenDesktop 7.1. Wyse terminal (Dell T10) support DM 360 Network Edition now supports Wyse terminal (Dell T10). DM360 Network Edition through a remote DM 360 Network Edition now supports using DM360 desktop connection on Windows Server 2012 Network Edition through a remote desktop connection on R2 Windows Server 2012 R2. 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 2.3 continues to support Windows XP. 7

11 Release notes for Dragon Medical 360 Network Edition What's new in Nuance Management Server This section covers the newest release of the Nuance Management Server (NMS) and its web client, the Nuance Management Console. This release provides new features, updates, and enhancements for administrators that work with the NMS and the Nuance Management Console. Feature Handling of duplicate user login names when migrating data to the cloud NMS Description In the Cloud Migration Tool, the On User Conflict page lets you set the tool to add a prefix, a suffix, or both to migrated user login names that conflict with user login names that already exist in the cloud NMS. After the Cloud Migration Tool sends the migration data to NMS, NMS migrates the user accounts and adds a prefix, suffix, or both to login names that are the same as login names already in the cloud NMS. If after adding the prefix and/or suffix there is still a conflict, NMS adds a random string of eight characters to the original login name and saves it. For more details about the Cloud Migration Tool, see Move data from an existing on-premise NMS server to the cloud NMS server in the DM 360 Network Edition Administrator's Guide. Copy message text to the clipboard Allow or prevent an end-user from using Dragon in offline mode Using DM360 Network Edition through a remote desktop connection on Windows Server 2012 R2 In NMS 4.3 Messages in the Nuance Management Console (NMC) have a context menu item labeled Copy message text to clipboard that allows you to copy the contents of the message to the clipboard. Use this feature to save message information in another application. For example, saving a list of new user account login IDs after using the Cloud Migration tool. An administrator can enable or disable offline mode in the NMC. If Offline mode is disabled and a user selects the 'If your connectivity is slow, select this option to connect to the server without synchronizing your master profile' checkbox on the Dragon login screen, a warning appears, noting that offline mode is unavailable. For details, see Allow DMNE Client Offline mode option in the DM 360 Network Edition Administrator's Guide. Using DM360 Network Edition through a Remote desktop connection now supports Dragon on Windows Server 2012 R2. For details, see Using the Dragon Medical client through a remote desktop connection in the DM 360 Network Edition Administrator's Guide. 8

12 Feature Ensure new profiles use BestMatch IV acoustic models. Set the 'insert via clipboard' feature for a user or a group. Disable the "automatically select the first field" feature for a group of users. Do not display a warning when a user profile with a BestMatch-IV or BestMatch-V model loads on a single-core computer. Changes to the default values of Dragon settings Creating a unique login for a user Installing Dragon and documentation from the NMC Description An administrator can set an NMC option to make all users in a site use BestMatch IV acoustic models when they create a profile. This is recommended for Citrix XenDesktop users that work in virtual environments. For details see Create BM-IV profiles by default in the DM 360 Network Edition Administrator's Guide. An administrator can set the 'insert via clipboard' feature for a client user or a group of users. The administrator does not need to set the feature for each individual Dragon client. For details, see Use clipboard for Citrix basic dictation for a group and Use clipboard for Citrix basic dictation for a user in the DM 360 Network Edition Administrator's Guide. The "automatically select the first field" feature advances the cursor to the first field when a user inserts a template into an edit control. An administrator can disable the "automatically select the first field" feature for a user or a group of users. For details, see Enable automatically select first field for a user and Enable automatically select first field for a group in the DM 360 Network Edition Administrator's Guide. On a single-core computer, if a user loads a user profile that uses a BestMatch-IV or BestMatch-V model, Dragon displays a warning message. An administrator can use the NMC option to suppress the warning. For details, see Suppress warning for using multi-core speech profiles on single core machines in the DM 360 Network Edition Administrator's Guide. The following settings have new default values: Enable mouse motion commands: The default value is now 'Disabled'. Insert two spaces after period: The default value is now 'Disabled'. Rewrite cc after a number as ml : The default value is now 'Enabled'. When an administrator creates a login ID for a user, if the ID already exists, the NMC displays an error message. For details, see Configuring user account details and address settings in the DM 360 Network Edition Administrator's Guide. The following items have been removed from the NMC in NMS 4.3: -Setting the location and version of the Dragon MSI installer -Setting the local download location for documentation 9

13 Release notes for Dragon Medical 360 Network Edition Feature Description -Downloading the Dragon MSI installer and documentation to a workstation Link to the medical documentation web site Specifying a level when importing auto-texts Apply profile updates to the master user profile when Dragon automatically logs off an idle user The main landing page in the NMC Help contains a link to the Dragon Medical documentation site: When importing auto-texts, an administrator can specify the level of (Site, Group, or User) in the XML file. For details, see Import auto-texts in the DM 360 Network Edition Administrator's Guide. An administrator can set profile changes to be saved to the master user profile when Dragon automatically logs off an idle user. This behavior can be set at the both the site and user level. For details, see Configuring Dragon Settings and Setting User Account options in the DM 360 Network Edition Administrator's Guide. 10

14 Known s and fixes in Dragon Medical 360 Network Edition s 25039, 25040, 24158, 22637, Improved Cerner MPages support for customers with Citrix servers running Internet Explorer 8 and newer. s and Allscripts Edit Control Support In-Depth Description Improved Cerner MPages support for customers with Citrix servers running Internet Explorer 8 and newer The Enable Automatically Select First Field" option in the Dragon Client now works consistently Templates no longer copy themselves repeatedly Slowness when using "Accept defaults" is resolved PowerMic II "Next Field" button now works to navigate through fields after the second patient is loaded Slowness when navigating through a template is resolved Dragon did not have full text control Dragon has full text control in the versions of Allscripts SCM that support TERN The cursor position was offset when a user uses the "select" command and then deletes prior word in Allscripts Sunrise Clinical Manager. s 23259, 23334, 24809, 22484, DRA outcast folder creation causes crashes / Side by side error in Dragon with dragon_ support_packager.exe Using Meditech word processor with Internet Explorer causes a crash. Dragon now has ful text control in the versions of Allscripts SCM that support TERN16. Customers who want this support must have Allscripts SCM 6.1 SU7 or newer installed. The cursor position is no longer offset when using the "select" command and deleting the prior word. DRA outcast folder creation causes crashes. DRA outcast folder creation no longer causes crashes. Side by side error in Dragon with dragon_support_packager.exe. The side by side error is resolved. Using Meditech word processor with Internet Explorer causes a crash. Using Meditech word processor with Internet Explorer no longer causes a crash. 11

15 Release notes for Dragon Medical 360 Network Edition 9024/ Dragon freezes in a terminal session Minitracker.log lost after failure to upload log to NMS Accession Numbers are formatted incorrectly vsync time outs In-Depth Description Dragon freezes in a terminal session. Dragon no longer freezes in a terminal session. Minitracker.log lost after failure to upload log to NMS. Minitracker.log is no longer lost if NMS fails to upload the log. When dictating Accession Numbers that have the following format:a letter followed by 2 digits, a dash, and then 5 or 6 additional digits (for example, S ), a space appears at random locations. Workaround Use Spell mode to dictate the Accession Numbers. vsync timed out frequently because messages sent by minidragon could not be processed by the Citrix virtual channel thread Users dictating into an unsupported edit control with PowerMicII must use the Enter/Select button to transfer text Unable to dictate into Epic 2010 Orders and Clinical Impression search window Cerner Powerchart - Drop Down Menu is not working with minitracker v vsync Notification Tool no longer supported Jumping cursor when using the Delete command with Cerner PowerNote Double Click to Correct not functioning in AllScripts Unstructured Notes. Time outs are less frequent. Users dictating into an unsupported edit control with PowerMicII must use the Enter/Select button to transfer text. New Content See the "Unanchored" table in the "Using the Dictation Box" topic of the Dragon Client help for more information. Unable to dictate into Epic 2010 Orders and Clinical Impression search window. Dictation now works as expected. Cerner Powerchart - Drop Down Menu is not working with minitracker v2.1. Resolution This is an issue with Cerner, and has been submitted to them as a bug. The vsync Notification Tool is no longer supported. Resolution The vsync Notification Tool is no longer supported. See isupport Solution for additional information. Jumping cursor when using the Delete command with Cerner PowerNote. The jumping cursor issue is resolved. Double Click to Correct not functioning in AllScripts Unstructured Notes. 12

16 In-Depth Description Jumping Cursor in Epic Upgrade leaves a backup directory filled with unneeded files Nuance Management Console's Import dialog box should not accept.dat files Command sharing delays and access denied to Command Sets Security vulnerablility in dgnsvc.exe. Customers can use the Double click to correct option when in an AllScripts Unstructured note. Jumping Cursor in Epic The jumping cursor issue has been resolved. Upgrade leaves a backup directory filled with unneeded files. Upgrade now deletes unneeded files. Nuance Management Console's Import dialog box should not accept.dat files. The Import dialog no longer accepts.dat files. Only.txt files are accepted. Command sharing is delayed and access is denied to command sets. This issue is resolved. Users can use the command sharing feature and access Command sets. DragonSvc (dgnsvc.exe) uses an unquoted service path, which introduces a security vulnerability Jumping cursor when a file has "Transcribe Recording" run on it Audio device not responding after OS upgrade and same machine name Jumping cursor in EHR-RPMS Dragon Medical 360 Network Edition fails to insert text and has a jumping cursor issue in Practice Partner. The security vulnerability has been fixed. When a file has "Transcribe Recording" run on it into the Dictation Box and you enter a "." (period) after a word, the cursor jumps to the bottom or highlights the text to the bottom. The cursor now remains where it was placed. Audio device not responding after OS upgrade and same machine name. The audio device now functions as expected after an OS upgrade where the machine name remains the same. Jumping cursor in EHR-RPMS. The jumping cursor is now fixed. Dragon Medical 360 Network Edition fails to insert text and has a jumping cursor issue in Practice Partner. The text insersion and jumping cursor issues are resolved. 13

17 Release notes for Dragon Medical 360 Network Edition In-Depth Description Dragon selection off by 1 character in Cerner PowerNote. Dragon selection off by 1 character in Cerner PowerNote In Cerner PowerChart if you switch to Full Screen Mode Global dictation is enabled and vsync does not work Selection offset issues after changing data format in Meditech Dragon crashes. Selection now functions as expected. In Cerner PowerChart if you switch to Full Screen Mode Global dictation is enabled and vsync does not work. vsync now works as expected. Selection offset issues after changing data format in Meditech. The selection offset problem is resolved. DM 360 Network Edition crashes at random intervals Dragon stops interacting with Windows, then crashes Choose commands not working inside spelling window Dragon client crashes followed by numerous RPC_S_ SERVER_UNAVAILABLE messages in Meditech Command Sets load in the client, even if the customer has more than 20 Command Sets Dragon erroneously treats custom commands with different formats as if they have the same format. Dragon no longer crashes. DM 360 Network Edition stops interacting with Windows, then crashes. Crashes no longer occur. Choose commands not working inside spelling window. Choose commands now work as expected. DM 360 Network Edition client crashes followed by numerous RPC_S_SERVER_UNAVAILABLE messages in Meditech. Crashes no longer occur. 20 Command Sets load in the client, even if the customer has more than 20 Command Sets. The client now loads as many Command Sets as the customer has created. Dragon erroneously treats custom commands with different formats as if they have the same format. Dragon now treats custom commands with different formats as expected. Note: For commands that are part of Command Sets, do not put commands with the same format into different Command Sets. Command Sets load in alphabetical order by name, so a Command Set named ABC loads before a Command Set named DEF. If Command Set ABC and Command Set DEF both have a command with the same format--for example, insert <radiology> in ABC, and insert <mylist> in DEF--only insert <radiology> will run, because Command Set ABC loads first, overriding any commands 14

18 Jumping cursor in Dragon Pad when using the space bar Cannot use the "Press F2" step by step command in Epic New option: "Enable HTML custom API" The Profile Association tool fails with a large number of users In Meditech, the "Move to top" command causes the cursor to go to the beginning of the line NMS should check group hierarchy for same-named speech rec objects before returning objects that exist in multiple groups Timeout can occur when running Profile Optimizer Scheduler Settings. In-Depth Description with the same format that exist in other Command Sets. Jumping cursor in Dragon Pad when using the space bar. The jumping cursor is resolved. Cannot use the "Press F2" step by step command in Epic. The "Press F2" step by step command now functions as expected. The "Enable HTML custom API" option is used to support dictation into a web control in the yet to be released Hyperspace The "Enable HTML custom API" option will be disabled for DM360 Network Edition 2.3 and fully enabled for the DM360 Network Edition 2.4 release. The Profile Association tool fails with a large number of users. The Profile Association tool now functions as expected. When a user inserts a template into the editor in Meditech, the "Move to top" command causes the cursor to go to the beginning of the line. This is a Meditech bug. NMS should check group hierarchy for same-named speech rec objects before returning objects that exist in multiple groups. NMS now checks the group hierarchy for same-named speech rec objects before returning objects that exist in multiple groups. Timeout can occur when running Profile Optimizer Scheduler Settings. Timeout no longer occurs when running Profile Optimizer Scheduler Settings. 15

19 Release notes for Dragon Medical 360 Network Edition 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.3 Dragon client NMS POS Call Forwarder SDK Dragon client 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

20 Product version Product Component Build Number NMS POS 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, (Rerelease 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 Service Pack 3.5 Hot fix 4 vsync MiniTracker only Service Pack 5 Dragon client NMS POS

21 Release notes for Dragon Medical 360 Network Edition Product version Product Component Build Number SDK Service Pack 6 Dragon client How to find the build number of a DM360 Network Edition component Compone nt Dragon client Instructions Method 1: On the DragonBar, click Help > About Dragon. Nuance Management Server 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.x, or Windows Server 2008, look here: C:\Users\<WindowsUsername>\AppData\Roaming\Nuance\NaturallySpeaking- 12\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 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. 18

22 Compone nt Profile Optimizer Server Instructions 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:". 19