Question about the shutdown of the regular endpoints

[Samuel Wang]

Hello BCDA team,

I noticed that the regular endpoints (Group/all, Patient, etc.) responded with a 500 error this year, but it was a 400 error last time, with a text "please use /Group/runout" in the response text.

I wanted to confirm this observation, and make sure that they're indeed the same thing despite the different error codes. And was wondering where can I learn more about the shutdown protocol ahead of time. The announcement didn't seem to specifically mention about the 500 error.

Best regards,

Samuel

Samuel​​​​   Wang Senior Software Engineer (647) 994‑5133 |  samue...@pearlhealth.com 220 5th Avenue, 17th Floor, NY, NY 10001 www.pearlhealth.com

This email address should not be used to communicate private, confidential or sensitive information, including, but not limited to, personal health information protected by the Health Insurance Portability and Accountability Act of 1996, Public Law 104-191, as amended and its implementing privacy, security and breach notification regulations ("Protected Information"). If you need to send a communication to the sender of this email or any Pearl Health personnel containing Protected Information, please send an email to he...@pearlhealth.com indicating your need, but not containing the Protected Information, so that you can be provided instructions respecting use of a secure channel.

[Beneficiary Claims Data API (BCDA) Community]

Hi Samuel,

Thank you for reaching out. You are correct that the API Response during the performance year transition has changed to use a 500 response code and OperationOutcome resource.

Apologies for not including the HTTP response code in the messaging. Our announcement in Google Groups is the place to find the most comprehensive information and resources related to API changes during the performance year transition. You didn't miss anything however - we failed to include a note about the change to use a 500 HTTP response code.

Thanks,
The BCDA Team