1. Team Lists

2. Learning Objectives Identify the purpose and use for Teams.
Examine the procedure for setting up a new Team.
Learn how to manage Teams.
Learn about Team Notifications.

3. Purpose and Use
Sending system generated (not user generated) Notifications to a group of users.
For IHS, Teams have proved most useful for sending Consult requests to a group of users

4. Setup Procedure (Cont.)
It is suggested that you prefix your list name with a term related to the function.
Use meaningful and consistent names so others can determine the use of the Team at a later date.
Example: Team that will result Pharmacy Consults can be named “CONSULT PHARMACY” (note you do not need to include the word “Team” in the name).

5. Setup Procedure Created in RPMS: Types: Menu structure.
EHR > BEH > PAT > TEA > CRE
Types:
P PERSONAL PATIENT
TA TEAM PATIENT AUTOLINKED
TM TEAM PATIENT MANUAL
MRAL MANUAL REMOVAL/AUTOLINK ADDITION
Select “MRAL” to create a new Consult Team

6. Setup Procedure (Cont.)
Team Type determines how patients are added and/or removed.
Originally in the VA Teams were designed to manage groups of Patients, but in this case we have no Patients on this team, but are using it to add Providers to the Team.

7. Adding or Removing Providers from a Team
The Team List Management Menu
CRE Create/Add to Team List
DEL Delete Existing List(s)
DPT Display Patients Linked to a User via Teams
DUS Display User's Teams
EXA Examine/Print Existing List(s)
RAL Remove Autolinks
REN Rename Existing List(s)
RPA Remove Patients from a List
RPR Remove Providers from a List

8. Adding or Removing Providers from a Team
In this training we will only discuss the relevant menu options.
There are Team menu options we will not review today.

9. Adding or Removing Providers from a Team (Cont.)
CRE Create/Add to Team List
Menu used to create a new Team.
Also used to add providers to the Team.
DUS Display User's Teams
Can be used for troubleshooting.
EXA Examine/Print Existing List(s)
Used to see current Teams. Important because during Team creation you cannot “question mark” to see what Teams are already created.
Used to see members of a Team.

10. Adding or Removing Providers from a Team (Cont.)
REN Rename Existing List(s)
Used to rename a Team.
RPR Remove Providers from a List
Used to remove providers from a Team.

11. Adding or Removing Providers from a Team (Cont.)
Subscription status.
Determines if users can add and remove themselves to a Team through the GUI.
NO: Users cannot add/remove themselves.
YES: Users can add/remove themselves.
In IHS when used for Consult recipients it is set to “NO.”

12. Team List Maintenance
At your site, you must keep the Team Lists current with the correct Providers on each Team or EHR will not send the correct Notifications to the correct people.
This is an on-going process that must be maintained as staff come and go.
It is suggested you develop a system to keep the Team List maintainer “in the loop.”

13. Notifications
Behavior of notifications, when received by a Team, is setup under RPMS.
EHR > BEH > NOT > PAR > DEL
Setup per individual Notifications.
Determines when notifications received by members of a Team are deleted.
Individual recipients: Notification is deleted only for the individual that reviews one of these notifications.
All recipients: Notification is deleted for all other recipients after only one recipient reviews it.

14. Questions and Discussion