myAvatar Approver (Doc) Routing

If your note type in myAvatar is configured for Approver (Doc) Routing, Bells will use that configuration for approver routing in Bells. When you sign your note in Bells, if the note type selected is configured for approver routing, additional fields show on the sign note display. 

• If the note type is not configured for approver routing, the checkbox for Requires Routing does not display. 
• If the note type is configured but not required for approver routing, the checkbox for Requires Routing shows but is not automatically checked. 
  • If the user does not route the note, the to do in myAvatar is not generated. 
• If the note type is configured and required for approver routing, the checkbox for Requires Routing is checked and is not editable. 
• If the user signing the note has more than 5 approvers available, a search bar will show to help filter out the available approvers to select from.
• If the Require Final Approver setting is false, the Final Approval column will be hidden in Bells. 
• If the user signing the note has routed before, the selection will be auto-populated to the previous user(s) selected for routing if available. 

When the Requires Routing checkbox is checked, the user must search and select at least one approver to route the note to in myAvatar. The user may be presented with additional checkboxes for Require Approval and Final Approval for the note, where applicable. 

• Require Approval means the note is routed to that staff for approval and the note cannot be finalized without that staff approving it. 
• Final Approval means the note is routed to that staff for approval after all other staff have signed the note. 
• Notify Only allows users to select someone to notify in myAvatar. A notifier must be selected along with an approver at this time. 
• If routing is required, the user must select someone else to route the note to. The user cannot select themselves. 
• If routing is optional, the user is allowed to select themselves. The user can also choose to not route at all. 

The Approver Routing details selected show on the preview and print preview displays in Bells. 

The document routing functionality has also been added to the Group Note and Bulk Sign workflows. 

Here is a quick video on how Document Routing works in Bells for myAvatar users. 

Bells Routing Options

Depending on which compatible routing flows are detected, Bells will present the following options during signing: 

• Only Self-Approval flow is detected: 
  • “Assign to approver” checkbox is disabled forced unchecked. User cannot route to their supervisor. 
• Only Supervisor Approval flow is detected: 
  • “Assign to approver” checkbox is disabled forced checked. User must route to a supervisor and cannot self-approve. 
• Both Self-Approval and Supervisor Approval flow is detected: 
  • “Assign to approver” checkbox is enabled and editable. User has a choice of routing to a supervisor or self approving. 

Custom routes are allowed from myAvatar but the organization must use routing NX and only have a single person that the route can end with. 

myAvatar Document Routing Frequently Asked Questions 

Do I have to go back into myAvatar to complete my Bells note?

If you do not use Document Routing in myAvatar, your note is complete when you sign it in Bells and there is no need to go into myAvatar to complete the note.

If you use Document Routing in myAvatar, there will be a To Do for the person the note is being routed to. Your note is complete when you sign it in Bells, there is no need for the note author to go to myAvatar to complete the note. 

For myAvatar, the routing options in Bells are based on these criteria:

myAvatar Form (must have doc routing enabled)

• Patient
• Patient's Episode
• User
  • When user roles are used, user routing privileges are inherited from the roles

For progress notes tied to a myAvatar note type that includes doc routing but the user chooses not to route, a To Do in myAvatar is not generated. 

Additional notes regarding Doc Routing for myAvatar in Bells: 

• We store your routing selection locally to remember who you selected. 
• The next time you write a note, we do the live call to get the list of suggested approvers from myAvatar. 
• If the locally-saved user from the previously routed note isn't in the list of suggested approvers from myAvatar, Bells won't select them as a default. 
• For the PDF that is generated, the Header is the Provider Name from the Facility Defaults Form on the PM side of myAvatar.