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

Clarification on CMS-68v11

XMLWordPrintable

    • Icon: EC eCQMs - Eligible Clinicians EC eCQMs - Eligible Clinicians
    • Resolution: Answered
    • Icon: Moderate Moderate
    • None
    • None
    • UCP
    • Hide
      Hello and thank you for your inquiry. Unfortunately, this ticket is out of scope for the eCQM Issue Tracker. Your question has been redirected to the QualityNet Service Desk, and the following ticket has been opened for you:

      CS1686887

      You will be contacted by their team, and assigned a customer service representative who will work to resolved your inquiry. We are closing this ticket now. Please let us know if you have any additional questions about eCQM logic or specifications.
      Show
      Hello and thank you for your inquiry. Unfortunately, this ticket is out of scope for the eCQM Issue Tracker. Your question has been redirected to the QualityNet Service Desk, and the following ticket has been opened for you: CS1686887 You will be contacted by their team, and assigned a customer service representative who will work to resolved your inquiry. We are closing this ticket now. Please let us know if you have any additional questions about eCQM logic or specifications.
    • CMS0068v11
    • looking for clarification, as current set-up in EHR seems incorrect

      Clarification: When running a report for a single clinician as a MIPS eligible clinician in TIN A should CMS-68 only include encounters in which the MIPS EC participated in? For example a Patient has 3 visits in TIN A, but only 1 visit in TIN A with this EC.  I am making the assumption that a MIPS EC report level would only include the one encounter for CMS-68, and a TIN A level report would include all three.  Is this correct?

            edave Mathematica EC eCQM Team
            kristina.kew kristina kew
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved:
              Solution Posted On: