Group Nesting

Why do we nest groups? Group nesting reduces the number of administrative actions necessary with regard to group membership(s), permission(s), and access to specific Vocera feature sets. The following figure shows an example of nested groups:

Figure 1. Nested groups Nested groups

The E D departmental group would only have listed on the members tab in the Administration Console: E D Nurse, E D Patient Care Tech, E D Physician, and E D Nurse Manager.

The E D LPN group may be nested in the E D Nurse group as they would typically be expected to respond to the same broadcasts as an E D Nurse.

The E D Resident group is nested in the E D Physician group allowing them to receive calls, broadcasts, and messages to the E D Physician group.

It is not required to nest the E D Charge Nurse group within the E D Nurse group. The members of the E D Charge Nurse group (in this example) are already an E D Nurse or they would not have the ability to add themselves to the E D Charge Nurse group. It may be desirable to nest it within the E D departmental group for purposes of understanding and compartmentalization.

The E D Nurse Manager is NOT nested in (a member of) the E D Nurse group as this is typically a person who has hired for/promoted to this managerial role and will typically not be providing direct patient care or want to receive calls destined for the E D Nurse group. Even though the E D Nurse Manager is not nested within the E D Nurse group, they can still be notified of situations within the department.