Temporary service limitation during the performance year transition

[Beneficiary Claims Data API (BCDA) Community]

BCDA data limited in Jan 2026 for yearly updates 

Hello BCDA community, 

There will be a temporary limitation to the data available from BCDA in January 2026 while CMS updates beneficiary attribution for the new performance year (PY 2026). Until BCDA receives your model entity's attribution information for PY 2026, you will not be able to request current or new claims data from the API. 

Temporary data limitations starting 01/2026

• You will only be able to request "runout" data from BCDA from PY 2025. Use the `runout` identifier with the /Group endpoint to return data for enrollees attributed to your organization in PY 2025. 

  • Claims with a service date in 2026 will be excluded. The claims returned will have a service date no later than December 31, 2025. 

  • You can use the _since parameter with the `runout` identifier to only return data updated since your last runout request.

  • Review our documentation and example requests for runout data. 

• You will not be able to make requests to the /Group/all or /Patient endpoints. These requests will result in an OperationOutcome error.

Normal functionality will be restored to individual entities as soon as their data is ready. This typically takes 1 month. We’ll notify you here when the limitation ends for each supported model. At that point, you can use the `all` identifier to request data, including 2026 claims, with the /Group and /Patient endpoints as usual.

Example requests and outcomes using BCDA in January 2026

• A caller makes a request to the /Patient or /Group endpoint using the `all` identifier.

  • GET /api/v2/Patient/$export

  • GET /api/v2/Group/all/$export

• The caller receives a 404 Not Found response and an OperationOutcome error.

  • An example OperationOutcome.fhir.json is attached. Callers should use the /api/v2/Group/runout/$export endpoint.

• A caller makes a request to the /Group endpoint using the `runout` identifier.

  • GET /api/v2/Group/runout/$export

• The caller receives a 202 Accepted response.

  • Content-Location header sent with the job location.

  • Content-Location: /api/v2/jobs/{job_id}

• A caller polls the /Jobs endpoint until the job completes.

  • GET /api/v2/jobs/{job_id}

• The caller can now download the job data.

  • GET /data/2/output.json

  • All claims data will be capped at December 31, 2025.

Please respond to this email if you need help or have questions.

- The BCDA Team

[Samuel Wang]

Hi BCDA Team,

I just wanted to verify that the statement that "The caller receives a 404 Not Found response" is correct. We saw a 500 error last year, with the text "awaiting new attribution information at the beginning of a Performance Year" in the response, and have used that to detect the annual maintenance error. I would like to get a confirmation about the exact status code and response text that will be used for 2026 to ensure that our control flow works currently. Any advice is much appreciated!

Thanks,

Samuel

Samuel   Wang ​​​​ Software Engineer II (647) 994‑5133 |  samue...@pearlhealth.com 220 5th Avenue, 17th Floor, NY, NY 10001 www.pearlhealth.com

This email address should not be used to communicate private, confidential or sensitive information, including, but not limited to, personal health information protected by the Health Insurance Portability and Accountability Act of 1996, Public Law 104-191, as amended and its implementing privacy, security and breach notification regulations ("Protected Information"). If you need to send a communication to the sender of this email or any Pearl Health personnel containing Protected Information, please send an email to he...@pearlhealth.com indicating your need, but not containing the Protected Information, so that you can be provided instructions respecting use of a secure channel.

[Beneficiary Claims Data API (BCDA) Community]

Hi Samuel, 

That is correct, and apologies for any inconvenience from the changes year-to-year! The error BCDA will use during the performance year transition has been updated to better reflect its status as an expected error and to align with general missing attribution messages. For 2026, you will receive a 404 error code and the following OperationOutcome: 

{ "issue": [ { "code": "exception", "details": { "coding": [ { "code": "Request Error", "display": "unable to perform export operations for this Group. No up-to-date attribution information is available for ACOID 'A####'. Usually this is due to awaiting new attribution information at the beginning of a Performance Year", "system": "http://hl7.org/fhir/ValueSet/operation-outcome" } ], "text": "unable to perform export operations for this Group. No up-to-date attribution information is available for ACOID 'A####'. Usually this is due to awaiting new attribution information at the beginning of a Performance Year" }, "diagnostics": "unable to perform export operations for this Group. No up-to-date attribution information is available for ACOID 'A####'. Usually this is due to awaiting new attribution information at the beginning of a Performance Year", "severity": "error" } ], "resourceType": "OperationOutcome" }

Thank you, 

The BCDA Team

[Samuel Wang]

Hi the BCDA team,

Thank you! That's helpful!

Cheers,

Samuel

