Escalation - Server Refresh issue

67 views
Skip to first unread message

jacob.b...@gmail.com

unread,
Jul 18, 2024, 4:07:47 PM7/18/24
to Beneficiary Claims Data API (BCDA) Community
Hi BCDA team -

We have detected that no INPATIENT, OUTPATIENT, SNF, HHA, or HOSPICE EOBs were loaded in the most recent server refresh this past week. Only CARRIER/DME/PDE EOBs were added to the BFD server during your most recent backend load.

We examined the last few years of BCDA history and this is the first such time that this has happened.  Are you aware of this load issue and is it being resolved already?  We have called an immediate halt to our weekly end user update process in the meantime.

Jake

Beneficiary Claims Data API (BCDA) Community

unread,
Jul 18, 2024, 4:44:04 PM7/18/24
to Beneficiary Claims Data API (BCDA) Community
Hi Jake,

Thank you for flagging this. Our team is taking a look and could use a bit more information. To support our investigation, could you 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 fields from the EoB resources your team is using to identify claims of these types.
  3. If you've seen an increase in volume of Part B and Part D claims since this issue started.
Thanks,
The BCDA Team

jacob.b...@gmail.com

unread,
Jul 18, 2024, 6:16:32 PM7/18/24
to Beneficiary Claims Data API (BCDA) Community
Hi BCDA Team - 

#1 - the first affected organization Entity ID we flagged is D0052.
#2 - the field used to identify EOBs of these types is ExplanationOfBenefit.type.coding[system=https://bluebutton.cms.gov/resources/codesystem/eob-type].code
#3 - we have not seen any particular increase in volume of Part B nor Part D EOBs since this issue started (the weekly levels of CARRIER, DME and PDE EOB types is typical this week).

Thank you for digging in quickly, we are standing by.

Kale

Jake Halpert

unread,
Jul 19, 2024, 10:11:19 AM7/19/24
to Beneficiary Claims Data API (BCDA) Community
(For community line of sight, answers w/ private organization information provided in direct message to BCDA Team)

@BCDA Team --

On additional digging, we have found that the problem is not with the server load but with the BCDA payload generation. We have discovered this by running without _since (full import) and still getting only CARRIER, DME and PDE EOB types (while last week we got all types as normal). Interestingly/oddly, we support a DPC client (which is ultimately built off of the same BFD server) and all EOB types are returning normally this week (INPATIENT, OUTPATIENT, SNF, HHA, HOSPICE, CARRIER, DME, and PDE). We have not changed anything in our BCDA interface in the last 2 weeks, and we are rapidly reviewing BCDA's public git repo recent commit history now to see if we can identify if there are any breaking chagnes in the last 1-2 weeks.

Please keep us posted as soon as you have ideas,

Jake

On Thursday, July 18, 2024 at 4:44:04 PM UTC-4 Beneficiary Claims Data API (BCDA) Community wrote:

Beneficiary Claims Data API (BCDA) Community

unread,
Jul 19, 2024, 3:46:18 PM7/19/24
to Beneficiary Claims Data API (BCDA) Community
Hi Jake,

Thank you again for alerting us to this issue and supporting our investigation. The issue, which impacted all BCDA V2 calls starting on July 10, should now be resolved. Please refer to this Google Group thread for more details and continue to let us know if you see anything unusual.

Thanks,
The BCDA Team
Reply all
Reply to author
Forward
0 new messages