Creating Group Templates and Normalizers for Units / Creating Group Templates for Units |
Because role-based group names are so systematic, you can use templates to filter out the Vocera Voice Server groups whose assignments you will not maintain in CTS. These templates are specified with a simplified regular expression notation when you add a unit.
About Group Naming Conventions describes the patterns that are typically found within the names of role-based groups on the Vocera Voice Server. It is easier to visualize the individual components of this systematic pattern by representing the group name data in tables such as the following:
Room | RoomNumber | Bed | BedNumber | RoleName |
---|---|---|---|---|
Room | E 1 0 1 | Bed | 1 | Nurse |
Room | E 1 0 1 | Bed | 1 | PCA |
Room | E 1 0 1 | Bed | 2 | Nurse |
Room | E 1 0 1 | Bed | 2 | PCA |
Room | E 1 0 2 | Bed | 1 | Nurse |
Room | E 1 0 2 | Bed | 1 | PCA |
Room | E 1 0 2 | Bed | 2 | Nurse |
Room | E 1 0 2 | Bed | 2 | PCA |
Room | RoomNumber | Bed | BedNumber | RoleName |
---|---|---|---|---|
Room | E 2 0 1 | Bed | 1 | Nurse |
Room | E 2 0 1 | Bed | 1 | PCA |
Room | E 2 0 1 | Bed | 2 | Nurse |
Room | E 2 0 1 | Bed | 2 | PCA |
Room | E 2 0 2 | Bed | 1 | Nurse |
Room | E 2 0 2 | Bed | 1 | PCA |
Room | E 2 0 2 | Bed | 2 | Nurse |
Room | E 2 0 2 | Bed | 2 | PCA |
In the above tables, notice that the values in columns 1 and 3 do not vary—they are constants. Notice also that while the values in columns 2 and 4 vary, they do so systematically—column 4 contains a numeric value, and column 2 contains a string and a numeric value. Finally, the values in column 5 vary, and it contains only strings.
The template regular expression notation accommodates all these variations. Templates may contain three types of parts, as shown in the following table:
Template Part Type | Template Part Syntax | Template Examples | Allows |
---|---|---|---|
Constant |
{Value} |
{ICU} {Room} |
ICU Room |
String |
{$VarName} |
{$Role} |
Nurse PCA |
Numeric |
{$VarName#} |
{$Room#} |
1 2 |
As you can see from the examples in the above table, values enclosed in curly braces ( { } ) are template parts. Values that are prefixed with a dollar sign ( $ ) are variables, and values appended with a hash ( # ) are numeric parts.
Numeric and string template parts may contain up to two modifiers enclosed in parentheses, shown as (m,n) in the syntax table below. In this syntax notation, the modifiers are defined as follows:
Template Part Type | Template Part Syntax | Template Examples | Allows |
---|---|---|---|
String |
{$VarName(m,n)} |
{$Role(1,2)} |
Nurse PCA (but not "P C A") |
Numeric |
{$VarName#(m,n)} |
{$Room#(1,3)} |
1 5 1 7 |
Modifiers for numeric and string template parts may include an optional range, specified as follows.
Template Part Type | Template Part Syntax | Template Examples | Allows |
---|---|---|---|
String |
{$VarName('x' 'y'... 'z',m,n)} |
{$Role('Nurse' 'PCA',1,2)} |
Nurse or PCA only (not LPN or "P C A") |
Numeric |
{$VarName#([xxx-yyy],m,n)} |
{$Room#([32-45],1,3)} |
32 to 45, inclusive |