Groups keyboard shortcuts have been updated
Dismiss
See shortcuts

Cannot Generate BCDA API Credentials in ACO MS for PY 2024 ACO

75 views
Skip to first unread message

Maddy Blakeslee

unread,
Jan 6, 2025, 2:06:06 PMJan 6
to Beneficiary Claims Data API (BCDA) Community
Hi all,

We have an PY 2024 ACO that is not continuing in PY 2025. We are unable to generate credentials for the PY 2024 ACO. We are however still able to use the CLI tool to download the files off of ACO MS. The runout and managing credential documentation does not state that the runout endpoint requires an ACO to be active in the current PY (PY 2025). Is this behavior expected? Our organization requires Runout data via the BCDA API (Not CCLF files) in order for us to ingest and display accurate and complete patient information within our application and for our finance team to calculate shared savings. 

We are able to generate credentials for all the PY 2025 ACOs, and our user role is consistent across all PY 2024 and PY 2025 ACOs -  ACOs (Credential Delegate). 

Beneficiary Claims Data API (BCDA) Community

unread,
Jan 7, 2025, 9:16:24 AMJan 7
to Beneficiary Claims Data API (BCDA) Community
Hi Maddy,

Yes, that is the expected behavior for an ACO no longer participating in PY 2025. It's the BCDA team's policy to remove API access for model entities the same day their participation in the model ends, including terminated entities and model entities not continuing into the next Performance Year. We'll update the website with this information; thank you for pointing out the gap!

Thanks as well for including the importance of continued access to BCDA for the PY 2024 ACOs. For how long in 2025 would you ideally have access to BCDA runouts data for ACOs not continuing in PY 2025?

Best,
The BCDA Team

Maddy Blakeslee

unread,
Jan 7, 2025, 1:29:55 PMJan 7
to Beneficiary Claims Data API (BCDA) Community
Thank you for confirming. Ideally, the runout end point would include all PY 2024 ACOs for the entire time it's active, 180 days. I would expect the runout endpoint to use the PY 2024 attribution files and claims lookback logic/window from each program to determine the patients we receive data for via the endpoint so that there aren't data sharing/HIPPA concerns. The attribution files I'd expect the runout end point to use for MSSP are the Q3 and Q4 report packages. For ACO REACH I would expect the runout end point to use the Beneficiary Alignment reports that we receive monthly from Dec. 2024 - April 2025. 
Reply all
Reply to author
Forward
0 new messages