Unclear description of behavior of multiple enableWhen conditions

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive
    • Priority: Medium
    • FHIR Core (FHIR)
    • R4
    • FHIR Infrastructure
    • Questionnaire
    • Hide

      Will revamp the wording to include an explicit reference to enableBehavior.  Will also indicate that an enableWhen clause is satisfied if any of the answers for the specified question match (in the event of the question permitting multiple answers).

      Show
      Will revamp the wording to include an explicit reference to enableBehavior.  Will also indicate that an enableWhen clause is satisfied if any of the answers for the specified question match (in the event of the question permitting multiple answers).
    • Paul Lynch/Stoyan Halkeliev: 6-0-0
    • Clarification
    • Non-substantive

      The current documentation of `Questionnaire.item.enableWhen` includes the following:

      >If multiple repetitions of this extension are present, the item should be enabled when the condition for any of the repetitions is true. I.e. treat "enableWhen"s as being joined by an "or" clause.

      It is very easy to misread this as saying that if you have multiple enableWhen conditions, they will always be joined with an OR (whereas, in fact, this behavior is controlled by `enableBehavior`). As a concrete example of incorrect understanding of the current wording, I offer this Zulip thread started by myself (which also discusses the potential for confusion):

      https://chat.fhir.org/#narrow/stream/179177-conformance/topic/Validator.20problem.20for.20compound.20enableWhen.20clause.3F

       

      I propose that the documentation be updated to make clear

      1. The difference between - and relevant behavior for - the case of (a) an `enableWhen` clause with multiple conditions, and (b) an `enableWhen` clause applied to a question that may have multiple answers.
      2. The link to `enableBehavior`

            Assignee:
            Lloyd McKenzie
            Reporter:
            morten
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: