myAvatar and Bells

Which myAvatar patch updates do I need for Bells? 

When requesting patches from myAvatar, these are the patches Bells requires:

• CWS 2022: 70,85
• CareFabric 2022: 31, 32, 38, 41, 42, 49, 50, 81, 97
• CareFabric 2023: 6, 19, 28, 29, 39, 48, 69, 71
• CareFabric 2024: 6, 7, 14, 16, 18, 27, 31, 33
• RADPlus 2022: 46, 62

Once your organization has installed these updates, please request the feature to be enabled in Bells. 

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 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. 

For the PDF that is generated, the Header is the Provider Name from the Facility Defaults Form on the PM side of myAvatar. 

My appointment times don't match between Bells and myAvatar? Why are they different?

This is due to using the default registry setting for scheduling in myAvatar. Our recommendation is to have your Bells administrator set the following registry settings for myAvatar. In our tests, we saw no impact to the user experience in Avatar.  

Time Zone settings must be configured on the Site Registration form in myAvatar. The last field of the Site Registration section on the form is a field called Time Zone to select the appropriate value.  

Help! I'm writing a note and I don't see any Service Codes, not even when I click Show All.

The list of service codes you see when you start a note is dependent on a combination of Visit Date + Patient + Enrollment + Program. When you start the note, Bells gets the list of valid service codes for that combination of fields directly from myAvatar. If you don't see it in Bells, it's because myAvatar says it's not an allowed service type for those factors.

Where does my email come from in myAvatar? 

For myAvatar users, the email address comes from the user definition, supplemental section, Organization email field where applicable. This may be hidden for your organization in myAvatar. Bells administrators can add an email for users in Bells via the Send Invite functionality on the User Management display when a user does not have an email in Bells. 

My locations aren't filtering based on the program! Is there a setting that can fix it?

There is a registry setting in myAvatar called "Activate Program/Location Filter Registry Setting Value" that will filter your locations based on program for your notes in Bells. 

Oh no! My notes in myAvatar are showing in Draft! 

There is a registry setting in myAvatar that can be changed to assist with this called Clear Selected Client After Filing. It clears the client from the encounter after filing the note. Changing the setting from Y to N should resolve the draft note issue. 

My users are showing as deactivated in Bells, but are active in myAvatar. 

If a user is showing with the Bells Enabled tag struck through on the User Management display, this can mean the user definition in myAvatar didn't pick up the correct dates and just needs a re-save or the sync isn't able to grab the latest data. When this happens, follow these steps:

Steps: 

• Resubmit the user definition and the practitioner enrollment in myAvatar
• Press the Resync menu option on the Bells' User Management display for the user(s). 
  • 

That should resolve the struck out Bells Enabled tag from showing.  

Launching Bells from myAvatar

This code can be imported into myAvatar to launch Bells AI from a widget: bells launch widget.xml

Term Crosswalk

Bells offers several labels that can be substituted within the application. This means you can change them to whatever is appropriate for your organization.

They include:

• Patient
• Location
• Session
• Problem