CMS50 (Closing the Referral Loop: Receipt of Specialist Report): 2 TINs Sharing an EHR

XMLWordPrintable

    • Type: EC eCQMs - Eligible Clinicians
    • Resolution: Referred to External Party for Resolution
    • Priority: Moderate
    • Component/s: None
    • None
    • Hide
      Thank you for your inquiry. Unfortunately, this is out of scope for the eCQM Issues Tracker. We have created a ticket with the CCSQ Service Center for you with the following ticket number: CS2619415

      You will be contacted by their team and assigned a customer service representative who will work to resolve your inquiry.
      Show
      Thank you for your inquiry. Unfortunately, this is out of scope for the eCQM Issues Tracker. We have created a ticket with the CCSQ Service Center for you with the following ticket number: CS2619415 You will be contacted by their team and assigned a customer service representative who will work to resolve your inquiry.
    • CMS0050v14
    • CMS0050v13

      This is a follow up scenario from CQM-8224.
      TIN A and TIN B share an EHR.
      TIN A uses the EHR for reporting to MIPS for CMS 50.
      TIN B uses a Qualified Registry, and is not reporting on CMS 50.
       
      In TIN A, Dr. E saw the Patient on 6/15/25.
      TIN B placed a referral to TIN A's Dr. E during the measurement period.
      Because both TINs share an EHR, the referral from TIN B to TIN A's Dr. E is counting toward Dr. E.
       
      TIN B did not close the referral loop, and therefore the referral is counting against Dr. E (even though Dr. E saw the Patient, so the referral is irrelevant)
       
      Question: For Individual or Group reporting, should the report differentiate by TIN in the EHR so that only qualifying encounters with an EC in the TIN and referrals placed by ECs in the TIN count for that TIN's reporting?

            Assignee:
            AIR EC eCQM Team
            Reporter:
            Shoshannah Gil
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved:
              Solution Posted On: