Nuance Management Center
Table Of Contents
- Dragon_AdminGuideCover_20160929_v2
- Chapter 1: Introducing the Nuance Management Server
- Dragon Group Overview
- User Groups Worksheet
- Prerequisites for the Nuance Management Center
- Accessing NMS Server: Logging in through the Nuance Management Center
- Change the NMC Administrator password
- Accessing and adding to your organization data
- Turning on data collection for your site
- Privacy of your data and Nuance data collection
- Setting up Active Directory single sign-on
- Chapter 2: Overview of NMS in the cloud
- Chapter 3: Configuring sites
- Chapter 4: Configuring groups and user accounts
- Understanding groups
- Determining site or group settings for members of more than one site or group
- Creating Groups
- Setting Privileges for administrator groups
- Viewing, modifying, and deleting groups
- Setting Dragon Group voice command options for user groups
- Creating user accounts
- Configuring user accounts
- Configuring user account details and address settings
- Administrators can send messages to other administrators
- Enable sending messages to an administrator
- Assigning user accounts to groups
- Configuring Users for Active Directory Authentication
- Import multiple users into the NMS server
- XML schema for the user XML import file
- Setting user account Dragon Group client options
- Setting Auto-Formatting Dragon Group options
- Viewing User Profile settings
- Automatically log out an administrator after a period of inactivity
- Viewing, modifying, and deleting a user account
- Finding and viewing a user account
- Modifying a user account
- Applying Dragon Settings to organizations, sites, or groups
- Chapter 5: Managing licenses
- Managing licenses
- Types of license upgrades available
- Obtaining and applying licenses
- Importing licenses included with Dragon Group
- Purchasing and obtaining new licenses
- Viewing licenses
- Viewing license usage information
- Granting licenses
- Granting a license immediately after creating a user account
- Granting a license to an existing user account
- Receiving expiration alerts and renewing licenses
- Viewing messages about expired licenses
- Renewing the License
- Revoking licenses
- Dictating with Author licenses while disconnected from network
- Chapter 6: Configuring Dragon Group settings
- Chapter 7: Managing user profiles
- Creating a user profile
- Configuring the location of Roaming user profiles
- The SSL Settings tabs
- NMS Administrative Settings: Setting site HTTP connection settings for Roamin...
- NMS Administrative Settings: Setting site SSL connection settings for Roaming...
- NMS Administrative Settings: Setting Roaming User settings and Data settings
- Chapter 8: Managing Dragon Clients
- Chapter 9: Managing messages
- Chapter 10: Managing uploads to Nuance
- Chapter 11: Working with Text and Graphics/auto-texts and custom words
- Overview of managing Text and Graphics/auto-texts and custom words
- Overview of Text and Graphics/auto-texts
- Creating shared and personal Text and Graphics/auto-texts and custom words
- Defining Text and Graphics/auto-texts
- Creating Text and Graphics/auto-texts
- Editing Text and Graphics/auto-texts
- Using Text and Graphics/auto-texts
- Adding and managing keywords for auto-texts
- Delete Text and Graphics or auto-texts
- Cutting, copying, and pasting Text and Graphics/auto-texts or words
- Searching for auto-texts, sites, groups, or users
- Viewing Text and Graphics/auto-texts details
- Importing or exporting Text and Graphics/auto-text
- Chapter 12: Working with Command Sets
- Overview of Command Sets
- Searching for Command Sets, sites, or groups in the Nuance Management Center
- Viewing Command Set details in the Nuance Management Center
- Considerations before creating or importing commands or command sets
- How conflicts between commands are identified and displayed
- Viewing information about Command and Command Set conflicts
- Adding Command Sets in the Nuance Management Center
- Modifying Command Sets in the Nuance Management Center
- Deleting Command Sets in the Nuance Management Center
- Chapter 13: Working with custom words
- Chapter 14: Working with Lists
- Chapter 15: Troubleshooting issues
Administrating Dragon with the Nuance Management Console
Cross-Department Commands and Lists
You should add a short organizational ID for all lists within the intended organization,
including ‘global’ commands and commands that are for applications and windows that are
available for multiple (or all) departments\groups.
For example:
mgh_referral_source
In this case, ‘mgh’ is the organization id and ‘referral_source’ is the root name of the list.
Department-specific commands and lists
For command set lists that are unique to specific departments or groups within the
organization, you should add an additional ID to minimize conflicts between the groups.
For example:
mgh_rad_position
In this case, ‘rad’ is the department and ‘position’ is the root name of the list.
Application-specific commands and lists
For lists that are intended for specific applications, you should add an ID for that application to
minimize conflicts between applications.
For example:
mgh_rad_ehr_function
In this case ‘ehr’ (i.e. - ‘electronic health record’) could be the prefix for a specific EHR system
used at the organization and ‘function’ is a list of specific functions to access in that EHR.
Update existing Command Sets instead of creating new ones
Before you create a new Command Set, consider adding the new commands to an existing
Command Set.
This is especially recommended if:
n you need to add new commands for users
n the commands are logically related.
n the commands use the same lists.
This can help minimize the occurrence of list conflicts. The lists in different Command Sets
should hopefully have different names and contents.
How conflicts between commands are identified and
displayed
Conflict Checking in the Dragon client when loading Command Sets
The commands can conflict by having the same name and availability or by using a conflicting
list name. The contents of a command (For example, steps or text) do not have to be the
same to cause a conflict. Commands that are identical to Command Set commands (name,
133










