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

include-dependencies wording should clearly indicate intent

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Medium Medium
    • US Quality Measures (FHIR)
    • current
    • Clinical Quality Information
    • Library Data Requirements [deprecated]
      Measure Data Requirements [deprecated]
    • Hide

      To address the issue more generally, we propose removing include-dependencies and include-components parameters, because dependency tracing should always happen. Whether items should be included in the result is a function of the $package operation and addressed in the resolution for J#40219

      Show
      To address the issue more generally, we propose removing include-dependencies and include-components parameters, because dependency tracing should always happen. Whether items should be included in the result is a function of the $package operation and addressed in the resolution for J#40219
    • Juliet Rubini / Bryn Rhodes : 15-0-0
    • Clarification
    • Compatible, substantive

    Description

      The wording of include-dependencies should clearly indicate that if affects what is included in the resulting bundle, not what is done as part of the analysis

       

      Implementers should always recurse the dependencies during the analysis, but this parameter should indicate if those dependencies should be included in the resulting Bundle.

       

      Discussed at Jan 2023 connectathon with Bryn Rhodes

       

       

      Attachments

        Activity

          People

            bryn.rhodes Bryn Rhodes
            mgramigna Matthew Gramigna
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: