Add conformance languge concerning the types of expression languages

XMLWordPrintableJSON

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

      Will update the specification to indicate that implementations SHALL - in the text of their CapabilityStatement - declare what expression languages they support.  Will also note that future versions of SDC may define a formal mechanism to express what expression languages are supported in a computable manner.

      Will also add language that indicates that if a system receives a questionnaire that contains expressions in a language it doesn't support, what it should do depending on where the extension appears (not a problem for populate/extract, but is a problem for stuff like enableWhen).

      Show
      Will update the specification to indicate that implementations SHALL - in the text of their CapabilityStatement - declare what expression languages they support.  Will also note that future versions of SDC may define a formal mechanism to express what expression languages are supported in a computable manner. Will also add language that indicates that if a system receives a questionnaire that contains expressions in a language it doesn't support, what it should do depending on where the extension appears (not a problem for populate/extract, but is a problem for stuff like enableWhen).
    • Paul Lynch/Stoyan Halkaliev: 8-0-0
    • Clarification
    • Non-substantive

      The page http://build.fhir.org/ig/HL7/sdc/expressions.html#expression-extensions lists for each extension which of the Expression languages (FHIRPath, CQL, or x-fhir-query) can be used.  Some language should be added to clarify whether an SDC system is expected to support all of those types.--

            Assignee:
            Lloyd McKenzie
            Reporter:
            Paul Lynch
            Paul Lynch
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: