Routing Dictation

Dictation uploaded can be routed with special rules. Contact your MIE Implementer if you wish any dictation that uploads to be routed to a specific user (transcriptionist), for a specific job type, etc. Many different routes (rules) can be programmed to look at uploaded/incoming dictation. Please contact your MIE Implementer for help.

You must have security access to Routing Tab Access set to Yes. If you are set to no, you will not even see the Routing tab in the Dictation sidemenu tab. If you have security access to the Routing tab, you will see the Routing tab at the top of the Dictation sidemenu tab feature.

The routing can be set up in Enterprise Health and to view any existing dictation routing rules can be viewed by clicking the sidemenu tab named DICTATION, then click the ROUTING tab at the top.

Your practice’s existing active dictation routing rules will display. These rules can automatically route specific dictation job types and by specific dictators who created the dictation to a specific transcriptionist if you have routing rules set up.

Dictation can be routed regardless if it’s uploaded via phone or from within Enterprise Health . Routing rules are processed in order of priority and searching for another rule stops when one rule matches the dictation.

Add Dictation Route

You can add a dictation route if you are familiar with html where clauses. Otherwise, please contact your MIE Implementer and let them know what you want routed and they can set up for you.

To add a dictation route, simply click the Add Dictation Route link found in the Dictation Routing tab.

The Add Dictation Route fields will open on your screen.

  • Route ID: This is automatically set internally with programming within the software. Enterprise Health will give the new route a specific route ID that it tracks and works from.
  • Priority: Set the priority of the rule. The higher the number, the higher the priority level the rule will search dictation for. This is not the priority of the dictation the dictation is set at; this is the priority of the dictation route that the system should search the dictation for and the higher the route priority is the route that will be searched for first. As soon as it finds a dictation that matches a route rule, it will stop and follow that dictation into that route rule.
  • Comment: Must type out exactly what this route rule is searching for and who it’s routed to and what the route rule is doing/searching for. This helps users see what the route is set for. This is a required field and you must type comments here.
  • Where Clause: Enter in the html where clause of what the rule is to look for. Contact your MIE Implementer to set this up. If the html where clause is invalid, it will tell you that and not allow you to save the route.
  • Set Clause: Enter in the html set clause of what the rule is to do once a dictation is found that matches this rule. Contact your MIE Implementer to set this up. If the html set clause is invalid, it will tell you that and not allow you to save the route.

Click the ADD ROUTE button once you have the route programmed. For help programming dictation routes and making sure correct priority of the rule is looked at, please contact your MIE Implementer.

You can also edit or delete routes that exist using those links in the options column.

Examples of Routes

This example shows a high priority rule set to look for any uploaded dictation set as priority 2 and priority 3 and will route those specific priority 2 & 3 dictations to user Judy Sample (user id#1122). The priority is set at 3 for the ‘route’ because the higher the route priority, the higher the rule is placed to look for that dictation rule on dictations that are uploaded. The comment explains what this route rule is looking for and what it will do. The Where Clause is the html where clause that looks for the uploaded dictation priority that is set on the specific dictations. The Set Clause is the html set clause that assigns the uploaded dictation that it found (that matches this rule) and assigns it specifically to user #1122.

This dictation route example below shows an example of all dictation uploaded by Dr Sample (user ID #1110) will be assigned to transcriptionist user Margaret Beam (user id#2221). Their ID number is found in their username screen in control tab. All of Dr Sample’s dictations will be routed and assigned to Margaret Beam to transcribe. These dictations will be placed/assigned then to her and placed in her pending queue to transcribe because of this route rule.

This dictation route example below shows an example of all dictation uploaded as job type 6 (LETTER doc.type) is to be assigned to transcriptionist Penny Hall (user ID# 1010). All dictations uploaded as job type #6 will be assigned to Penny Hall to transcribe and assigned to her and only show in her pending queue to transcribe.

Enterprise Health Documentation

Last Updated:

Last Build: Tue, 18 Jun 2024 18:57:46 EDT
WikiGDrive Version: dd69069d725fca5f553df7ded62e130a49d49ca6