FHIR Chat · MyHealthEData & Blue Button 2.0

Stream: Announcements

Topic: MyHealthEData & Blue Button 2.0

Abbie Watson (Mar 06 2018 at 18:35):

Oy vey. CMS just announced #MyHealthEData and their Blue Button 2.0 API. Do we know anything about this? It's a web API, so that's good news (it's not a PDF or HIPAA compliant e-mail), but do we have any word if it's OAuth compliant, uses FHIR resources, etc?

https://www.cms.gov/Newsroom/MediaReleaseDatabase/Fact-sheets/2018-Fact-sheets-items/2018-03-06.html

Grahame Grieve (Mar 06 2018 at 23:34):

I believe that is @Mark Scrimshire's API and it is a FHIR api

Peter Jordan (Mar 07 2018 at 02:46):

@Mark Scrimshire can you reveal which version of FHIR this is using?

John Silva (Mar 07 2018 at 10:49):

FYI: the "Blue Button" concept began in the VA back in 2010 for US Veterans: https://www.va.gov/bluebutton/ From the press release it sounds like this Blue Button 2.0 is expanding the reach beyond veterans to Medicare beneficiaries.

And here is the official page for "Blue Button 2.0": https://bluebutton.cms.gov/ which specifically says that it uses FHIR and OAuth 2.0.

Interesting info on "Blue Button 2.0" page; you can even sign up for a sandbox demo account to try it out. It also talks about the FHIR Model it uses and the coding and identifiers they have used/mapped.

"We have mapped over 1,300 fields from the CMS claims data warehouse into FHIR. These fields are surfaced across the Patient, Coverage and Explanation of Benefits FHIR resources."

Josh Mandel (Mar 08 2018 at 00:11):

It's fhir STU3, supporting the SMART authorization specification for confidential clients. Patient, ExplanationOfBenefit, and Coverage resources exposed.

Lloyd McKenzie (Mar 08 2018 at 00:16):

Note that discussion should ideally be happening on #social or #implementers :)

Mark Scrimshire (Mar 12 2018 at 15:52):