SlideShare utilise les cookies pour améliorer les fonctionnalités et les performances, et également pour vous montrer des publicités pertinentes. Si vous continuez à naviguer sur ce site, vous acceptez l’utilisation de cookies. Consultez nos Conditions d’utilisation et notre Politique de confidentialité.
SlideShare utilise les cookies pour améliorer les fonctionnalités et les performances, et également pour vous montrer des publicités pertinentes. Si vous continuez à naviguer sur ce site, vous acceptez l’utilisation de cookies. Consultez notre Politique de confidentialité et nos Conditions d’utilisation pour en savoir plus.
Hello Everyone. My name is Mark Scrimshire, I'm a Blue Button Innovator and Developer Evangelist for the Centers for Medicare and Medicaid Services, Otherwise known as CMS.
For the past few years I've been working on technologies and policies that empower patients to access their health data.
Today I'm here to talk to you about the new Blue Button API, Blue Button 2.0 and how with the help of Innovative Developers we can create a Data-driven ecosystem with our Medicare Beneficiaries.
Recognizing these challenges Two years ago, the Office of Civil Rights at HHS issued additional guidance reinforcing a Patient’s right to their health records electronically.
*Some of the key points in that guidance include* **...to direct a covered entity to transmit a copy of their medical records to the third party the patient chooses** ...offer patients electronic means to requests access**
CMS wholeheartedly supports this guidance and wants beneficiaries to be able to access their health information more easily.*
*Betty is a little younger than my Mum but like an ever growing community of Medicare Beneficiaries she is not afraid of technology.
**Betty is...* A 70 year old woman from Cleveland, OH. She has a smart phone and a fitness tracker that her son bought her for Christmas. She Factimes with her Grandkids regularly.
Her friend told her about a smart phone app that lets her see all of her medical records. She searches for it in the app store and downloads it.
Betty is relatively healthy but her Healthcare still leads to her having mountains of paper to deal with. All of those "This is not a bill" envelopes.
She carries her pill bottles to her doctor's appointments so she doesn't forget which pills and dosages she is on.. Every doctor's visit she finds herself filling out the same information into an endless number of forms.
Like thousands of other people her Healthcare experience is still stuck in the last century. But it can and is changing...
*For this magical interaction to happen in just a few clicks it requires a developer to build the integration using some well-proven Internet Standards*
*Let's run through what a Developer needs to do to* build this. First, he had to create a Developer account on the CMS Blue Button Developer Portal and setup his app.
Next, he sets up the Blue Button OAuth and used a sample MyMedicare username and password to retrieve a valid token
Next, he fetches this sample Beneficiary's Explanation of Benefit record. The Explanation of Benefit FHIR Resource combines key information from a Claim and optional Account information to describe the goods and services rendered by a provider and the settlement made under the patient's coverage in respect of that Claim. A doctor's visit or prescription filled for example. *The Developer uses our documentation and the Developer Preview environment to add the Blue Button API functions to their application. When the app is ready for prime time they submit their app to CMS to be added to the Production API.
**Once their app is activated on the Production Blue Button API they can update their App in the relevant app stores and start recruiting Medicare Beneficiaries.*
So what is in the API?
4 years of Claims history comprising Medicare Part A, B & D information For 53 Million Beneficiaries.
*ie. Hospital/In-Patient, Professional and Pharmacy claims.* The API provides a variety of information about a beneficiary’s health, including type of Medicare coverage, drug prescriptions, primary care treatment and cost.
**HIPAA**: Betty is invoking here HIPAA Right of Access to share her information with the Applications or Services she trusts.
**Consent**: The most important thing to remember is that beneficiaries always have full control over how their data can be used and by whom, with identity and authorization controlled by the Beneficiary through their [MyMedicare.gov](http://mymedicare.gov/) credentials.
**OAUTH2.0**: We are using OAuth 2.0 for authorization of the exchange of healthcare information electronically.
**FHIR** and HL7's FHIR industry-standard specification for the definition of the structured data that is being exchanged.*
All of these elements combine to make it quicker and easier for developers to create new and useful applications for patients....*
*CMS is also partnering with the National Institutes of Health through the "All Of Us" initiative.
Working together we can enable beneficiaries to contribute to scientific discoveries...
*With the click of a button, they will be able to donate their claims data to scientists performing groundbreaking research.
At CMS, we knew that when it came to empowering patients it is the services, not just the raw data, that is important. This is why we set out to build an API and tools so that Developers could access a Beneficiary’s claims with their consent and put that data to work.
Developers at big tech companies, large-scale research projects like the NIH’s Sync for Science, and at hundreds of startups across the country are building these patient-facing services enabled by access to Medicare claims data.
From health data aggregation to medication adherence to clinical trials, app developers can reduce patient burden and turn claims data into actionable insights improving patient care and reducing healthcare costs.
*This has been a long journey for me and I am proud of the support and leadership that CMS has provided in this quest to unleash the power of data for patients.
I am truly looking forward to seeing how you, as innovators, dream up new ways to help Beneficiaries by using their claims history without placing a heavy burden on them when they choose to share their data.*
I am delighted to announce today that the **Blue Button 2.0 API** is ready for you to use.
So Developers and Innovators. This is your call to action: **Go To** [bluebutton.cms.gov](http://bluebutton.cms.gov/) **and get started.**
Join more than 80 other organizations registered on our Developer Preview. Next week we will begin processing requests from those developers to move their applications over to the production Blue Button 2.0 API.
The CMS Blue Button API team will be hanging around if you have additional questions but I am happy to take a few questions now.
Blue Button 2.0 - At ONC Interoperability Forum
Creating a Data-Driven Ecosystem
with Medicare Beneficiaries
• Patients should have access and control to easily and securely share their
data with whomever they want, making the patient the center of our
• Vision for Blue Button 2.0 at CMS:
To build a developer-friendly, standards-based data API
that enables beneficiaries to connect their data to the
applications, services, and research programs they trust
Why Improve Blue Button?
Medicare Part A, B, and D
4 Years of Claims History
Patients have a right
to view and transmit
their health records.
for exchanging health
The industry standard
The beneficiary is always
in control of who can
access to their data.
Synthetic Beneficiary Records
With the click of a button, Medicare
beneficiaries will be able to donate
their claims data to scientists
performing groundbreaking research
Partnering with NIH’s Sync for Science