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

Expression should support operations

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Highest Highest
    • FHIR Core (FHIR)
    • R5
    • FHIR Infrastructure
    • Metadata Types
    • 2.1.27.6.0.6
    • Hide

      1. We will move the definition of x-fhir-query into the FHIR core specification (from SDC - http://build.fhir.org/ig/HL7/sdc/expressions.html#x-fhir-query-enhancements)
      2. We will ensure the definition of x-fhir-query covers URL-invocable operations as well
      3. We will define a new %??? variable similar to %terminologies that allows the invocation of StructureMap/$transform and any additional R5 operations that require 'body' parameters that we feel would be useful in expressions and/or FHIRPath.

      • need further discussion about what those operations should be and what the variable (or variables) should be called. Will take this on as part of the editing.
      Show
      1. We will move the definition of x-fhir-query into the FHIR core specification (from SDC - http://build.fhir.org/ig/HL7/sdc/expressions.html#x-fhir-query-enhancements ) 2. We will ensure the definition of x-fhir-query covers URL-invocable operations as well 3. We will define a new %??? variable similar to %terminologies that allows the invocation of StructureMap/$transform and any additional R5 operations that require 'body' parameters that we feel would be useful in expressions and/or FHIRPath. need further discussion about what those operations should be and what the variable (or variables) should be called. Will take this on as part of the editing.
    • Bas van den Heuvel/Bryn Rhodes: 12-0-2
    • Enhancement
    • Compatible, substantive
    • R5

    Description

      The Expression resource should be extended with support the calling FHIR operations. Many operations are usefull, the following ones are specifically interesting:

      • StructureMap/$transform
      • ActivityDefinition/$apply

      This can be done by allowing operations to be called as a x-fhir-query and/or by adding an additional language (in http://hl7.org/fhir/ValueSet/expression-language).

      In both cases additional explanation is required in what way the input parameters are passed (default as part of the URL, preferably also as additional included parameter resource).

      Attachments

        Activity

          People

            Unassigned Unassigned
            bvdh Bas van den Heuvel
            Bas van den Heuvel
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: