Notice: Temporary service limitation during the performance year transition

[Beneficiary Claims Data API (BCDA) Community]

Hello BCDA community,

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

Temporary data limitations starting 01/01/2025

• You will only be able to request "runout" data from BCDA from PY 2024. Use the `runout` identifier with the /Group endpoint to return data for enrollees attributed to your organization in PY 2024.
  • Claims with a service date in 2025 will be excluded. The claims returned will have a service date no later than December 31, 2024.
  • 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 now be restored to individual entities as soon as their data is ready, which typically takes 1 month. We will notify you via Google Group when the limitation ends for each supported model. At that point, you can use the `all` identifier to request data, including 2025 claims, with the /Group and /Patient endpoints as usual.

Example requests and outcomes using BCDA in January 2025

• 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 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/2
• A caller polls the /Jobs endpoint until the job completes.
  • GET /api/v2/jobs/2
• The caller can now download the job data.
  • GET /data/2/output.json
  • All claims data will be capped at December 31, 2024.

Please respond to this email if you need additional assistance or have any questions.
- The BCDA Team

[Beneficiary Claims Data API (BCDA) Community]

Hello BCDA Community,  

This is a reminder that you will not be able to request claims with a 2025 service date during the performance year (PY) transition. You will, however, be able to request “runout” data for enrollees attributed to your organization at the end of PY 2024. This is a temporary limitation that will be in effect December 31, 2024 and last approximately a month.

• You will only be able to request runout data from BCDA from PY 2024. Use the `runout` identifier with the /Group endpoint to request runout data.

• • Claims with a service date in 2025 will be excluded. The claims returned will have a service date no later than December 31, 2024.
  • 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.

Thanks,
- The BCDA Team

[Beneficiary Claims Data API (BCDA) Community]

Hello BCDA Community,  

Starting tomorrow you will not be able to request claims with a 2025 service date due to the performance year (PY) transition. You will, however, be able to request “runout” data from PY 2024. This is a temporary limitation that will last approximately a month.

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

• • Claims with a service date in 2025 will be excluded. The claims returned will have a service date no later than December 31, 2024.
  • 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.

Thanks,
- The BCDA Team

[Beneficiary Claims Data API (BCDA) Community]

Hello BCDA Community,  

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

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

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

• • Runout data from PY 2024 will be available for 180 days after BCDA receives updated attribution files.

• • 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, which typically takes 1 month. We will notify you when this limitation ends for each supported model.

Thanks,
The BCDA Team