Unable to Access BCDA v3 Sandbox Data – 500 Internal Server Error

[Ashvani goyal]

Hi, BCDA Team,

We are experiencing a 500 Internal Server Error while requesting BCDA test data using the Sandbox API (v3).

API URLs used:
https://Sandbox.bcda.cms.gov/api/v3/Group/all/$export?_since={since_date}
https://Sandbox.bcda.cms.gov/api/v3/jobs/85110

Request Headers:
{
  "Accept": "application/fhir+json",
  "Authorization": "Bearer {access_token}"
}

Error Response:

{

    "issue": [

        {

            "code": "exception",

            "details": {

                "text": "Service encountered numerous errors. Job failed to complete."

            },

            "diagnostics": "Service encountered numerous errors. Job failed to complete.",

            "severity": "error"

        }

    ],

    "resourceType": "OperationOutcome"

}

 
 We have retried the requests multiple times over the past few hours and have also encountered the same issue on several occasions during the last week. Since the error persists despite repeated attempts, it appears that the issue may be originating from the BCDA server.  

Could you please advise on:

1. Whether there are any known issues with the BCDA v3 Sandbox environment?
2. If there are any additional requirements or configuration changes needed to access v3 data successfully?
3. Any alternative approach or troubleshooting steps we should follow?

We would appreciate your guidance on how to proceed with accessing BCDA v3 data.

Thank you for your support, and we look forward to your response.

Thanks & Regards,
Ashvani Goyal

[Beneficiary Claims Data API (BCDA) Community]

Hi Ashvani,

Thanks for your interest in trying out BCDA v3! At this point, we've wrapped up the Early Adopter Program and are working on some final updates to the API and documentation before we release v3 as Generally Available. Keep an eye on the BCDA Google Group for the latest.

The BCDA v3 Sandbox is open for your testing, however only the Adjudicated claims data sets – 2 advanced sizes have been configured with v3 data in the BCDA sandbox. Use either of the following sets of credentials to access synthetic data from BCDA v3:

Small Advanced Model Entity (100 synthetic enrollees)

• Client ID: 6dc59a4c-ef93-46c0-9c00-02e500e13731
• Client Secret: 48fe3a3731ee5b68cf4ebeea6d93fa2d9db3396e94f6830f17d7d7c0fa1fb61f413fcde6f6322f84

Large Advanced Model Entity (10,000 synthetic enrollees)

• Client ID: f5b6a686-0d7b-4080-873a-e60534fd2995
• Client Secret: 96ac1483449c652f363396737937f23cdae47a56a116c8a4405dbd54b31d2686f005df502c5c86ab

This preview of our migration guidance may be useful in planning your migration to BCDA v3. Please keep in mind the documentation is still being updated to reflect the latest changes to the API, and our recommendations may change from now to the release of BCDA v3.

We welcome any and all feedback you have on BCDA v3 and the supporting documentation. Happy testing.
The BCDA Team

[Ashvani goyal]

Hi BCDA Team,

Thank you for your response and for providing access to the BCDA v3 sandbox.

We tested the sandbox using the credentials you shared and were able to successfully authenticate and download the exported files. However, we noticed that only the ExplanationOfBenefit (EOB) and OperationOutcome resource files are being generated and downloaded.

We are unable to retrieve Patient and Coverage resource files. Could you please confirm whether these resources are currently available in the BCDA v3 sandbox datasets, or if there are any additional steps or parameters required to access them?

Thank you for your assistance. We look forward to your guidance.

Best regards,
Ashvani Goyal

[Beneficiary Claims Data API (BCDA) Community]

Hi Ashvani,

We are sorry to hear about the missing Patient and Coverage resources from your v3 sandbox requests. In support of our investigation, please share the following:

1. The /Group or /Patient $export request that is resulting in missing Patient and Coverage resources.
2. Whether or not you have been able to successfully retrieve Patient and Coverage resources using the BCDA v2 sandbox.

Please feel free to provide any additional information that you think might be pertinent.

The BCDA Team