Activity Log
The activity log can be helpful for troubleshooting commands that aren’t working as expected. Once the activity log has been launched, the command should be tested within the appropriate environment. Users should verify that the proper application has focus and that Fluency Direct is executing the correct command. Once the command has finished running the activity log should be checked for the following:
Command Name – Does this match the command that was dictated?
A misrecognition occurred, try mapping the command to a keyboard or microphone button to test again. If the command is recognized through a key press the command name may need modified for recognition (e.g. patient lookup --> patient look up). Try modifying the command name and testing again. If the command continues to be misrecognized verify that there isn't a dictionary or abbreviation entry in the users profile that matches the command name.
Group – Does this show the proper command group for the command?
Check to make sure their isn't already another command with the same name, or an old starter set command that Fluency Direct is triggering instead. (e.g. Epic 2017 General Commands vs. Epic 2018 General Commands)
Process Name – Does the process reflect the intended EMR or application?
Make sure that the cursor has focus in the proper application before testing the command again.
Window Title – Does the window title match the EMR or application window that should have focus?
Make sure that the cursor has focus in the proper application window before testing the command again.
Do all the command steps show as complete?
There may be a missing data set or grammar. Check the command in manage commands for an error.