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

Public Comment for Draft 2024 CMS QRDA I Implementation Guide

XMLWordPrintable

    • Icon: Question/Guidance Question/Guidance
    • Resolution: Resolved
    • Icon: Moderate Moderate
    • None
    • None
    • Hide
      Comment:
      Section 5.1.6
      documentationOf was changed to a MAY statement a few years ago. Is this information still valuable for HQR reporting? As stated, the NPI and TIN may not be applicable for HQR reporting. If this information is no longer used by the HQR receiving system, I wonder if this section can be removed.
      Response: Thank you for this feedback, we will consider this update with stakeholders.
      Comment:
      Section 5.2.3.2
      There is a minor typo here where 'xsi:datype' should be 'xsi:type'
      Response: Thank you for catching this error, this will be corrected in the final publication.
      Comment:
      Section 5.2.3.3
      The example looks technically from CMS334v4.0.000. The draft specifications for RY2024 previously provided on the QRDA Issue Tracker is CMS334v4.0.011 and has a slightly different definition for the example text.
      Response: Thank you for this feedback, we will review the measure and example prior to final publication.
      Comment:
      Section 6.2
      Depending on the finalized value set for Platelet Count Lab Test for RY2024, should {ratio} be included as an allowable unit for Platelet CCDE? See CHM-143 for additional information about the types of codes that have been included in the Platelet Count Lab Test value set.
      Response: Thank you for this feedback, we will review this prior to final publication.
      Comment:
      CMS_0086
      We recommend that the description of CMS_0086 be updated so that it is explicit that files containing IQR/PI and OQR eCQMs cannot be submitted within the same batch.
      Response: Thank you for this feedback, we will discuss options for updating this error with the CMS receiving system team.
      Comment:
      Section 13 Change Log for 2024 CMS QRDA I IG
      Under 3.1 Background, there may be a mistaken reference to Medicaid Promoting Interoperability Program for 2024. Our understanding is that Medicaid Promoting Interoperability ended at the beginning of CY 2022.
      Response: Thank you for this feedback, we will correct the typo in the change log. The text in 3.1 is correct, which states “the Medicare Promoting Interoperability Program 2024 reporting period” and did not reference Medicaid.
      Show
      Comment: Section 5.1.6 documentationOf was changed to a MAY statement a few years ago. Is this information still valuable for HQR reporting? As stated, the NPI and TIN may not be applicable for HQR reporting. If this information is no longer used by the HQR receiving system, I wonder if this section can be removed. Response: Thank you for this feedback, we will consider this update with stakeholders. Comment: Section 5.2.3.2 There is a minor typo here where 'xsi:datype' should be 'xsi:type' Response: Thank you for catching this error, this will be corrected in the final publication. Comment: Section 5.2.3.3 The example looks technically from CMS334v4.0.000. The draft specifications for RY2024 previously provided on the QRDA Issue Tracker is CMS334v4.0.011 and has a slightly different definition for the example text. Response: Thank you for this feedback, we will review the measure and example prior to final publication. Comment: Section 6.2 Depending on the finalized value set for Platelet Count Lab Test for RY2024, should {ratio} be included as an allowable unit for Platelet CCDE? See CHM-143 for additional information about the types of codes that have been included in the Platelet Count Lab Test value set. Response: Thank you for this feedback, we will review this prior to final publication. Comment: CMS_0086 We recommend that the description of CMS_0086 be updated so that it is explicit that files containing IQR/PI and OQR eCQMs cannot be submitted within the same batch. Response: Thank you for this feedback, we will discuss options for updating this error with the CMS receiving system team. Comment: Section 13 Change Log for 2024 CMS QRDA I IG Under 3.1 Background, there may be a mistaken reference to Medicaid Promoting Interoperability Program for 2024. Our understanding is that Medicaid Promoting Interoperability ended at the beginning of CY 2022. Response: Thank you for this feedback, we will correct the typo in the change log. The text in 3.1 is correct, which states “the Medicare Promoting Interoperability Program 2024 reporting period” and did not reference Medicaid.

      The Centers for Medicare & Medicaid Services (CMS) has posted the draft 2024 CMS Quality Reporting Document Architecture (QRDA) Category I Implementation Guide (IG) for Hospital Quality Reporting (HQR) for public comment starting on March 28, 2023, and ending at 5 p.m. eastern time (ET) on April 11, 2023. The 2024 CMS QRDA I IG outlines requirements for eligible hospitals and critical access hospitals to report electronic clinical quality measures (eCQMs) for the calendar year 2024 reporting period. Visit the QRDA Issue Tracker on the ONC Project Tracking System (Jira) website to submit comments.

      The 2024 CMS QRDA I IG uses the same base Health Level 7 (HL7) QRDA I standard as the 2023 CMS QRDA I IG.

      The draft 2024 CMS QRDA I IG contains updates to support the 2024 reporting period.

      Information about submitting comments:

      • You must have a JIRA account to submit a comment.
      • We are accepting comments until 5:00 p.m. ET on April 11, 2023.

      Please note, this is a draft document and the contents are subject to change. Contents may change based on final rules and your comments. We look forward to receiving your feedback on the draft 2024 CMS QRDA I IG.

       

       

       

        1. 2024-CMS-QRDA-I-v1.0-Mar-2023.zip
          59 kB
        2. QRDA-HQR-2024-CMS-IG-final-DRAFT__508.pdf
          961 kB

            jseeman02 Jennifer Seeman
            jseeman02 Jennifer Seeman
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: