Uploaded image for project: 'eCQM Issue Tracker'
  1. eCQM Issue Tracker
  2. CQM-5087

Inconsistencies in the application and definition of NormalizeInterval

XMLWordPrintable

    • Icon: EC eCQMs - Eligible Clinicians EC eCQMs - Eligible Clinicians
    • Resolution: Answered
    • Icon: Moderate Moderate
    • None
    • None
    • Nisarg Khandekar
    • Hide
      ​Thank you for your inquiry about the "NormalizeInterval" function for CMS56v10, CMS66v10, and CMS127v10. We will consider applying the "NormalizeInterval" function consistently to all three measures during a future annual update cycle.
      Show
      ​Thank you for your inquiry about the "NormalizeInterval" function for CMS56v10, CMS66v10, and CMS127v10. We will consider applying the "NormalizeInterval" function consistently to all three measures during a future annual update cycle.
    • CMS0056v10, CMS0066v10

      We can see that NormalizeInterval in being used inconsistently across eCQMs for the same data elements (e.g. Procedure, Performed).
      NormalizeInterval function is used for Procedure, Performed for 134v10, 165v10, 130v10, etc. 

      • For CMS56v10, we are seeing that 
        The definition for 'Total Hip Arthroplasty Procedure, uses NormalizeInterval function for Procedure, Performed, which means one can use either RelevantPeriod or RelevantDateTime.
      • But when  'Total Hip Arthroplasty Procedure' is used in 'Has THA with Initial and Follow Up HOOS Assessments, the CQL is expecting only RelevantPeriod.
      • These are conflicting requirements

      Same is the case with CMS66v10.

      Similarly in CMS127v10, "Procedure, Performed": "Pneumococcal polysaccharide vaccine, 23-valent (PPSV23), adult or immunosuppressed patient dosage, when administered to individuals 2 years or older, for subcutaneous or intramuscular use" requires RelevantDateTime only. NormalizeInterval is not used in this scenario.

      The above inconsistent requirements within the same data elements seem to be in contradiction to the intent of introducing NormalizeInterval - ease burned on healthIT developers.

      Will these inconsistencies be rectified in the near future, in the form of a patch to the eCQM specifications?

         

            edave Mathematica EC eCQM Team
            knisarg Nisarg Khandekar (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved:
              Solution Posted On: