Conditional Actions - Hide

Hiding and Unhiding a Form or Data Field During Data Entry

Fields can be hidden based on data entered (or not entered) either on the current form or other forms (via external variables). This is also known as “Skip Logic”, used to focus data entry only on what is needed so the data entry user is not sifting through irrelevant content.


Hiding a Field

There are three ways a field can be hidden:

  • Conditional hiding - Prevents users from entering data on irrelevant fields. This method is covered in this article.
  • The 'Hidden' field property - Hides a field at all times for all users, but can still compute or populate data behind the scenes
  • Field Blinding - Hides the field only for specific users, but can still contain data

Conditional hiding of a field will, by default, cause the data to be cleared if data exists in the field before it becomes hidden. In the example below, if data is saved in the 'Specify' field, that data will be removed if the field later gets hidden by the user changing their answer.

Conditionally hidden forms will not clear data.


Make the field's label follow what the field is doing

It's important to consider the field's label too. If a field is hidden or blinded, and that field has a  text label along with it, you most likely want the label to also do what the field is doing. 

To accomplish this, each label has a "field" property where the label can be attributed to the field it's part of.

Building a Hide Condition

For a Hide condition, a common example is to collect further details based on a prior response. That prior response is often in the same form, but does not need to be (read more about external variables).


In the example shown above, the conditional action is set up on the Specify field. The operator is set as “Not Equal” because the field where the action is being written needs to be hidden at all times until the Race field has “Other” selected during data entry.


Hiding a Field Based on Choices Made in a Multi-select Field

The operators in a multi-select field work differently because there is no exact value to use as a trigger. A user could select one, some, or all choices. For this reason, the operators in a multi-select field are “in” and “not in” - meaning “includes” and “does not include”.

In this example, a ‘Specify’ field only needs to be displayed if the user selects the choices Mexico or Other, or both. So the condition should be to Hide if the multi-select field does NOT include the value 4 or 9 (coded values for the choices Mexico and Other):




Hiding a normalized table

Normalized tables can be conditionally hidden as well, the process of setting it up is just like that of any field. Select the table and then the conditional action builder.

Hiding Tabs/Pages On a Form

Hidden Tabs are often used when a form contains multiple tabs, but some tabs aren’t applicable and don’t need to be accessible for data entry.

To hide a tab, define a Hide CA on any field (usually the first one) within the tab that needs to be hidden. Second, name the conditional action starting with this syntax: {Tab

Here's an example:

Hiding Forms and Visits

Both forms and entire visits can be conditionally hidden. This is helpful for only collecting the forms that are relevant to the current subject. A common example is a Pregnancy Test form being hidden for any subject that is not female.

To hide a form, the condition must be an external variable collected on some other form or visit. In this example "Gender" is an external variable from the Demographics form at a specified visit. The conditional action is written at the Form level, rather than field level.

Additionally, if an entire visit needs to be hidden, apply the same Hide condition to all forms within the visit. This can be done by copying and pasting to the other forms. For visit-based hiding, the condition needs to include criteria for the visit as part of the condition.

Be cognizant of how much form hiding is being done within the study. Having a large number of forms hiding based on all kinds of various conditions will start to impact the speed of the system when Clinicians open subject casebooks. This is because the system needs to process through all the hiding logic to determine which forms to display.