Request timing out during receiving Authorization token for Authentication

[Mihan Ali]

Hello ,

We are trying to download runout claims for our organization but we cannot obtain an authorization token to initiate our basic authentication.

I contacted my IT team and confirmed there were no firewall obstructions to the request.

Can we please we assisted in this regard?

[Beneficiary Claims Data API (BCDA) Community]

Hello,

Sorry for the trouble connecting to the production API. The timeout responses you've received are consistent with making API requests from an IP address that is not on the allow list. If you haven't already, please ensure that your requests are being made from an IP address that is on the allow-list associated with your organization's credentials in 4i or ACO-MS

Some common API clients, like the Postman Web Client, will send requests from their own web server by default. If you are using the Postman Web Client, please check that any proxy settings for your API client are set to use one of your organization's allowed IP addresses. Alternatively, try making a request from the Postman Desktop Client or another API client. The Postman Desktop Client allows you to view the network information from the request in the console. Postman has some documentation on how to do this here.

If you continue to have this issue after confirming you have taken the steps above, 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 timeout 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. The last time a successful job was completed for your respective entity(ies), and the last time a job was requested but not completed.
4. Whether this is happening for every type of resource type (e.g., patient, EoB, coverage).

Thank you,
The BCDA Team

[Mihan Ali]

Hello ,

I was able to troubleshoot this and was able to request data for my ACO. Thankyou

I had another question regarding the run-out api use. If i don't use the _since parameter , will it provide me all of PY2024 claims or all of 2024 run-out claims?

If i last downloaded data for my ACO on December 27th, 2024. how do i use the run-out api for the very first time if i need all the run-out claims till today?

[Beneficiary Claims Data API (BCDA) Community]

Hi,

Glad to hear you were able to resolve the issue and get connected to BCDA's production environment.

Using /Group/runout without the _since parameter will start a job that returns all data for your model entity's PY2024 attributed enrollees with the exception of claims having a service date after 12/31/2024.

Using /Group/runout with the _since parameter will further restrict the claims data you receive. For example, providing a date of 12/27/2024 for the _since parameter will start a job that returns data according to the following criteria:

• For enrollees attributed prior to December 2024:
  • Claims have a service date on or before 12/31/2024 (specified by /Group/runout) AND
  • claims have been updated on or after 12/27/2024 for enrollees (specified by _since=2024-12-27T00:00:00.000-05:00 )
• For enrollees newly attributed in December 2024:
  • Claims have a service date on or before 12/31/2024 (specified by /Group/runout)

Thank you,
The BCDA Team