Should we replace candidateExpression with answerExpression or keep it?

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive
    • Priority: High
    • Structured Data Capture (SDC) (FHIR)
    • current
    • FHIR Infrastructure
    • Candidate Answers Expression
    • Form Population
      Using Expressions
    • Hide

      Group agrees that we need both.  We will update the specification to make clear the distinct uses of each and include an example of what a user-interface might look like for an element that contains both extensions to help make it clear.

      Show
      Group agrees that we need both.  We will update the specification to make clear the distinct uses of each and include an example of what a user-interface might look like for an element that contains both extensions to help make it clear.
    • Paul Lynch/Joee Garcia: 10-0-0
    • Clarification
    • Non-substantive

      There are conflicting resolutions on some tickets regarding candidateExpression and answerExpression. There are tickets that agree on removing candidateExpression (https://jira.hl7.org/browse/FHIR-21332, https://jira.hl7.org/browse/FHIR-27815), but according to Lloyd, we need to discuss this more as there might be instances that we might still have both.
      For example, imagine that the base question says "Please list any potentially related concomitant drugs" and the answer is constrained to "all Health Canada DINs". I.e. there's an answerValueSet. (Alternatively could be an answerExpression that says "all drugs currently listed in Server X's repository.) However, as part of the 'population' enhancement to the form, we want to include a lookup that lists the patient's currently active drugs as a 'candidateExpression'.
      We need to discuss more about the interplay between them. (In practice, there could be interplay between some of the others in terms of "what's allowed" vs. "what's displayed" vs. "what's suggested".)

      Related Tickets on candidateExpression and answerExpression:
      FHIR-28386
      FHIR-28081
      FHIR-27815
      FHIR-25960
      FHIR-21400
      FHIR-21332
      FHIR-20820
      FHIR-26990
      FHIR-20396

            Assignee:
            joeegarcia
            Reporter:
            joeegarcia
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: