Clarification on value set update philosophy

XMLWordPrintable

    • Type: EC eCQMs - Eligible Clinicians
    • Resolution: Done
    • Priority: Moderate
    • Component/s: ValueSet
    • Laurie Wissell
    • 802-371-7600
    • Hide
      ​

      When reviewing measure specifications for update the value set that is chosen must be consistent with the reporting period. If a value set is used that is not consistent with the reporting period there is the potential for the measure to fail.
      Additional information regarding Meaningful Use Requirements can be found on the CMS website.
       
      With regard to mapping, measure developers consider all terms within a value set to represent the intended concept. Value sets routinely contain related or hierarchical concepts at varying levels of granularity, to allow implementers to map to those concepts they are either already using within the EHR or those that best represent the data within their system.
       
      If you want to be able to reuse the data in the future, for eCQMs, clinical decision support, or internal quality improvement uses, mappings should be carefully considered and evaluated.
      Show
      ​ When reviewing measure specifications for update the value set that is chosen must be consistent with the reporting period. If a value set is used that is not consistent with the reporting period there is the potential for the measure to fail. Additional information regarding Meaningful Use Requirements can be found on the CMS website.   With regard to mapping, measure developers consider all terms within a value set to represent the intended concept. Value sets routinely contain related or hierarchical concepts at varying levels of granularity, to allow implementers to map to those concepts they are either already using within the EHR or those that best represent the data within their system.   If you want to be able to reuse the data in the future, for eCQMs, clinical decision support, or internal quality improvement uses, mappings should be carefully considered and evaluated.

      I reviewed the CQM Issue Tracker/ CQM-1601: 2015 valueset update and a comment on CQM Issue Tracker: CQM-1642 regarding value set updates during a yearly update to be used in the next reporting year, and I have a question(s) I'm hoping you would clarify.

      Under the Value Set Details, there is a drop-down for Expansion Versions - For Program: CMS MU 2 Update 2017-01-06, MU2 Update 2016-04-01, MU2 Update 2015-05-01, etc... If a value set update is published during a yearly update (2016), why is it that the updates cannot be used until the next reporting year (2017)?

      For example:
      Noted in CQM Issue Tracker/CQM-1642 -
      "It is appropriate to map concepts that meet the clinical intent of the codes listed in the measure where alternative codes are being natively used. It is expected that, if audited, a review would find these codes clinically appropriate to meet the intent of the measure."

      Based on the comment above: Morbid, obesity (disorder), would be clinically appropriate to map to the 'Overweight (finding)' Value Set for the 2016 reporting year - correct?

      The Obesity (disorder) value was added for the 2017 reporting year, therefore Morbid, obesity (disorder) can now be mapped to Obesity (disorder) for more relevance? Or is adding the Obesity (disorder) value more to do with adding the OID and code system for QDM/QRDA alignment for interoperability? Or both?

      There seems to be two ways of looking at the value sets.
      1. Clinically appropriate mapping
      2. Technical development/implementation for interoperability

      Please help clarify?

            Assignee:
            Mathematica EC eCQM Team (Inactive)
            Reporter:
            Laurie Wissell (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved:
              Solution Posted On: