🐛 Bug report: Missing enableWhenBehavior for items with multiple enableWhen, resulting in incorrect questionnaire behaviour when used with Spezi

[lukaskollmer]

Description

The FHIR spec says that "If there are more than one enableWhen, enableBehavior must be specified".

However, this is not the case for questionnaires created using phoenix; by default adding multiple enableWhens does not also add an enableBehavior field. The field is only added once the user changes the "at least one condition / all conditions must be fulfilled" radio button.

Reproduction

1. Add multiple conditions to a question
2. See that the "At least one condition must be fulfilled" option is selected by default
3. Preview/Download the JSON for the questionnaire
4. See that there is no enableBehavior field for the item.

Expected behavior

the behaviour should follow the specification

Additional context

This is actually kinda bad, because the default selection in the UI is for the any option, whereas ResearchKitOnFHIR currently defaults missing enableBehavior fields to .all, meaning that if a user were to create a conditional question using the website, with the intention of requiring any of the conditions to be true, saw that option already selected, exported the questionnaire without changing this option, and then imported the JSON into Spezi, it would result in an incorrect questionnaire behaviour (requiring all conditions to be true instead of just a single one).

Code of Conduct

• I agree to follow this project's Code of Conduct and Contributing Guidelines