The BCDA team is investigating a degradation in service

[Beneficiary Claims Data API (BCDA) Community]

Hello BCDA Users,

We've identified and are working to mitigate a service disruption that began in the past week. When making requests to the production API (api.bcda.cms.gov), users may not receive Part A claims.

At this time, we are investigating the root cause with our partner teams.

We're working to restore the service in full and will update the Google Group when we have an expected timeline for the service to be fully restored.

We apologize for any disruption this may have caused. Please don't hesitate to reach out to our team at bc...@cms.hhs.gov if you have any questions.

Thanks,
The BCDA Team

[Beneficiary Claims Data API (BCDA) Community]

Hello BCDA Users,

We've determined the root cause of the issue is related to filtering logic used to suppress SAMHSA related claims for the V2 endpoint. There is no impact to BCDA V1.

Our teams are working to restore the service in full and will update the Google Group once a fix is ready to be deployed. We'll provide instructions with how to ensure a full load of historical claims from the time this bug was first introduced.

We apologize for any disruption this may have caused. Please don't hesitate to reach out to our team at bc...@cms.hhs.gov if you have any questions.

Thanks,
The BCDA Team

[Beneficiary Claims Data API (BCDA) Community]

Hello BCDA Users,

Our partner team has deployed a fix and service is fully restored.

A bug introduced on July 10th incorrectly suppressed some INPATIENT, OUTPATIENT, SNF, HHA, and HOSPICE claims from BCDA V2 sandbox and production job results. There was no impact to BCDA V1 job requests.

For BCDA V2 users, we recommend re-running any job requests made on or after July 10th to backfill missing claims and ensure your organizations have a complete history of claims data.

We apologize for any disruption this may have caused. Please don't hesitate to reach out to our team at bc...@cms.hhs.gov if you have any questions.

Thanks,
The BCDA Team

[jacob.b...@gmail.com]

Thank you so much for your speedy root cause analysis and remedy.  We are re-executing now, and will let you know as soon as it completes without issue.  I plan to stay thru the end-of-the-day today to monitor our end-to-end ingestion and post-process and ensure everything gets pushed to end users successfully, so I will confirm with you as well before signing off.

Jake

[jacob.b...@gmail.com]

The re-run completed without issue  and we’ve resumed normal production posture. Thank you again for the speedy investigation and resolution on this.