Samuel Wang​​​​Software Engineer II(647) 994‑5133 | samue...@pearlhealth.com220 5th Avenue, 17th Floor, NY, NY 10001www.pearlhealth.comThis email address should not be used to communicate private, confidential or sensitive information, including, but not limited to, personal health information protected by the Health Insurance Portability and Accountability Act of 1996, Public Law 104-191, as amended and its implementing privacy, security and breach notification regulations ("Protected Information"). If you need to send a communication to the sender of this email or any Pearl Health personnel containing Protected Information, please send an email to he...@pearlhealth.com indicating your need, but not containing the Protected Information, so that you can be provided instructions respecting use of a secure channel.

[Beneficiary Claims Data API (BCDA) Community]

2026 data unavailable until February 2026

Hello BCDA Community,

This is a reminder about temporary limitations in effect during the performance year (PY) transition.

Which data will not be available

• Claims with a 2026 service date will be unavailable until February 2026.
  • We’ll let you know when we have more precise dates for each model.
• You won’t be able to make requests to the /Group/all or /Patient endpoints. These requests will result in an OperationOutcome error.

Which data will be available
You will be able to request “runout” data for enrollees attributed to your organization at the end of PY 2025. Use the `runout` identifier with the /Group endpoint to request runout data.

• Claims with a service date in 2026 will be excluded. The claims returned will have a service date no later than December 31, 2025.
• You can use the _since parameter with the `runout` identifier to only return data updated since your last runout request.
• Review our documentation and example requests for runout data.

Thanks,
- The BCDA Team

On Tuesday, December 2, 2025 at 2:43:06 PM UTC-5 Beneficiary Claims Data API (BCDA) Community wrote:

[Beneficiary Claims Data API (BCDA) Community]

2026 data unavailable until February 2026

Hello BCDA Community, 

The following limitations go into effect Dec 31, 2025: 

Which data will not be available

• Claims with a 2026 service date will be unavailable until February 2026.

• You won’t be able to make requests to the /Group/all or /Patient endpoints. These requests will result in an OperationOutcome error.

Which data will be available

You will be able to request “runout” data for enrollees attributed to your organization at the end of PY 2025. Use the `runout` identifier with the /Group endpoint to request runout data. 

• Claims with a service date in 2026 will be excluded. The claims returned will have a service date no later than December 31, 2025. 
• You can use the _since parameter with the `runout` identifier to only return data updated since your last runout request.
• Review our documentation and example requests for runout data. 

Thanks,

The BCDA Team

[Beneficiary Claims Data API (BCDA) Community]

2026 data unavailable until February 2026

Hello BCDA Community,  

Please follow this guidance to access BCDA data during our performance year (PY) transition:

• You will only be able to request BCDA “runout” data from PY 2025. Use the `runout` identifier with the /Group endpoint to return data for enrollees attributed to your organization in PY 2025. 

  • Claims with a service date in 2026 will be excluded. Claims returned will have a service date no later than December 31, 2025. 

  • You can use the _since parameter with the `runout` identifier to return data updated since your last runout request.

  • Runout data from PY 2025 will be available until Fall of 2026. Review our documentation and example requests for runout data. 

• You will not be able to make requests to the /Group/all or /Patient endpoints. These requests will result in an OperationOutcome error.

Normal functionality will be restored to individual entities as soon as their data is ready. This typically takes 1 month. We’ll update the Google Group when we have more precise timing. 

Thanks,

- The BCDA Team

[Anil Bobade]

Hi Team,

By when 2026 data be available in Feb 2026?

Regards,

Anil Bobade

[Beneficiary Claims Data API (BCDA) Community]

BCDA data available for ACO REACH and KCC as of 2/3/2026, coming soon for MSSP

Hi BCDA users, 

Model entities participating in the ACO REACH and KCC models can now access PY 2026 data using the /Group/all and /Patient endpoints. MSSP ACOs are expected to gain PY 2026 data access in the week of February 9.

We restore access to each of your organizations once we receive the corresponding CCLF files.

Before BCDA receives PY 2026 files for your organization (For MSSP)

• You can use the /Group/runout endpoint as normal

• Requests to the /Group/all and /Patient endpoints will return a 500 error message with an OperationOutcome

Access after BCDA receives your PY 2026 files (For ACO REACH and KCC)

• You'll be able to use the `all` identifier for /Group and /Patient endpoint requests.

• Use the `all` identifier for your first PY 2026 data request. There will be no service date restrictions for this data.

• In order to request "runout" data from PY 2025, use the `runout` identifier separately with the /Group endpoint. 

  • This will return data for enrollees who were attributed to your organization in PY 2025, but not PY 2026.

  • Use the `_since` parameter in conjunction with the `runout` identifier to limit data to updates occurring since your last runout request.

  • The `runout` identifier will be updated each month up to and including July 2026. After July 2026, new data for enrollees who were attributed to your organization in PY 2025, but not PY 2026, will no longer be included.

Please respond to this conversation or email bc...@cms.hhs.gov if you have questions or need help. 

- The BCDA Team