CMS-2 Clarification on positive/negative result of screening in case of audit

XMLWordPrintable

    • Type: EC eCQMs - Eligible Clinicians
    • Resolution: Answered
    • Priority: Moderate
    • Component/s: None
    • None
    • Hide
      Thank you for your inquiry on CMS2v14 (Preventive Care and Screening: Screening for Depression and Follow-Up Plan). Guidehouse has been contracted by the Centers for Medicare & Medicaid Services (CMS) to conduct the Data Validation and Audit (DVA) work for the MIPS program. Please send DVA questions to MIPS_DVA@Guidehouse.com. MIPS eligible clinicians and groups are required to provide substantive, primary source documents as requested by CMS.
      Show
      Thank you for your inquiry on CMS2v14 (Preventive Care and Screening: Screening for Depression and Follow-Up Plan). Guidehouse has been contracted by the Centers for Medicare & Medicaid Services (CMS) to conduct the Data Validation and Audit (DVA) work for the MIPS program. Please send DVA questions to MIPS_DVA@Guidehouse.com . MIPS eligible clinicians and groups are required to provide substantive, primary source documents as requested by CMS.
    • CMS0002v14
    • Potentially failing an audit

      CMS-2: Preventative Care and Screening: Screening for Depression and Follow-up Plan. We are seeking clarification on what is needed in the case of an audit regarding the depression screening result (positive/negative). If we get audited and we use the score method (mapping to the recommended SNOMED codes (428171000124102: depression screening negative (finding) / 428181000124104: depression screening positive (finding)), what would we have to show from the EHR as proof of that result if we were audited? If the mapping occurs in the background and there is no front-facing result showing for the screening in the EHR, will we be negatively impacted?

            Assignee:
            AIR EC eCQM Team
            Reporter:
            Amanda Dunn
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: