Uploaded image for project: 'QRDA Issue Tracker'
  1. QRDA Issue Tracker
  2. QRDA-934

Inconsistency in relevantDateTime vs relevantPeriod for data elements

XMLWordPrintable

    • Icon: QRDA-I Standard QRDA-I Standard
    • Resolution: Answered
    • Icon: Moderate Moderate
    • None
    • None
    • critical; blocker for advising clients on 2021 reporting
    • Dynamic Health IT
    • Jessica Ordoyne
    • Hide
      Reference QKI-2 for resolutions.
      Show
      Reference QKI-2 for resolutions.

      In our analysis of the 2021 eCQM data elements and attributes, we're finding that some measures continue to use relevantPeriod on some data elements and relevantDateTime on others. The problem is that some data elements allow either notation, and the notation is not used consistently across measures. 

      We have found four data elements with this inconsistency:

      • Diagnostic Study, Performed
      • Intervention, Performed
      • Laboratory Test, Performed
      • Procedure, Performed

      For example, measure CMS 125 looks for a mammogram returned as a Diagnostic Study Performed with attribute relevantDateTime. But then CMS 129 looks for a bone scan returned as a Diagnostic Study Performed but with attribute relevantPeriod. Given that these examples are both types of diagnostic scans, and given QDM specifically states that relevantDateTime and relevantPeriod are mutually exclusive, how do we guide our clients to return this data? 

      Additionally, two of the above data elements use both attributes in the same measure – in the case of CMS 129 with Procedure Performed, even in the same line of logic:

      I am attaching an excel file with a full list of all affected measures/data elements and which attribute is required by each.

      Is there any available guidance or recommendations on best practices for handling these inconsistencies?

            yanheras Yan Heras
            jordoyne@dynamichealthit.com Jessica Ordoyne
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: