Recently there has been an increase in questions on the Blue Button Google Group about a ‘500 error’ when using the Test Client.

A few changes have been made to help you avoid this issue when starting to use the Blue Button 2.0 API.

Here are the changes that have been implemented:

Changes to the Test Client

The Test Client was originally developed to enable simple testing of our secure Sandbox API. But if you are logged into your developer sandbox account and go through the authorization flow in the Test Client, you will get a 500 error. In order to reduce confusion and make testing easier, we’ve added a warning message and a logout link to the Test Client.

Changes to the “Try the API” documentation

While diagnosing the 500 error on the Test Client, we discovered that our documentation for first-time users of the Blue Button 2.0 API was unclear and needed improvement.

Instructions for users of the popular Postman developer tool have been provided in step 3 of the “Try the API” section of the documentation. These instructions are also easy to follow for developers who prefer to use the Insomnia app on Mac OS.

In the “Try the API” section, we have highlighted the Medicare.gov synthetic beneficiary user IDs and passwords in each section where you might need to use them to authenticate.

The documentation also reflects the switch to using a minus sign prefix to the FHIR Patient IDs for the Blue Button 2.0 synthetic records. When we added the synthetic beneficiaries and their claims to the production environment, we added a minus sign prefix to the FHIR ID to avoid any possibility of a collision between synthetic and real beneficiary records.

Check out the documentation and let us know if there are other improvements we can make. As always, we welcome your feedback via the Google Group.


Earlier Blog Posts

Blog Index

Latest

Category:Latest

General

Category:General

Code

Category:Code

Back to top Subscribe to RSS Feed Comments via Google Group