How can we disable Dragon Medical SpeechKit built-in standard voice commands in the Browser SDK?

Huaifei 0 Reputation points
2026-05-14T09:37:45.7633333+00:00

Hello, we are using Dragon Medical SpeechKit Browser SDK in a web application.

Our current Browser SDK configuration is similar to the following:

window.NUSA_userId = configuration.userId;
window.NUSA_applicationName = configuration.applicationName;
window.NUSA_service = configuration.serviceUrl;
window.NUSA_enableAll = false;
window.NUSA_language = configuration.language;
window.NUSA_topic = configuration.topic;

We also use application commands/custom controls in our integration.

We are investigating whether it is possible to disable Dragon Medical built-in standard voice commands, or specific standard dictation/formatting commands, from the Browser SDK side.

For example, when a user dictates phrases such as:

  • new line
  • next line
  • new paragraph
  • paragraph

Dragon Medical SpeechKit may interpret them as built-in dictation/formatting commands instead of literal dictated text.

From the documentation, I found that:

  • NUSA_enableAll=false only controls which HTML controls are speech-enabled via data-nusa-enabled="true".
  • NUSA_enableCommandSet(id, enabled) and NUSA_enableCommand(id, enabled) seem to apply only to application commands registered by the application.
  • The documentation says Dragon Medical standard commands have priority over application commands.

My questions are:

  1. Is there any Browser SDK API or configuration option to disable Dragon Medical built-in standard commands globally while keeping normal dictation enabled?
  2. Is there any way to disable only specific built-in standard commands, for example new line or new paragraph?
  3. If this is not supported from the Browser SDK, is there any tenant/admin/user-level configuration in Dragon Medical SpeechKit or Nuance/Microsoft backend settings that can control built-in dictation formatting commands?
  4. What is the recommended approach if an application needs mostly literal dictation text and wants to avoid automatic command interpretation for phrases like new line / new paragraph?

Any official guidance would be appreciated.

Nuance | Other
Nuance | Other

Additional Nuance products, services, or issues

0 comments

1 answer

Sort by: Oldest
Most helpful Newest Oldest

  1. AI answer

    2026-05-14T09:38:05.62+00:00

    The Browser SDK documentation only distinguishes between:

    • Standard commands: built-in Dragon Copilot / Dragon Medical commands for dictation, navigation, correction, etc., which “don’t require or allow any handling by your app.”
    • Application commands: commands defined and fully controlled by the integration.

    Standard commands are defined, stored, and handled entirely by Dragon Copilot / Dragon Medical, not by the Browser SDK integration:

    “Standard commands: These are the Dragon Copilot built-in voice commands and include commands for dictation, navigation, correction, etc. They don't require or allow any handling by your app.”

    Application commands are the only commands that can be enabled/disabled or modified via the Browser SDK APIs (NUSA_createCommandSet, NUSA_createCommand, NUSA_enableCommandSet, NUSA_enableCommand, NUSA_reinitializeVuiForm, etc.). Command sets and command enablement apply only to these application commands.

    The documentation also states that standard commands have priority over application commands:

    “The spoken phrases for application commands must be unique. If they share a name with a standard command, the standard command is applied.”

    Within the provided documentation set, there is no API, configuration flag, or browser-side mechanism to:

    1. Disable all built-in standard commands while keeping dictation enabled.
    2. Disable or override specific standard commands such as new line or new paragraph.
    3. Reconfigure standard dictation/formatting behavior from the Browser SDK.

    All enable/disable mechanisms described (NUSA_enableAll, NUSA_enableCommandSet, NUSA_enableCommand) are scoped to:

    • Which HTML controls are speech-enabled (NUSA_enableAll and data-nusa-enabled).
    • Which application command sets and application commands are active.

    They do not affect standard commands.

    The documentation in scope also does not describe any tenant/admin/user-level configuration for turning off or customizing standard dictation/formatting commands. Any such configuration, if it exists, is not covered in the referenced materials.

    Given this, the only documented, supported levers for an integration are:

    • Control where dictation is allowed (speech-enabled controls and command sets).
    • Define application commands with unique phrases that do not collide with standard commands.
    • Follow the recommendations for application command phrases (distinctive, natural, non-ambiguous) to reduce misinterpretation as commands.

    There is no documented way in this context to achieve “literal-only” dictation for phrases that are already defined as standard commands.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.