Introducing Native Mobile App Support
Installing a Client App Using Docker
This is the second in a series of posts in which we work step-by-step through installing, configuring, and running our new sample applications.
Over the past several weeks the Blue Button 2.0 team had been reviewing feedback from our developer community about new features you would like to be added to the API.
As we prepared for our first Blue Button 2.0 Developer Conference we wanted to add to our
portfolio of sample client applications.
Check out our new sample applications. The links to the GitHub repositories are in an earlier blog post here: https://bluebutton.cms.gov/blog/More-Sample-Applications.html
The Google Support forum is a vibrant place. We are always monitoring comments and questions there.
The Blue Button team is continually working to improve the Blue Button 2.0 API and the supporting documentation. When the API was announced at HIMSS in March 2018 it created a lot of interest. That interest came not just from developers wanting to connect to the API and work with the data it contains, but also from other organizations around the healthcare industry, such as insurers and Medicaid agencies. For the latter category of technologists there is significant interest in how The Blue Button team built the Fast Healthcare Interoperability Resource (FHIR) records that hold the beneficiaries’ data.
One of the frequent questions we get is: How does a beneficiary grant access to their claims information to an application?
As we prepared to launch our Production Blue Button 2.0 API we wanted to test the API from the perspective of a third-party client application.