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

Expressions must be able access parameter fields.

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Medium Medium
    • FHIR Core (FHIR)
    • R4
    • Clinical Decision Support
    • ActivityDefinition
      PlanDefinition
      Questionnaire
    • Hide

      Add discussion about how PlanDefinition/$apply and ActivityDefinition/$apply allow for access to the parameters of the operation, and suggest this as a general pattern for operations that support evaluation of logic.

      Show
      Add discussion about how PlanDefinition/$apply and ActivityDefinition/$apply allow for access to the parameters of the operation, and suggest this as a general pattern for operations that support evaluation of logic.
    • Abdullah Rafiqi/Ben Hamlin: 19-0-0
    • Enhancement
    • Non-substantive
    • R5

    Description

      The FHIR specification supports different operations that require evaluating expressions with FHIRpath and/or CQL expressions. These expressions require access to the context of the operation meaning the parameters provided.

      I suggest to add a generic section on Expression generation and state in there that all parameter fields will be accessible as enviroment variables.

      %param --> Parameter resource

      In the case of ActivityDefinition.$apply, this will result in the following environment variables: %activityDefinition, %subject, %encounter, %practitioner, %organization, %userType, %userLanguage, % userTaskContext, %setting, %settingContext.

       

      Attachments

        Activity

          People

            bryn.rhodes Bryn Rhodes
            bvdh Bas van den Heuvel
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: