Showing posts with label BlueButtonPlus. Show all posts
Showing posts with label BlueButtonPlus. Show all posts

Friday, June 12, 2015

FHIR and BlueButtonPlus for Newbies

This one is for ePatient Dave, who asks:


Blue Button Plus (BB+) is an initiative that started at a White House sponsored meeting several years ago (I got to attend with my daughter).  I've written a number of posts about this particular effort, and participated in the Blue Button Plus Pull initiative of the ONC Standards Initiative project.  That workgroup produced an API based on an early draft of the HL7 FHIR Standard.  Integrating the Healthcare Enterprise further developed that into a specification called Mobile Access to Health Documents (MHD for short).  BB+ Pull and MHD are specifications that meet the requirements of the ONC Certification and Standards regulations for EHR systems to support View and Download. A sister specification BB+ Push uses a different protocol (call Direct) based on e-mail to support the "Transmit" requirement of that regulation.

BB+ Pull and VDT capabilities allow you to access the same kinds of clinical data at nearly the same level of fidelity that healthcare providers have in their EHR systems.  This allows patients to use this data in ways of their own choosing, including sharing the data with other healthcare providers, or tracking and using it in applications on their own computers and mobile devices.

As a standard, FHIR has really taken off, reaching awareness heights in the trade press, academic organizations, and medical professionals that many standards organizations would drool with envy over.  HL7 and its creators have much to be proud about in this.  I've awarded several of the developers with an Ad Hoc Harley award, including Grahame Grieve, its chief Architect, and Josh Mandel (who was also very involved in the BB+ work).  However, FHIR is also still in the early adoption stages.  Several vendors are supporting its development and incorporating it into products, but it will take some time for those versions of the products to reach a doctor near you.  From product release to mainstream deployment across a customer base can take several years.

While FHIR has really taken off, Blue Button Plus still has yet to reach similar dizzy heights.  The Blue Button Connector page lists 140 hospitals, 9 pharmacies, 4 labs, and 39 payers who provide BB+ access, but few of these allow you (as BB+ Pull does) to send those records to your favorite application.  There are also about 13,000 physicians who have attested to MU Stage 2 which provide some access for download, but likely don't provide the BB+ Pull capabilities.

Both of these specifications have a lot to offer patients, and we are likely to see even more utilization of FHIR, Blue Button Plus, and IHE's Mobile Access to Health Documents, as well as another FHIR related ONC initiative; the Data Access Framework, which will provide access to granular health data instead of documentation of encounters in the future.  However, at the current rates of development and deployment, it will probably be five years or more until I, as a resident in a rural community, can have a nearby physician who uses a system that supports these standards.  If I were to drive an hour to a Boston-based physician, I might have to way only three years for wide-enough deployment to be readily able to find a physician that could give me my damn data.

   -- Keith


Wednesday, September 25, 2013

It must be Wednesday at the HL7WGM

If you've figured it out by now, I have a tradition on Wednesday mornings at the annual plenary meeting.  Of course it's a time for recognition in the HL7 community, but I have to tell you those blue vases are quite heavy.  What I've got is much cooler and lots easier to carry around.

So who's next up for an Ad Hoc Harley?  I'll give you some hints.  He's young, probably late 20s. He's smart. He knows CDA. And CCDA. And FHIR. Already his contributions to interoperability are great.

Give up?  Need more hints?  He's disruptive.  He knows OAuth. And RDF.  If you haven't figured it out by now, I'm pretty sure he has.

Let's delve a bit more: Genetics.  IT.  Software.  Geeky software.  Health IT Software.  And Poetry.  I'm told he likes poetry.  And speaks fluent French.  He's also an all around nice guy.  And smart?  Did I mention smart?  It doesn't hurt to say it again.

If I were to give this award for one of his accomplishments, I don't know which it would be.  Many of the things he's managed to accomplish is stuff I should have, wanted to or aspired to do, but couldn't pull it off. And I don't know what he'll do next and look forward to it, but frankly I'm also hoping he'll stick around for a while, because we [patients] need him.

So here we go...

This certifies that 
Josh Mandel of Children's Hospital Boston 


Has hereby been recognized for outstanding contributions to Healthcare IT including, but not limited to: SMART and Blue Button Plus and C-CDA Examples and Scorecard and FHIR Open Source


Thursday, August 15, 2013

A Low Res HITECH Destination

Here it is.  What is it?  Why, it's where you can send me my data Doc.
Crafted with QR Pixel



Monday, July 29, 2013

What does BlueButtonPlus / FHIR provide that CCDA doesn't have?

I joined the NwHIN Power Team last week.  I was asked likely due to my experiences with Blue Button Plus Pull and HL7 FHIR.  Today on a join call with the Privacy and Security workgroup, the question came up about what FHIR and/or BB+ provides that isn't available with C-CDA.  I always struggle here because I'm involved in the SDO activities, and get this.  Yet many C-levels who are reviewing the work of these groups are don't yet. The communications from one to the other is always a challenge.  SDOs typically don't spend whole lot in targeted marketing to the C-suite on their work, and this is especially true during the development time frame.  I'll try to approach the question from a C-level perspective:

Let's start with this qualification: FHIR and Blue Button Plus are related but not identical initiatives.  The former is an HL7 International standards effort.  The latter is a US initiative that is using parts of FHIR to enable consumer access to clinical data.

What is different with BlueButtonPlus / FHIR from what I'm doing today?
What Blue Button Plus (pull) provides is access to a  FHIR-based resource by which you can query for CCDA documents in a RESTful manner, and subsequently download them.  It doesn't ask you to aggregate your content differently, or use some new format to describe problems, medications and allergies.  So, content is structured the same, but metadata is structured and queried RESTfully.

The mechanism by which access is granted via BB+ Pull makes use of OAuth 2.0, which is the same thing that FaceBook, Twitter, Linked In, and other services on the web enable other applications to access your data stored in those services.

Why is BlueButtonPlus / FHIR good?
This is good because it vastly simplifies the way that consumer applications can access health data, making it possible for smart phones, tablets, wearable devices, et cetera, to participate in consumer data access and use of healthcare data.  It also prepares sources of consumer data to move towards an architecture that can support more granular access in the future (but doesn't require it today).

Does Blue Button Plus / FHIR eliminate the need for CCDA?
Blue Button Plus is not eliminating CCDA, but rather building from the use of it.  Blue Button Plus REQUIRES the use of CCDA.

You've probably heard about "Green CDA" and I've said in the past that FHIR is to HL7 V3 what Green CDA is to CDA.  FHIR greens HL7 Version 3, and so EVENTUALLY, there will be a new Document resource in FHIR that is a composite of clinical resources (like problems, allergies, medications, lab results, et cetera).  But we (HL7 Structured Documents) aren't working on that right now.  Eventually this will occur, and those resources will be key components of it.

How is Blue Button Plus / FHIR retaining compatibility with CCDA?  
CCDA and Green CDA and content from similar efforts are being used to help define FHIR resources.  The document resource enables access to "FHIR-based" documents as well as those that existed prior to the development of FHIR (like CCD or CCDA documents).  Present efforts in Blue Button Plus focus on the latter.