Automate Blue Button Initiative Content Workgroup Meeting November 19, 2012

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

Agenda 3 TopicTime Allotted Welcome and Announcements5 minutes Status, Deliverables, Dashboard5 minutes Draft Implementation Guide Review45 minutes Next Steps / Reminders5 minutes

Announcements and Reminders 4 Meeting Reminders – Content Workgroup Meetings are Mondays from 4:00 – 5:00 pm Eastern. – The next Community Meeting will be held as needed – Meeting information is on the Automate Blue Button Wiki Page:

Pre- Discovery Discovery Reference Implementations  Agreed and voted on charter, including  Scope  Timeline  Deliverables  Reviewed options to meet human readable + machine readable requirement  Reviewed use cases being developed by PUSH group  Began discussing implementation guidance for CONTENT, based on C-CDA requirement of MU 2  Write draft implementation guide for CONTENT  PUSH reference implementations  Other existing DOWNLOAD implementations that could serve as guidance Implementation Guidance Implementations  Refine implementation guide based on PUSH reference implementations  Refine implementation guide based on other known DOWNLOAD implementations  3-6 full implementations that reflect implementation guidance CLINICAL CONTENT Current Status Clinical Content Sub-Group 5

PUSH Current Deliverables Content Issues – What content format should be sent? What section and fields are required? – Should first transmission include entire health history or encounter only? – How should payload be packaged? Issues Being TackledUse Case Issue List (Not quite posted yet) 6 Clinical Content Sub-Group

ToC Guidance Demo WG Launch (09/17) Nov-12 Discovery S&I Framework Lifecycle Sep-12Mar-13 Pilot & Implementation Guidance Oct-12 Dec-12 Jan-13Feb-13 Reviewed and discussed options Identified Priority Standard (C-CDA) Finalize & Document Recommendations for PUSH Discussed options Identified C-CDA as priority Building recommendation Finalize recommendation Reconvene as needed Timeline Outstanding Issues Standards Identified Accomplishments Status Draft Implementation Guidance CLINICAL CONTENT Dashboard Reconvene As Necessary Clinical Content Sub-Group 7

Outstanding Questions Summary + Encounters What gets sent when a patient asks for a transmit? What gets sent when the transmit is automated?

Outstanding Questions XDR / XDM How will the files be packaged? Download – XDR/XDM Transmit - MIME

Outstanding Questions Documenting Transmit as Patient Initiated How do we remove the implied referral/action/burden ? Make it clear that this business case was generated by the patient Make sure this is placed in a standardized place “Class Code” might be able to show this (research further) How do we indicate that this came from the patient and not the doctor?

Next Steps 13 Next Steps – Review the new version of the IG Draft In Person Meetings: – Dec. 6 th Direct Connect-a-thon – Dec. 11 th ONC Annual Meeting – ABBI Townhall Meeting Reminders – Meeting information is on the Automate Blue Button Wiki Page: For questions, please contact your support leads – Initiative Coordinator: Pierce Graham-Jones (pierce.graham- – Presidential Innovation Fellow: Ryan Panchadsaram – Project Manager: Jennifer Brush – S&I Admin: Apurva Dharia

Useful Links Automate Blue Button Wiki – Content Sub Workgroup – Join the Initiative –