Skip to main content

Troubleshooting Starter Set Commands

When importing starter sets there can be configuration changes or importing errors that prevent a command from working as expected. Before reaching out to your adoption resource the following items can be checked to verify everything is set up properly. Reporting an FDS ticket

Starter Set Compatibility

Starter Set compatibility can be found in the associated pdf for each Starter Set. This includes the EMR or application version(s) and the earliest version of Fluency Direct that the commands are supported in. Some Starter Sets require the latest version of Fluency Direct to run.

Commands without Grammars Failing

Commands without grammars can fail due to the command name. In these cases, the command name should be reviewed for the following:

  • Adjust the naming convention from uppercase to lowercase

  • Check to make sure there are no dictionary or abbreviation entries conflicting with the current command name

  • Try dictating the command name to see if Fluency Direct recognizes the word differently (e.g. patient lookup --> patient look up)

Command steps are accurate but the command isn't recognized

Some starter sets have their availability set for an intended EMR or application.  To ensure the keyboard shortcuts are accurate for the intended application try the steps manually with your keyboard. Once the keyboard steps are verified, try changing the command group or individual command availability to "Available everywhere" or adding waits if the command has multiple steps.  If the command continues to be misrecognized, try modifying the command name (e.g. Open Powerpoint --> Open Power point) and checking to make sure a dictionary or abbreviation entry doesn't already exist with the same naming convention.

Error Message, "command not recognized"

In Fluency Direct deployments with version 11.0 client and connector, scripting commands must be configured to run via remote processing.  To "enable remote processing" open the command in secret mode and navigate to the details tab.  Check that "enable remote processing" is checked for any scripting commands.

Issues with FD performance

Commands with complex grammars allow users to create and use commands with many possible results.  If performance issues exist, including no text output or freezing there may be an issue with complex grammar commands. Require pauses should always remain checked for commands with complex grammars.  To resolve, open the command in secret mode and check that require pauses is checked appropriately.