Conditional dimensions and maps

Another advantage afforded by the use of blueprint maps is the ability to link them together to create conditional logic that controls how they display at the item-level. This means that a dimension can be made available for use on an item depending on the value selected in another dimension to which it is linked.

Consider the example that we would like to record simulated patient age range and sex attributes against our OSCE stations because we need to report that information to our recruitment agency. However, some of our stations don't use a simulated patient at all. Rather than record a "N/A" value for the age range and sex attribute against those stations, we can conditionally display the attributes fields only if an SP is required for the station.

In preparation for the below example we have created 3 dimensions:

Dimension	Type	Values
SP required	Discrete	Yes, No
Age range	Discrete	05-12, 13-18, 18-35, 36-55, 56-70, 70+
Sex	Discrete	Female, Male, Not important

For help on creating dimensions, see the article here.

We have added those dimensions into two blueprint maps.

Map	Dimension(s)
SP required	SP required
SP attributes	Age range, Sex

For help on creating blueprint maps, see the article here.

Linking the maps together

To link the maps together:

• Step 1 of 4

  Navigate to the map you would like to be conditionally displayed (in this case the SP attributes map). Click Edit map.

  

• Step 2 of 4

  Find the map you want to link this to (in this case the SP required map). Click Change.

  

• Step 3 of 4

  Select the category that needs to be chosen for the conditional map to be shown (in this case Yes). Click save.

  

  Multiple categories can be selected from the list. Where more than one value is selected the system uses OR logic, therefore if either of the values are selected the conditional map is shown.

• Step 4 of 4

  Finally, submit and approve the map as normal

  

How linked maps behave at the item-level

At the item-level, if the SP required tag is set to No, then none of the attribute tagging fields are shown.

If, however, the SP required value is set to Yes, the attribute map is also now displayed.