How can I set up dependencies between input forms? (Step 4)

Modified on Fri, 25 Apr at 1:31 PM

In addition to the dependencies between individual input fields within the same input form, you can also create dependencies between input forms.


Step 1: 

  1. Dependencies are created in the study set up under "Step 4. Workflows". To access them, click on the studies module in the top bar.
  2. Search for the study that you wish to edit.
  3. Click on the "Settings" button of your study.
  4. If you are already working within your study and want to update dependencies, click on "Study Settings > Workflows > Scheduled Events" in the sidebar on the left.



Step 2: 


  1. The editing overview of your study opens. Now click on "4. Workflows".
  2. Go to the step for which you would like to create a dependency between the input forms. Click on the pencil-icon to edit.
  3. A pop-up window opens.
  4. Click on the eye symbol of the input form you want to edit. This is where you define the input form's visibility. By default, all forms are visible for the subject.
  5. As soon as a form dependency is set and saved, the icon will become active, indicated by a yellow colour.




Step 3:


First, define the overarching operator that you want to use to combine the different conditions and/or condition groups that you will set up. Two options are available: AND and OR.
  1. If you select AND, the selected form "Inclusion and Exclusion Criteria" will only become visible if ALL of the following conditions are met.
  2. If you select OR, the selected form "Inclusion and Exclusion Criteria" will only become visible if at least ONE of the following conditions is met.
Choose whether you want to set  a condition or condition group.
  1. A condition is based on a single form and condition rule you define.
  2. A condition group enables you to combine multiple condition rules by nesting them within a second-layer operator, allowing for more complex and flexible logic. This is helpful if you want to set an AND/OR dependency (e.g. condition 1 AND (condition 2 OR condition 3) have to be met).
Select the form that builds the basis for the form visibility of the selected form "Inclusion and Exclusion Criteria".
Choose between three different dependency relations. You can set a dependency a) to an input field, b) to the form update timestamp, or c) to the visibility of another form. In most cases, a dependency is set to a specific field or to visibility. If you set a dependency to visibility, this means that this form only becomes visible once the selected form becomes visible.
In case of an input field relation, the next step is to select the input field, condition (and value) which defines the condition. You can also compare the value of the selected field with another field of the same type.
Click "Save dependency" and don't forget to save your changes in the workflow settings as well. 
At any time, you can choose the "Collapse all conditions" option, providing an optimized overview of your set conditions and dependency logic.




Good to know:

  1. In the selection fields, you can search directly for the step, form and field for which you want to add the dependency condition. However, please note that this is case-sensitive.
  2. Dependencies between forms can be set up in a study for scheduled events only.
  3. You can set dependencies on forms within the same study step and/or between forms of other steps in the workflow.
  4. You can set dependencies between visit forms or ePRO forms, or both.
  5. Multiple dependencies are possible; however, be mindful that increased complexity can slow down the application and make your study more difficult to manage.
  6. Similar to field dependencies in a form, you can use dependencies to either display a form or keep it hidden until the specified condition is met.
  7. As with field dependencies in a form, the available condition options depend on the input field type, i.e. the options for "if the value from the chosen field is..." will vary based on whether the field is a "date" or a "single choice," among others.
  8. Forms that are hidden by a dependency will show as "n.a." in the progress overview. The actual form will state that there are "no forms to be filled at the moment".
  9. Be careful when setting up dependencies for ePROs. If you schedule the ePRO send out based on "after at least one form becomes visible", the ePRO weblink will be triggered per schedule and when at least one of your forms within the ePRO step is visible. Refer to the following article for details: How can I edit ePRO settings?
  10. The dependency setup is documented in the annotated PDF export.





Read the following article if you would like to find out what options you have for tab dependencies in our system: All possible tab dependencies





✉️ Still have questions? Feel free to contact your Customer Success Manager or email us at support@climedo.de.




Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article