Automate Blue Button Initiative 08222012


Published on

Published in: Health & Medicine, Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Automate Blue Button Initiative 08222012

  1. 1. Automate Blue Button InitiativeAll Hands Community MeetingAugust 22, 2012
  2. 2. Meeting Etiquette • Remember: If you are not speaking, please keep your phone on mute • Do not put your phone on hold. If you need to take a call, hang up and dial in again when finished with your other call o Hold = Elevator Music = frustrated speakers and participants • This meeting is being recorded o Another reason to keep your phone on mute when not speaking • Use the “Chat” feature for questions, comments and items you would like the moderator or other participants to know. o Send comments to All Panelists so they can be addressed publically in the chat, or discussed in the meeting (as appropriate). From S&I Framework to Participants: Hi everyone: remember to keep your phone on mute  All Panelists 2
  3. 3. Agenda Topic Time Allotted Welcome and Announcements 10 minutes Call to Action 5 minutes Project Charter Review 40 minutes Workgroup Formation 20 minutes Consensus Process Overview (time permitting) 10 minutes Next Steps / Reminders 5 minutes 3
  4. 4. Current Registrants • Access My Records, Inc. • • ADHS • Laboratory Corporation of America • Allscripts • Louisiana Dept of Health and Hospitals • American Academy of Family Physicians • McKesson • American College of Physicians • Microsoft • AORN • Napersoft • Cerner • Optum • Data Exchange Specialist California Immunization • OrionHealth Registry • Sager Systems • Department of Defense (Booz Allen Hamilton • Patient First Contractor) • Patients as Partners • Dossia • Regulatory Informatics • Ep-Con • RelayHealth • eRECORDS, Inc • Ricoh Healthcare • Florida Hospital • Sutter Medical Center of Santa Rosa • CakeHealth • Thotwave Technologies, LLC. • Humetrix • Transformations at the Edge (TATE) • Gartner • UnitedHealth Group • Gorge Health Connect, Inc. • US Army • Health Information Xperts • Veterans Affairs • HealthURL • Videntity • Healthwise and HITSC FACA • WellSpan Health • HHS • Wittie, Letsche & Waldo, LLP • Hunter College • IMS Health • IPS Technology Services JOIN THE INITIATIVE: e+Blue+Button+Join+the+Initiative 4
  5. 5. Announcements • The Automate Blue Button Initiative will hold weekly community meetings on Wednesdays at 3:00 pm Eastern. – To participate, please see the “Attend the Weekly Community Meeting” section of the Automate Blue Button Wiki Page: • Weekly Meetings Please check the meeting schedule weekly as the meeting link and call in numbers will change 5
  6. 6. ABBI WikiOrientation Quick Links Weekly Meetings Calendar Community Schedule Contacts
  7. 7. Call to Action • You’re Invited! We need experts to develop standards, organizations ready to drive towards implementation, innovators to push the envelope, and patients and providers willing to provide their perspective. • Your commitment and participation are critical to our success and the ability to provide patients and their families with electronic access to their health data when and where it is needed. • To join the Automate Blue Button Initiative, go here: read about the commitment process and fill out the “Join the Initiative” form at the bottom of the page. 7
  8. 8. Project Charter Review • This is your opportunity to provide input! • We will discuss each section of the Project Charter in the community meeting. • Updates will made to the wiki after the meeting. – • Please also review and comment on the wiki after the meeting. Review and Comment 8
  9. 9. Automate Blue Button Project CharterChallenge and Goals • Challenge – How can we advance the implementation standards, tools, and services associated with the Blue Button to provide consumers with automated updates to their health information in a human readable and machine readable format? • Goals – PUSH: Automating transmission of personal health data to a specific location, using the Blue Button – PULL: Allowing a third party application to periodically access personal health data, using the Blue Button 9
  10. 10. Automate Blue Button Project CharterScope Statement • Identify, define, and harmonize implementation standards, tools and services that facilitate the automated PUSH and automated PULL of patient information via the Blue Button • Identify, define and harmonize content structures and specifications for the Blue Button so that information downloaded is machine readable and human readable • Identify, define, and harmonize protocols around identification and credentialing, and protocols around access and authorization, that facilitate the automated PUSH and automated PULL of patient information via the Blue Button 10
  11. 11. Automate Blue Button Project CharterValue / Vision Statement Consumers want more access to and portability from their health care information. They want to be able to: • Better understand their health and make more informed decisions • Help to make sure that they and all of their care team members are on the same page • Improve the accuracy and completeness of the information • Plug it into apps and tools that promise to make information truly available when and where it’s neededc 11
  12. 12. Automate Blue Button Project CharterSuccess Metrics For dataholders: • Number of existing BB dataholders that implement Auto Blue Button • Number of new dataholders that take the pledge and implement Auto Blue Button For patients: • Number of patients that access their data using Blue Button • Number of patients that use new features of Blue Button (both push and pull) For third-parties: • Number of application developers parsing Blue Button data • Number of patients using applications that are powered by Blue Button 12
  13. 13. Automate Blue Button Project CharterTarget Milestones & Timelines Driving Milestones • Pilot Push implementation by November 22, 2012 • Pilot Pull implementation by March 3, 2013 13
  14. 14. Automate Blue Button Project CharterExpected Deliverables • Workgroup Charters • Use Case(s) and Functional Requirements • Standards for Blue Button • Implementation Guidance for Blue Button • Tool development to support Blue Button • Pilots and results 14
  15. 15. Automate Blue Button Project CharterRelevant Standards & Stakeholders • DIRECT: A set of transport standards, services, and use cases that any data holder or receiver can implement, to package and send/receive electronic health information in a private and secure fashion. • ToC Content Recommendations: Recommendations on document structures to fulfill Meaningful Use Stage 2 Transitions of Care requirements (consolidated CDA). ( • OAuth & OpenID: Community-developed, industry-standardized protocols for authentication and authorization. (Note: The FHA is currently developing a RESTful approach to information exchange that leverages OAuth and OpenID.) • LRI Content Recommendations: Recommendations on document structures for Lab Interfaces to electronic health records • RHEx: Working on security standards (OpenID and OAuth) and content standards (working now) for applying a RESTful design approach to exchanging health information. • OSEHRA is an open, collaborative community of users, developers, and companies engaged in advancing electronic health record software and health information technology • Markle Foundations recommendations for Blue Button (including privacy and security specifications) • Work to create and encourage adoption of a new CCD to Blue Button “Transform tool” (to support OPM request) • Work underway to specify use cases for using EHRs and DIRECT to transmit updated summaries of care to a patient as they become available. 15
  16. 16. Proposed Workgroups Automating transmission of personal health data to a specific location • Discovery: review existing standards and formulate project charter and scope Push • Work on use cases Project • Define deliverables and timeline • Scope input needed on content and privacy and security Allowing a third party application to periodically access my personal health data Pull • Discovery: review existing standards and formulate project charter and scope Project • Work on use cases • Define deliverables and timeline • Scope input needed on content and privacy and security A Blue Button file must be machine-readable and human-readable Content Sub-Group • Review existing efforts and standards to leverage • Develop plan to support PUSH and PULL projects 16
  17. 17. Workgroup 1: Push PUSH Automating transmission of personal health data to a specific location EXAMPLE USE CASES By patient request, a provider can specify in an A patient can specify in a dataholder’s system to EHR that a patient be sent an updated copy of be sent an updated copy of his/her personal his/her personal health information as it becomes health information as it becomes available. available REQUIREMENTS & IN SCOPE OUT OF SCOPE ASSUMPTIONS (TO BE CONSIDERED) (NOT TO BE CONSIDERED) • Patient/Provider is already • Transport standards, • Policy concerns and authenticated in services, and specifications constraints. This initiative dataholder’s system. • Content standards: will define the mechanism, • Transport must be secure whether or not to include – how and where they • Data sent must be both in implementation guide(s) apply it will be up to state human-readable and • Implementation guide(s) to and local laws machine-readable support use case(s), building off existing standards 17
  18. 18. Workgroup 2: Pull PULL Allowing a third party application to periodically access my personal health data EXAMPLE USE CASE A patient can direct a third party application to periodically have access to his/her personal health information via the internet. The dataholder will ensure this data is made available and follow certain privacy and security standards. REQUIREMENTS & IN SCOPE OUT OF SCOPE ASSUMPTIONS (TO BE CONSIDERED) (NOT TO BE CONSIDERED) • Data must be transmitted • Authentication, transport, • Policy concerns and securely and content standards. constraints. This initiative • Patient must give • Leverage REHx project will define the mechanism, application consent to pull (Oauth and OpenID) – how and where they health information from • Leverage ToC project apply it will be up to state data holder • Leverage lab interface and local laws • Data sent must be both project human-readable and machine-readable 18
  19. 19. Sub-Group: Content CONTENT A Blue Button file must be both machine-readable and human-readable. EXAMPLE USE CASES A patient can download a copy of his/her records A patient can point a software or web application and is able to read and print it out. to their Blue Button file and it can parse it. REQUIREMENTS & IN SCOPE CHALLENGES ASSUMPTIONS (TO BE CONSIDERED) • File must be both human- • Leverage work done by HL7 • A cross-platform file that is readable on multiple and Consolidated CDA self contained. platforms: PC, Mac, iOS, • Leverage work done by the • Enabling easy-parsing of and Android ToC S&I Initative the file. Should take a • File must be printable developer less than 3 • File needs to be machine minutes to use. readable 19
  20. 20. Consensus on the Project Charter For those of you who are committed members, we ask you to vote on the Automate Blue Button Project Charter: • Yes – A Yes vote does not necessarily mean that the deliverable is the ideal one from the perspective of the Initiative Member, but that it is better to move forward than to block the deliverable • Yes with comments – If a Consensus Process attracts significant comments (through Yes with comment votes), it is expected that the comments be addressed in a future revision of the deliverable. • Formal Objection- with comments indicating a path to address the objection in a way that meets the known concerns of other members of the Community of Interest. "Formal Objection" vote without such comments will be considered Abstain votes. – A Formal Objection means that the objector cannot proceed with the project unless the objections are met. It is acceptable and expected to use a Formal Objection in a first consensus round to communicate a point of view or process issue that has not been addressed in the drafting of the initial deliverable. – Should a Consensus Process attract even one "Formal Objection" vote with comments from an Initiative Member, the deliverable must be revised to address the "Formal Objection" vote (unless an exceptional process is declared). • Abstain (decline to vote) Note: Each Organization, no matter the number of Committed Members only receives 1 Vote. If there are multiple committed members from your organization please verify your collective vote with them
  21. 21. Submitting your Vote 1. Review the Project Charter: 1 – te+Blue+Button+Project+Charter 2. Complete the Voting Form: – NOTE: You must be a Committed Member to Vote • Yes • Yes with comments. 2 • Formal Objection • Abstain (decline to vote) 3. Submit your Vote 3 4. A Message is displayed verifying your vote was recorded 4 21 21
  22. 22. Viewing your vote 5. View and track your Vote. (Voting record is directly below the Voting Form. • Note: you may need to refresh your browser to see your vote 5 Automate Blue Button Project Charter Consensus Vote Jane Smith Committed Member Note: All Consensus Votes are due Sept 17th by 8:00 pm EST 22
  23. 23. Next Steps • Next Steps – Comment on the Project Charter: – • Next Work Group Meeting – 3:00pm - 4:30pm Eastern, Wednesday, August 29, 2012 – • All ABBI (ABBI) Announcements, Meeting Schedules, Agendas, Minutes, Reference Materials, Use Case, Project Charter and general information will be posted on the HeD Wiki page – 23
  24. 24. Contact InformationFor questions, please contact your support leads • Initiative Coordinator: Pierce Graham-Jones ( • Subject Matter Experts: to be announced • Project Management: Jennifer Brush ( • S&I Admin: Apurva Dharia ( 24
  25. 25. Useful Links • Automate Blue Button Wiki – • Join the Initiative – • Automate Blue Button Project Charter – 25