Clarification on Interpreting Data & Insurance Coverage from Blue Button 2.0 API

Shaun MR

unread,

May 13, 2025, 12:05:39 PMMay 13

to Developer Group for CMS Blue Button API

Hi there,
I am currently working on integrating the Blue Button 2.0 API to fetch patient data for healthcare applications. While I am able to successfully retrieve data from various endpoints like ExplanationOfBenefit, Coverage, Patient, Condition, etc., I am facing some challenges in interpreting and displaying this data in a user-friendly manner.

My objective is to present patient insurance coverage, diagnoses, and eligibility information clearly . Any guidance, resources, or documentation pointers you can provide would be highly appreciated.

Thank you

Developer Group for CMS Blue Button API

unread,

May 14, 2025, 3:05:21 PMMay 14

to Developer Group for CMS Blue Button API

Hello,

We recommend referencing the following FHIR resource definitions:

Also, if you have not already, we also recommend reviewing the following resources for developers seeking to connect with the Blue Button 2.0 API:

Blue Button 2.0 website: https://bluebutton.cms.gov/
Production Access User Guide: https://bluebutton.cms.gov/guide/

Best,

-The Blue Button 2.0 Team

Shaun MR

unread,

May 19, 2025, 11:33:09 AMMay 19

to Developer Group for CMS Blue Button API

Hello,
I am currently working on integrating data from the Blue Button API endpoints. The data I am receiving is in JSON format, and it contains a large number of entries. These entries also include multiple 'link' objects with associated fields such as 'display', 'value', and others.

At this stage, I am looking to filter and extract only the necessary data from the response and display it on the frontend in a clean and organized way for other users to view. However, I am facing some challenges, especially with interpreting the 'link' objects. I would like to make these links more meaningful by presenting them with appropriate labels or descriptions that are user-friendly rather than showing the raw URLs.

To summarize, I am seeking assistance on the following:

Best practices to extract, interpret, and display Blue Button API data, particularly the 'link' objects.
Guidance on how to process the 'display', 'value', and other fields associated with the links to present them in a user-friendly and intuitive format.
Recommendations on structuring the data effectively for frontend display.

I would really appreciate your inputs on how to approach this problem efficiently.

Thank you for your support.

Best regards,
Shaun MR

Developer Group for CMS Blue Button API

unread,

May 20, 2025, 12:17:58 PMMay 20

to Developer Group for CMS Blue Button API

Hello Shaun -

In addition to the resources mentioned in our earlier post, you may also want to view our sample applications (listed below) as a starting point and test them using the synthetic user BB2User10000 (this is a special synthetic user that provides nearly every field the API supports, including a variety of claim types. This makes it an excellent testing account for populating test scenarios).

For processing individual fields, we recommend this resource, and recommend you find a FHIRPath implementation. Additionally, you can email us at bluebuttonapi@ cms.hhs.gov if you have specific questions.