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

Clarify the use of the valueFilter extension

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive
    • Icon: Medium Medium
    • US Quality Measures (FHIR)
    • 5.0.0-ballot [deprecated]
    • Clinical Quality Information
    • CQFM Value Filter [deprecated]
      EXM Measure
    • Hide

      Agree with the URL approach outlined in the tracker description (regarding the example of the valueFilter extension) and use rendered value extension (https://hl7.org/fhir/extensions/StructureDefinition-rendered-value.html) with the slice name. 

      When an extension is referenced as part of a data requirement, it is included in the mustSupport list (Library.dataRequirement.mustSupport) using a FHIRPath extension reference. In addition, the mustSupport list will include a rendered-value extension with the slice name of the extension.

      When it renders in the human readable it will read 'ethnicity' (this is the actual slice name from the US Core Patient profile) but in the mustSupport value it will read extension(" http://hl7.org/fhir/us/core/StructureDefinition/us-core-ethnicity ")

      In addition, update the example to reference the QICore profile, rather than base patient, so that the path is resolvable on the profile

      In addition, include another example (such as a reference to a Lab with a quantity comparison) that provides a simpler illustration of the valueFilter extension on a data requirement.

      Note that the cqfm-valueFilter extension has been moved to the base Extension Pac. So needs to use the one from the base Extension Pac instead of cqfm-valueFilter. 

      Add guidance describing this in the dataRequirement.comment field (https://hl7.org/fhir/us/cqfmeasures/2024Jan/StructureDefinition-module-definition-library-cqfm-definitions.html#key_Library.dataRequirement) The change will be applied in CRMI because this profile will be moved to CRMI from QM IG. 

      Show
      Agree with the URL approach outlined in the tracker description (regarding the example of the valueFilter extension ) and use rendered value extension ( https://hl7.org/fhir/extensions/StructureDefinition-rendered-value.html)  with the slice name.  When an extension is referenced as part of a data requirement, it is included in the mustSupport list (Library.dataRequirement.mustSupport) using a FHIRPath extension reference. In addition, the mustSupport list will include a rendered-value extension with the slice name of the extension. When it renders in the human readable it will read 'ethnicity' (this is the actual slice name from the US Core Patient profile) but in the mustSupport value it will read extension(" http://hl7.org/fhir/us/core/StructureDefinition/us-core-ethnicity  ") In addition, update the example to reference the QICore profile, rather than base patient, so that the path is resolvable on the profile In addition, include another example (such as a reference to a Lab with a quantity comparison) that provides a simpler illustration of the valueFilter extension on a data requirement. Note that the cqfm-valueFilter extension has been moved to the base Extension Pac. So needs to use the one from the base Extension Pac instead of cqfm-valueFilter.  Add guidance describing this in the dataRequirement.comment field ( https://hl7.org/fhir/us/cqfmeasures/2024Jan/StructureDefinition-module-definition-library-cqfm-definitions.html#key_Library.dataRequirement) The change will be applied in CRMI because this profile will be moved to CRMI from QM IG. 
    • Karl Naden / Bryn Rhodes : 24-0-0
    • Correction
    • Non-compatible

    Description

      The example of the valueFilter extension (extracted below from MeasureEXM) needs additional explanation or updates.

       

      {
   "extension" : [{
      "url" : "path",
      "valueString" : "url"
   },
   {
      "url" : "comparator",
      "valueCode" : "eq"
   },
   {
      "url" : "value",
      "valueString" : "http://hl7.org/fhir/us/core/StructureDefinition/us-core-ethnicity"
   }],
   "url" : "http://hl7.org/fhir/us/cqfmeasures/StructureDefinition/cqfm-valueFilter"
 }],
 "type" : "Patient",
 "profile" : ["http://hl7.org/fhir/StructureDefinition/Patient"],
 "mustSupport" : ["url",
 "extension",
 "value"]
}

      In this example, the filter appears to be on the element `url`, but `url` is not an element of the Patient resource. It seems to be trying to say that the “us-core-ethnicity” extension is required. If so, shouldn’t the path (both in the must support list and the extension) be extension.url? Or better, couldn’t the requirement be expressed using FHIR path: extension(“http://hl7.org/fhir/us/core/StructureDefinition/us-core-ethnicity”).value? This is in-line with the definition of the entries in the mustSupport list, which includes the simple FHIRPath subset that includes the .extension(“url”) function.

      If you agree that this example should use a mechanism other than the valueFilter extension, please provide another example of the valueFilter extension that illustrates a valid use.

       

      Attachments

        Activity

          People

            abdullah.rafiqi@icf.com AbdullahRafiqi
            karlnaden Karl Naden
            Watchers:
            7 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: