ACO Sync Overview

ACO Sync is an automated process that performs the ACO-level patient de-duplication and combines all the TIN Participant data under your ACO organization. This is triggered daily if the ACO Sync is not already running and will continue to completion. This process may take 1-2 days depending on the amount data to aggregate.

You can determine the date and time of the most recent ACO Sync using the following steps:

• Navigate to Group Practices > Select practice name in blue >  ACO Sync button
• Notice the date and time in the ACO Synch Status panel in blue

You can determine if the ACO Sync is currently queued or running by looking each TIN Participant in the Status column which then indicates "Sync Queued" or "Sync Running". If the ACO sync is not currently running, the message "Sync Complete" will be displayed.

Patient De-Duplication

Patients are de-duplicates at the ACO level  by matching of the Patient First Name, Last Name, Date of Birth, and Gender. This is triggered by the automated ACO Sync process.

Scoring

Once ACO Sync has completed the ACO organization will have combined the numerator and denominator information from all of the Participant TINs according to the following rules: 

Combining Collection Types

The table below illustrates the combinations of collection types the member TINs for an ACO could submit to Patient360 along with the resulting ACO aggregation options.

*As of 03/24/25 the denominator criteria for MCQM M112 has an age range which is different than the eCQM version of this measure. Patient360 is confirming with CMS. Unless CMS changes these date ranges, conversion of eCQM to MCQM for M112 will not be possible. 

Please note that MCQM is the ONLY aggregation option available to ACOs who have at least 1 member TIN that submits MCQM data to Patient360 or reports MCQM denominator-only counts for at least 1 member TIN. 

ACO Sync Process

For each ACO, for each measure:

Step 1: Perform CQM/eCQM aggregation

• If at least 1 member TIN submitted MCQM data to Patient360, then verify the ACO has an MCQM roster on file; If not, halt aggregation for the measure with the message, “ACO aggregation for measure {MEASURE #} cannot proceed due to missing Medicare roster”
• If all member TINs submitted eCQM data to Patient360, then aggregate to eCQM
• If any member TINs submitted CQM or MCQM data to Patient360, then aggregate to CQM 

Step 2: Perform MCQM aggregation

• If ACO has an “active” Medicare roster, then create MCQM instance of measure
• For each patient for each measure: Compare patient information to Medicare roster
  • If exactly 1 match is found, copy the patient to the MCQM instance of the measure
  • If 0 matches are found, do nothing
  • If >1 match is found, skip patient and log message, “Patient {MASTER_PAT_ID} skipped because more than one roster match was found”

Step 3: Clean-Up

If any member TINs submitted MCQM data to Patient360, then remove CQM instance of measure from ACO