External Variables

Using External Fields to Reference Within Conditional Actions (cross-form logic)

External variables allow users to define fields outside the current form along with the interval that the field should be evaluated in, and for use with a conditional action in the current form.  These can only be done using a Web Browser.

Common examples:

• Hide a form based on data entered in another form

• Compare a date in one form against a date in another form

Define External Fields

Locate the External Variables option under the Study menu on the web or app.

Web browser:

Mobile App:

This will open the table of existing variables and an option to add new variables with the parameters defined below.

1. Name - The name designated for the external field can be anything.  However, the name should describe the form and the field itself. This makes it easy to pick out the fields when there are lots of defined external fields.

2. Type - Currently, the only selection available in the dropdown list is External Fields. However, the ability to add other types of fields in the future is possible. For now, simply select External Field.

3. Form  - Select the form where the external field resides from the list presented.

4. Field - Once a Form has been selected, all the fields defined in that form will populate the field dropdown. Select the field to use externally.

5. Interval The interval tells the system where exactly to retrieve the data for the external field when evaluating the conditional action expression. Here is a list of the Interval options to identify the data needed from a form:

• Visit Interval Names

  All visits will be listed to choose from. For example, if you need to reference the Physical exam date at the 6 month follow up visit.

• Unscheduled 

  The latest record ID for the defined form wherever it is not collected in a visit schedule. This is most commonly used for the Registration form where there is only one record being collected for the form.

• Previous Interval 

  The closest visit date record before the current visit interval where the expression is being evaluated. 

• Previous Entered Form 

  The latest Record ID for the defined form wherever it's collected - both in scheduled visits or unscheduled visits. If the expression is evaluated in a CA on the same form, it will get the latest record ID prior to the current record ID. An example would be to check for a continual increasing value over time - such as a Subject's age, or an adverse event sequence number. If the current record is new and not yet saved, the system will get the literal latest record ID of the target form.

• Same Visit 

  Gets the value from the defined form only if the CA is being evaluated in a scheduled visit where that form also exists.  

• Any Record

  Gets the values for all records of the defined field and then compares all of those values in the condition where it is used

  Using this in a conditional action

  When this variable is used, it needs to be the FIRST criteria of the condition.

  For example:

  OKAY: If <External> is greater than a field on the current form.

  NOT OKAY: If <field on current form> is less than <External>

• Parent

  Gets the value from the record that is the parent of the current record (if applicable). If the current record where this external is used does not have a parent, the condition will not run.

Using External Fields

Select from the list of available external variables created in the previous steps above.

When comparing an external variable to another field, the system will limit to comparing fields only of similar types. For example, if the external is a date field, it can be compared to dates and numbers, but can't be checked to make sure its not equal to a choice field.

Two-way edit checks: If a form, "Form A", containing an external variable is saved, and another form "Form B" contains an edit check referring back to Form A, then a query has potential to open on Form B - even if the user is not saving Form B. This is a very helpful function to catch data errors when any of the dependency values are changed.

Deleting External Variables

Export External Variables

The list can be exported, along with all dependencies for record keeping purposes, along with the conditional actions data dictionary for a complete picture of how cross-form logic has been designed.