Uploaded image for project: 'FHIR Specification Feedback'
  1. FHIR Specification Feedback
  2. FHIR-33057

que-14 precludes setting answerConstraint when using answerExpression extension

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Medium Medium
    • FHIR Core (FHIR)
    • R4
    • FHIR Infrastructure
    • Questionnaire
    • Hide

      Change this to a warning.  In the invariant, reword to "Should only have answerConstraint if answerOption or answerValueset are present.  This won't apply if there's an equivalent extension - e.g. answerExpression"

      Also, in the SDC profile on Questionnaire, will override the invariant to specifically check for answerExpression too.

      Show
      Change this to a warning.  In the invariant, reword to "Should only have answerConstraint if answerOption or answerValueset are present.  This won't apply if there's an equivalent extension - e.g. answerExpression" Also, in the SDC profile on Questionnaire, will override the invariant to specifically check for answerExpression too.
    • Brian Postlethwaite/Paul Lynch: 6-0-0
    • Correction
    • Compatible, substantive
    • R5

    Description

      We definitely want to be able to have open vs. closed even if the answers are coming from an expression.  We need to re-evaluate how this invariant works, or maybe soften to a warning.

      Attachments

        Activity

          People

            lloyd Lloyd McKenzie
            lloyd Lloyd McKenzie
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: