Download - Automate Blue Button Initiative Content Workgroup Meeting

Transcript
Page 1: Automate Blue Button Initiative Content Workgroup Meeting

Automate Blue Button Initiative Content Workgroup Meeting

November 19, 2012

Page 2: Automate Blue Button Initiative Content Workgroup Meeting

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 recordedo 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

Page 3: Automate Blue Button Initiative Content Workgroup Meeting

Agenda

3

Topic Time Allotted

Welcome and Announcements 5 minutes

Status, Deliverables, Dashboard 5 minutes

Draft Implementation Guide Review 45 minutes

Next Steps / Reminders 5 minutes

Page 4: Automate Blue Button Initiative Content Workgroup Meeting

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:

http://wiki.siframework.org/Automate+Blue+Button+Initiative

Page 5: Automate Blue Button Initiative Content Workgroup Meeting

Pre-Discover

y

Discovery

Reference Implementatio

ns

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

Page 6: Automate Blue Button Initiative Content Workgroup Meeting

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

Page 7: Automate Blue Button Initiative Content Workgroup Meeting

ToC Guidance Demo

WG Launch(09/17)

Nov-12

DiscoveryS&I Framework Lifecycle

Sep-12 Mar-13

Pilot & Implementation Guidance

Oct-12 Dec-12 Jan-13 Feb-13

Reviewed and discussed options

Identified Priority Standard (C-CDA)

Finalize & Document Recommendations for PUSH

Discussed optionsIdentified C-CDA as priorityBuilding recommendationFinalize recommendationReconvene as needed

Timeline

Outstanding Issues

Standards Identified

Accomplishments Status

Draft Implementation Guidance

CLINICAL CONTENT Dashboard

Reconvene As Necessary

Clinical

Content Sub-

Group

7

Page 8: Automate Blue Button Initiative Content Workgroup Meeting
Page 9: Automate Blue Button Initiative Content Workgroup Meeting
Page 10: Automate Blue Button Initiative Content Workgroup Meeting

Outstanding Questions

Summary + Encounters

• What gets sent when a patient asks for a transmit?

• What gets sent when the transmit is automated?

Page 11: Automate Blue Button Initiative Content Workgroup Meeting

Outstanding Questions

XDR / XDM

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

Page 12: Automate Blue Button Initiative Content Workgroup Meeting

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?

Page 13: Automate Blue Button Initiative Content Workgroup Meeting

Next Steps

13

• Next Steps– Review the new version of the IG Draft

• In Person Meetings: – Dec. 6th Direct Connect-a-thon– Dec. 11th ONC Annual Meeting – ABBI Townhall

• Meeting Reminders– Meeting information is on the Automate Blue Button Wiki Page:

http://wiki.siframework.org/Automate+Blue+Button+Initiative

• For questions, please contact your support leads– Initiative Coordinator: Pierce Graham-Jones ([email protected])– Presidential Innovation Fellow: Ryan Panchadsaram (

[email protected])– Project Manager: Jennifer Brush ([email protected])– S&I Admin: Apurva Dharia ([email protected])

Page 14: Automate Blue Button Initiative Content Workgroup Meeting

Useful Links

• Automate Blue Button Wiki– http://wiki.siframework.org/Automate+Blue+Button+Initiative

• Content Sub Workgroup– http://wiki.siframework.org/ABBI+Content+Sub+Workgroup

• Join the Initiative– http://wiki.siframework.org/Automate+Blue+Button+Join+the+Initiative

14