Confirmation of file sizes

60 views
Skip to first unread message

Eddy H Nieves

unread,
Jul 2, 2024, 1:52:18 PM7/2/24
to Beneficiary Claims Data API (BCDA) Community
Hey BCDA Team, 

I was looking at chunking/resource counts and would like to confirm my understanding. I've seen these previous posts:

Limit on data file size? (google.com)

Patient/EOB File Size & ACO Access (google.com)

And also found some code in the project:

bcda-app/conf/configs/prod.env at master · CMSgov/bcda-app · GitHub

BCDA-1480 Feature: separated data chunking on a per datatype basis by tbellj · Pull Request #310 · CMSgov/bcda-app · GitHub

So, these seem to be the current numbers:
  • BCDA_FHIR_MAX_RECORDS_EOB=150
  • BCDA_FHIR_MAX_RECORDS_COVERAGE=4000
They don't match the sample data, but I assume that was on purpose for ease-of-use reasons. Is that correct? If so, are they subject to change, and will patient files ever get their own record count setting?

Thanks,
Eddy

Beneficiary Claims Data API (BCDA) Community

unread,
Jul 2, 2024, 5:23:53 PM7/2/24
to Beneficiary Claims Data API (BCDA) Community
Hi Eddy,

Thanks for the question! The maximum number of resources in a single file are defined for each of the FHIR resource types supported by BCDA including Patient. These maximums are subject to change, but here are the current values by resource type:
  • EOB = 150
  • Patient = 5000
  • Coverage = 4000
  • Claim = 4000
  • ClaimResponse = 4000
There are two code snippets where these values may be defined. The first snippet which you shared are the environment variables which take precedence and will override the default values defined in this second snippet.

Correct on the sample data - those files are meant for ease-of-use. However, files retrieved from the BCDA Sandbox will follow the same maximums defined for BCDA's production environment.

Hope this helps,
The BCDA Team
Reply all
Reply to author
Forward
0 new messages