STATUS: Completed Project
CMS established a Blue Button platform in 2010 to give Medicare beneficiaries access to their own health information. In 2014, CMS was awarded a PCORTF project to develop a plan to redesign the Blue Button to enable it as a Data-as-a-Service platform. In 2016, a second CMS PCORTF project was awarded to implement the Data-as-a-Service platform and to utilize the Health Level Seven International (HL7) Fast Healthcare Interoperability Resources (FHIR®) framework. This allows third party services to build computer applications (apps) and other tools that can easily collect, present, and share the data—in a manner that ensures privacy and security of the data—which would make the data more actionable for patients.
PROJECT PURPOSE & GOALS
CMS worked with NIH to leverage the Sync for Science (S4S) and Blue Button API (BB API) programs to enable Medicare beneficiaries to donate their medical claims data for scientific research studies using S4S data donation workflow.
Make source code and documentation publically available.
Monitor the BB API system for performance and system issues and generate notifications.
Update the S4S reference implementation guide to include CMS BB API.
Make documentation, guides, and reference tools publically available.
Create and run Developer/Application Validation process to support operations.
Create a final report of the pilot, suitable for ASPE PCORTF to publish on their website.
Provide digital and printed materials to facilitate outreach and education on BB API and S4S to developers and end users.
PROJECT ACHIEVEMENTS & HIGHLIGHTS
CMS modified the BB API code to meet the S4S specifications. Specifically, modifications were made to the S4S reference implementation open source test suite for Medicare beneficiary claims data to work with the CMS Blue Button 2.0 developer sandbox.
CMS incorporated native mobile app support to the industry-standard OAuth2.0 authorization protocol. In addition, CMS added 30,000 synthetic Medicare beneficiaries to the production environment for production application testing, and increased the frequency of Medicare Part D data updates from monthly to weekly.
NIH conducted pilot testing on the S4S App, which was successful in validating the technology and workflow. NIH developed the S4S Discovery App that supports viewing both clinical and CMS Blue Button patient data made available by the S4S Procure App. The NIH-developed S4S Procure App allows developers to obtain data from the CMS Blue Button API.
PUBLICATIONS, PRESENTATIONS, AND OTHER PUBLICALLY AVAILABLE RESOURCES
- The BB source code is published on GitHub, which is maintained continuously for the Blue Button Platform: https://github.com/CMSgov
- CMS developed source code documentation, user experience guides, and reference tools, which are available on the Blue Button website: https://bluebutton.cms.gov
- The Blue Button 2.0 implementation guide was published June 2018. The implementation guide is available here: https://bluebutton.cms.gov/developers/#blue-buttonimplementation-guide
- Documentation detailing the developer/application validation process to support operations is available here: https://bluebutton.cms.gov/developers/#production-api-access
- The Blue Button 2.0 Sandbox is available at: https://sandbox.bluebutton.cms.gov
- A listing of Blue Button 2.0 Production applications can be found at: https://go.cms.gov/bluebuttonapps
- The MyMedicare.gov BlueButton Data Pipeline provides an Extract-Transform-Load (ETL) data pipeline, which moves data from CMS' Chronic Conditions data warehouse (CCW) into the CMS Blue Button FHIR Server. https://github.com/CMSgov/bluebutton-data-pipeline
- The S4S API website provides links to support the sharing of data via portals, including use cases in clinical data, financial data, and imaging data: http://syncfor.science
- The project has created a S4S Test Suite.
- The framework for testing S4S API implementations can be found here: https://github.com/sync-for-science/test-suite
- The Inferno Testing Tool for testing server compatibility with S4S can be found here: https://github.com/sync-for-science/test-suite/wiki/Inferno-Migration-Guide
- The S4S Research App API describes the list of endpoints available to any clients working with the Research App API. The App API is available here: https://github.com/sync-for-science/research-app-api
- The CARIN Consumer Directed Payer Data Exchange Implementation Guide describes the CARIN for Blue Button Framework and Common Payer Consumer Data Set (CPCDS), providing suggested resources for payers to provide to their consumers. The implementation guide is available here: http://build.fhir.org/ig/HL7/carin-bb/
Below is a list of ASPE-funded PCORTF projects that are related to this project
Improving Beneficiary Access to Health Information: A Plan to Enhance “Blue Button” – “Blue Button” is a service that allows patients to access their own health information in electronic form. CMS established a Blue Button platform in 2010 to give Medicare beneficiaries access to their own health information: however, this initial service had limited functionality and scalability, making it difficult for beneficiaries to use and share their health information. This project aimed to engage a range of stakeholders to define functional requirements for Blue Button as well as develop a plan to improve Blue Button, including an implementation strategy and roadmap for a ‘Data-as-a-Service’ Platform.
Improving Beneficiary Access To Their Health Information Through An Enhanced Blue Button Service – This project built on the project entitled, “Improving Beneficiary Access to Health Information: A Plan to Enhance “Blue Button”. Utilizing the Fast Healthcare Interoperability Resources (FHIR) framework to ensure data is in a structured format that can be accepted by a wide range of applications, the Blue Button on FHIR (BBonFHIR) interface put Medicare beneficiaries in control of connecting their data to third party applications and services they trust. In this model, beneficiaries are empowered to select participation in research based on their preferences (e.g., enrolling in a genetic cancer research study because of a familial history of cancer). This dramatically simplified the acquisition of beneficiary claims data to support beneficiary participation in clinical research studies. Once completed, the BBonFHIR Service application program interface (API) allowed researchers to selectively pull beneficiaries’ Medicare part A, B, and D claims data specific for specific research needs.