Medicare Shared Savings Program BCDA

[Somaiya Shakil]

BCDA group,

I have created BCDA credentials for MSSP to be able to obtain BCDA data. I can successfully retrieve an access token with the credentials but when I attempt to request data with this token, I get a 403 response. I have attempted multiple times and the response remains unchanged. 

I am using the same host address as for REACH. Is this appropriate or is the address different? 

Thanks,

Somaiya

[Beneficiary Claims Data API (BCDA) Community]

Hi Somaiya,

We are sorry to hear about the 403 issue when submitting a job request for this entity. In support of our investigation, please share the following:

1. The 5 character Entity ID for your organization(s). For example, ACOs in the Shared Savings Program have Entity IDs which begin with the letter 'A' followed by four numbers, like "A9999".
2. The API request that is resulting in these 403 errors. Please be sure to censor Personally Identifiable Information (PII) and other sensitive information (e.g., private keys, passwords) by replacing the information with the word ‘REDACTED’. Additional details and guidance can be found here in the Google Group.
3. Any additional messaging the system is providing to accompany the 403 error message.
4. If you have ever been able to make a successful job request with this MSSP entity.
5. Whether this is happening for every type of resource type (e.g., patient, EoB, coverage).

Feel free to add additional key details, and be sure to redact PII and other sensitive information.

Thank you in advance,
The BCDA Team

[Beneficiary Claims Data API (BCDA) Community]

Hi Somaiya,

Thanks for the info on the 403 error. We took another look at what you sent over and it seems we missed a step in getting this ACO fully onboarded to BCDA. The team has made the adjustment and you should be able to make successful requests at this point. Please give it another try and let us know if you're still receiving the same issue.

Please remember to redact sensitive information including bearer tokens from emails and messages to the Google Group. We prevented your previous response from posting to the Google Group because it included a bearer token in the output of the curl command. Switching your curl command from the `-v` (or --verbose) flag to the `-i` (or --show-headers) flag should prevent the bearer token from being included in the output of future curl commands.

Thanks!
The BCDA Team

[Somaiya Shakil]

Hi,

We have been able to successfully make API calls for BCDA for ACO ID A5388 but we were not able to download all 5 file types. We were able to retrieve files for eob, patient and coverage. However, claim and claim response types gave a "400 Bad Request" response. We would like to be able to retrieve partially adjudicated BCDA. Could this be done?

Thanks,

Somaiya

[Beneficiary Claims Data API (BCDA) Community]

Hi Somaiya,

BCDA's partially adjudicated claims data is only available for REACH ACOs at this time. We recommend emailing the model leads at SharedSavi...@cms.hhs.gov with your interest in accessing partially adjudicated claims data through BCDA.

Thanks!
The BCDA Team

[Wellvana Wellvana]

Hi,

I am having this same issue with onboarding a new MSSP ACO. What email should I send the impacted Entity ID to?