Admin: Review & Correct Dictation Event Timeline
  • 5 Minutes to read
  • Dark
    Light

Admin: Review & Correct Dictation Event Timeline

  • Dark
    Light

On the Timeline tab of the Detail Review & Correct page you can see metadata about dictation transactions, including information that can be used for troubleshooting dictation issues and latency.

This tab only displays on dictation items.

RandC-timeline-tab-17-0-0

 

 

View the Timeline

 

  1. Go to the Review & Correct page in nVoq.Administrator. 
  • Optionally, click the Manage icon in the sidebar to hide the sidebar while you work.

 

 

  1. Select the appropriate organization from the organization menu at the top of the page.
    • Navigate this menu by using the Expand All button to open all organizations, by clicking the > arrow next to each organization level to open it, or by typing an organization name in the Filter text field. 

 

 

  1. From the Account drop-down menu, select an account or choose "All" at the top of the list to view activity. 
  • Optionally use the Find Account field at the top of the menu to locate a specific account.

RandC-find-account

You can hover your mouse over the account in the list to see the username in a tooltip if it's cut off on the menu.
account-list-hover-username

 

  1. Optionally, filter results to see only dictation activity in this list.
The Timeline tab only displays on dictation items.

 

  1. Click the refresh iconToolbar-Refresh-iconin the blue bar to view results. 

 

 

  1. A summary table of all items appears on the page. Click the Actions icon next to the item you want to review (Accounts-actions-icon) and select Open Item to open the Detail Review & Correct screen.

RandC-open-item

 

  1. On the Detail Review & Correct screen, click the Timeline tab. 
    RandC-timeline-tab-cropped-17-0-0

 

 

Timeline & Metadata Information

Timeline Details

This timeline lists the transaction events that this dictation had with the server. All timeline events and time stamps are displayed according to the system's configured time zone setting. If you change the time zone for your account, the timeline changes to reflect the new time zone. 

Delta (ms) is the difference (in milliseconds) between the previous timeline event being completed and the next one starting.

RandC-timeline

Submit time: The time the dictation was performed. 

Picked up by dictation server: The time the item was picked up by the server.
WebSocket dictations always show the same value for “Submit time” and “Picked up by the dictation server”. The delta between these events is always zero.

 Transcription started: The time the server started transcribing the dictation.

Audio set to done: The time the server finished loading the audio. This delta may display as a negative value, which indicates that the user may have recorded a long dictation that they completed before the system finished processing it.

Transcription done: The time the transcription ended.

Completion: The time the processing on the server ended.

  • If the timestamp for any event is zero (meaning it did not occur) it will not be included in the timeline.
  • The expected order of events is as listed above, and each timeline displays the actual order that events occurred. If events occurred out of the expected order or if an expected event did not occur, events are shaded in light blue (see below).

 

 

RandC-timeline-missing-event-17-0-0

 

RandC-timeline-wrong-order-events-17-0-0

 

Server

The name of the dictation server that processed the job. (This is only displayed to System level administrators.)

Client Product

This is the name of the dictation client that was used to record the dictation.

  • If the dictation was recorded with nVoq.Voice, the field will say "Voice."
  • If the dictation was recorded with nVoq.Mobile Voice, the field will say "nVoq.Mobile Voice."
  • If the dictation was recorded with SayIt, this field will say "SayIt."
  • This field could also be populated for other client products using our APIs.

Client Vendor

This is the vendor of the dictation client used to record the dictation.

  • If the dictation was recorded with SayIt, nVoq.Voice, or nVoq.Mobile Voice, the field will say "nVoq Incorporated."
  • This field could also be populated for other client vendors using our APIs.

Client Version

This is the version number of the dictation client used to record the dictation, for example "16.0.00 build 101" or "16.1.0-9."

  • This field could also be populated for other client products using our APIs. 

ID

The UUID of the dictation that is stored in the database. 

Microphone

The microphone used to record this dictation.

  • If the dictation was recorded on nVoq.Voice and the Microphone setting in the client is configured as "Default," the words "Default - Microphone (microphone name)" will be displayed here. For example, if your computer's default microphone is a Plantronics Blackwire C210, this will display as, "Default - Microphone (Plantronics Blackwire C210)."
  • If the dictation was recorded on nVoq.Voice and a preferred microphone (not "default") is configured on the Microphone setting in the client, the name of that microphone will be displayed, e.g. "Microphone (Plantronics Blackwire C210)".
  • If the dictation was recorded in SayIt this field will be blank unless one of the nVoq Wireless Microphones was used to record the dictation.
  • If the dictation was recorded using the nVoq Wireless Microphone for Android, "Android wMic Dictation" will be displayed.
  • If the dictation was recorded using the nVoq Wireless Microphone for iOS, "iOS wMic Dictation" will be displayed.
  • If the dictation was recorded on nVoq.Mobile Voice, "Android Keyboard" will be displayed. 
An apostrophe in a microphone name may not display properly in this field. 

Queue Depth

The number of items already in the queue and waiting to be picked up by the dictation server when the job was submitted.

This only applies to HTTP dictations. It does NOT apply to WebSocket dictations (a.k.a. "Fast Dictation" in SayIt). 

Queue Time (ms)

The time (in milliseconds) that the item was in the dictation server queue.

This only applies to HTTP dictations. It does NOT apply to WebSocket dictations (a.k.a. "Fast Dictation" in SayIt). 

Topic

The name of the dictation topic used to process this dictation. This is the actual topic from the dictation server that processed the dictation and may not be the same topic name that displays in the user's application. For example, if "Home Healthcare and Hospice" is selected in the application, "General Medicine" will display here. 

Total Time (ms)

The total time (in milliseconds) that elapsed between the time this item was submitted to a dictation server and the time the item was completed by the dictation server.

  • Look at the differences between Audio Length (near the top of the page) and Total Time. A much longer total time than audio length indicates latency on the dictation servers. (Keep in mind that Audio Length is displayed in SECONDS while Total Time is displayed in MILLISECONDS.) If you see a large discrepancy here, you should compare it to other users in that same group and pull the user’s log file for nVoq Support. 

RandC-timeline-audiolength-v-totaltime-17-0-0

Upload Delay

Upload Delay = delta for Audio Set to Done - (Audio Length *1000)

  • Lower or negative numbers indicate faster audio upload time. 
  • Normally the value of the Upload Delay is negative, which means the dictation was processed in less time than the length of the audio. A large positive value, like a 5-digit number, indicates that it took much more time to process the dictation than the length of the audio. For example, an upload delay value of 20,000 would mean a 20 second delay. A positive upload delay value of four digits represents a delay of at least one second (e.g. a value of 3000 is a delay of 3 seconds).
  • Positive upload delay values may indicate slowness on the customer’s internal system (like their WiFi), but it could be a problem on our end.
  • If you see a large number, you should compare it to other users in that same group. (Is it happening for just one user? Or the whole group?) You should also pull the user’s log file and send that to nVoq Support.


 


What's Next