Review and provide more information concerning the patient-level Measure Report structure. - 2016-09 cqf #186

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Medium
    • Clinical Quality Information Framework (CQIF) [deprecated] (FHIR)
    • DSTU2
    • Clinical Quality Information
    • MeasureReport [deprecated]
    • MeasureReport resour
    • Hide

      Rather than trying to modify the MeasureReport to support reporting multiple measures, we propose to keep the MeasureReport structure as is, but to make clear that in the case of multiple measures for the same patient, the evaluated resources bundle should be the same bundle to avoid duplicating patient information in the report.

      In addition, the extension indicating which population criteria a resource applies to will indicate the measure as well as the population.

      Show
      Rather than trying to modify the MeasureReport to support reporting multiple measures, we propose to keep the MeasureReport structure as is, but to make clear that in the case of multiple measures for the same patient, the evaluated resources bundle should be the same bundle to avoid duplicating patient information in the report. In addition, the extension indicating which population criteria a resource applies to will indicate the measure as well as the population.
    • Bryn Rhodes/Julia Skapik: 12-0-0
    • Correction
    • Compatible, substantive

      Comment:

      The structure and UML provided in 14.7.3 looks like the patient-level MeasureReport is framed around the measure instead of the patient. QRDA-I reports are framed around the patient such that the data for all measures for which a patient qualifies is submitted in one file. How is it expected that MeasureReports will be submitted when a patient falls into multiple measures (e.g., CMS111, CMS91, etc?)? Will it be based on each measure, rather than as a document containing all data for a single patient?

      Secondary data receivers frequently need all of the discrete data for a patient in order to perform other operations beyond those specified in the measure, such as 'risk adjustment', 'denovo measure development', and 'data quality/interoperability analysis'. Data receivers that are not able to receive actual patient identifiers (e.g., patient's medicare/medicaid numbers) will be unable to recombine a patient's data for this analysis.

      Summary:

      Review and provide more information concerning the patient-level Measure Report structure.

            Assignee:
            Unassigned
            Reporter:
            michelle_dardis
            michelle_dardis
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: