Overlap between initialExpression and itemContext

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive
    • Priority: High
    • Structured Data Capture (SDC) (FHIR)
    • STU3
    • FHIR Infrastructure
    • (profiles) [deprecated]
    • 12.37.1
    • Hide

      Make clear (at least for now) that itemContext does NOT set an answer (where question type is 'reference') but instead sets context for use with initialExpression. Raise an open issue about whether itemContext should be able to auto-populate the answer to a question and, if so, what the rules should be around when that should happen. Also provide more of an explanation about the relationship between itemContext and initialExpression.

      Show
      Make clear (at least for now) that itemContext does NOT set an answer (where question type is 'reference') but instead sets context for use with initialExpression. Raise an open issue about whether itemContext should be able to auto-populate the answer to a question and, if so, what the rules should be around when that should happen. Also provide more of an explanation about the relationship between itemContext and initialExpression.
    • Clem McDonald/Paul Lynch: 4-0-0
    • Clarification
    • Non-substantive

      There seems to be some overlap in the funtionality provided by initialExpression and itemContext. Both can be used for prepopulation of resources. I would like to see some guidanance about on the two extensions pages about when one should be preferred over the other.

      Differences that I can see:

      1) initialExpression does not limit itself to resources, as itemContext does. (Well, at least the description says it is for resources, but I don't see a constraint that enforces that.)

      2) itemContext is used for both prepoulation and extraction.

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

              Created:
              Updated:
              Resolved: