Need understanding for Numerator in CMS60 & CMS53

XMLWordPrintable

    • Type: Annual Update
    • Resolution: Duplicate
    • Priority: Minor
    • Component/s: Measure
    • None
    • Nikita Kukreja
    • Hide
      Thank you for your feedback. Please refer to CQM-1101 where a similar question was posted and a planned update to the logic as outlined in the ticket will occur during the next annual eligible hospital eCQM update.
      Show
      Thank you for your feedback. Please refer to CQM-1101 where a similar question was posted and a planned update to the logic as outlined in the ticket will occur during the next annual eligible hospital eCQM update.

      Denominator of CMS60 & CMS53 says:
      AND: "Occurrence A of Diagnostic Study, Result: Hospital Measures-ECG (result: 'Hospital Measures-Acute or Evolving MI')"
      AND NOT:
      AND: "Occurrence A of Diagnostic Study, Result: Hospital Measures-ECG (result: 'Hospital Measures-Acute or Evolving MI')"
      AND: "Occurrence A of Diagnostic Study, Result: Hospital Measures-ECG (result: 'NSTEMI')"
      AND NOT: "Occurrence A of Diagnostic Study, Result: Hospital Measures-ECG (result: 'NSTEMI')"

      Need a explanation for the above mentioned conditions, as to what exactly are the conditions specifying.

      As when I come across a scenario while testing,
      where a patient has Diagnostic Study, Result: Hospital Measures-ECG (result: 'Hospital Measures-Acute or Evolving MI') for a particular visit it will move ahead and check for the same Diagnostic Study, Result as 'AND NOT' , but since the patient is already having Diagnostic Study, Result: Hospital Measures-ECG (result: 'Hospital Measures-Acute or Evolving MI'), the AND NOT condition will never get satisfied and the patient would never qualify for the denominator.

            Assignee:
            Joelencia Leflore
            Reporter:
            Nikita Kukreja (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved:
              Solution Posted On:
              Comment Posted On: