A status code of 429 indicates “Too Many Requests.” This can occur due to two reasons:
Regardless of the reason, you will see a Retry-After response in the header. Wait until the period of time specified in the header has passed before making any more requests. This makes sure your client can adapt without manual intervention, even if the rate-limiting parameters change.
+If the request was successful, a 202 Accepted response code will be returned and the response will include a Content-Location header. The value of the Content-Location header indicates the location to check for job status and outcome. In the example header above, the number 42 in the URL represents the ID of the export job. The claims returned in the job will be filtered to have a serviceDate of 12/31/2020 or before.
-- If you're already requesting data from one endpoint and try to request data from that endpoint again while the first request is processing, you'll receive a 429 Too Many Requests error. -
++ If you're already requesting data from one endpoint and try to request data from that endpoint again while the first request is processing, you'll receive a 429 Too Many Requests error. For guidance on how to handle 429 errors, refer to our best practices. +
+See Step 3: Check the job status in the Request Data section above.
diff --git a/_includes/data/data_dictionary.html b/_includes/data/data_dictionary.html index 74e2b44..d96cfbb 100644 --- a/_includes/data/data_dictionary.html +++ b/_includes/data/data_dictionary.html @@ -1,9 +1,9 @@- BCDA provides CCLF to BCDA Data Dictionary to customers to facilitate their data mapping process. + BCDA provides the CCLF to BCDA Data Dictionary to customers to facilitate their data mapping process.
- The Data Dictionary was last updated in November 2023. + The Data Dictionary was last updated in March 2024.
Because BCDA delivers data in the FHIR format, data field names will be different from data fields delivered through CCLF files. In this spreadsheet, BCDA has provided a crosswalk between all CCLF data fields and their new locations within BCDA claims files. The BCDA Data Dictionary also provides supplementary context for each of the CCLF/BCDA data fields, including: diff --git a/assets/data/BCDA_Data_Dictionary.xlsx b/assets/data/BCDA_Data_Dictionary.xlsx index 236f62b..ad4a3c9 100644 Binary files a/assets/data/BCDA_Data_Dictionary.xlsx and b/assets/data/BCDA_Data_Dictionary.xlsx differ diff --git a/build.html b/build.html index 04a97f1..f6a7118 100644 --- a/build.html +++ b/build.html @@ -116,6 +116,20 @@ + + +