Issues around Expression.language and Expression.expression

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Medium
    • FHIR Core (FHIR)
    • R5
    • FHIR Infrastructure
    • Measure
      PlanDefinition
    • Hide

      We will make Expression.language 0..1 instead of 1..1 and add an invariant that language must be present if Expression.expression or Expression.reference are present.

      Will clarify that if Expression.expression and Expression.reference are both present, the Expression.expression might just be a name pointing something within the referenced content.

      Show
      We will make Expression.language 0..1 instead of 1..1 and add an invariant that language must be present if Expression.expression or Expression.reference are present. Will clarify that if Expression.expression and Expression.reference are both present, the Expression.expression might just be a name pointing something within the referenced content.
    • Correction
    • Non-substantive

      Expression.language is required, but Expression.expression is not, and the language defines the language of the expression. So what does it mean to have a language such as text/cql but no actual expression in that language? Should we require expression, or maybe make language optional? 

      Also, I would assume that it would be legal to have an expression that is in plain text (i.e. a non-computable, potentially psychometric question). I know the binding for language is extensible, but should be add text.plain to the existing value set? 

            Assignee:
            Unassigned
            Reporter:
            Rick Geimer
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: