Beacon Community and EHR Vendor Collaboration: A Catalyst for Interoperability and Exchange

1. Beacon Community and EHR Vendor Collaboration: A Catalyst for Interoperability and Exchange ONC CMS Meaningful Use Stage 2 Exchange Summit March 18, 2013

2. Agenda • Welcome and introduction to the Beacon Vendor Affinity Group • Purpose the Affinity Group • Phase 1 Activities – focus on content • Pilots and Lessons Learned • Phase 2 Plans – focus on MU2 TOC transport • Questions

3. The Beacon Community Program: Where HITECH Comes to Life 17 communities each funded ~$12-16M over 3 yrs to: Build and strengthenhealth IT infrastructure and exchange capabilities - positioning each community to pursue a new level of sustainable health care quality and efficiency over the coming years. Improvecost, quality, and population health - translating investments in health IT in the short run to measureable improvements in the 3-part aim. Test innovative approaches to performance measurement, technology integration, and care delivery - accelerating evidence generation for new approaches.

4. 17 Diverse Communities Bangor Beacon CommunityBrewer, ME Western New York Beacon Community Buffalo, NY Beacon Community of Inland NorthwestSpokane, WA Southeastern Minnesota Beacon Community Rochester, MN Rhode Island Beacon Community Providence, RI Southeast Michigan Beacon Community Detroit, MI Keystone Beacon Community Danville, PA Central Indiana Beacon Community Indianapolis, IN Utah Beacon Community Salt Lake City, UT Greater Cincinnati Beacon Community Cincinnati, OH Colorado Beacon Community Grand Junction, CO Southern Piedmont Beacon Community Concord, NC Great Tulsa Health Access Network Beacon Community Tulsa, OK San Diego Beacon Community San Diego, CA Delta BLUES Beacon Community Stoneville, MS Hawaii County Beacon Community Hilo, HI Crescent City Beacon Community New Orleans, LA

5. Affinity Group Purpose • Promote the adoption, use and interoperability of EHR technology to advance the care improvement goals of impacted communities • Phase 1 use cases for CCD exchange (Nov 2011 – Jan 2013): • Update clinical registry or repository • Patient referral • Phase 2 – Guidance on MU2 (March – August 2013) • Test required and option transports for Transitions of Care (TOC) and View online, Download, and Transmit (VDT) • Explore implementation across trust exchanges both within and between communities

6. Phase I – Affinity Group (AG) Problems and Goals • The AG articulated 6 high priority problems that the group was charted to address • Information Exchange and Interoperability (4) • EHR adoption and Meaningful Use (1) • Quality Measure Reporting (1) • AG members laid out specific, time-bounded goals intended to address the identified problems

7. Full Affinity Group Participants

8. Affinity Group Governance • ONC Beacon-EHR Vendor Affinity Group Co-Chairs • Executive Steering Committee • 5 Beacon and 5 Vendor Representatives that guide the work of the Affinity Group • ONC Representative • Technical Support – Booz Allen Hamilton • Technical and Engagement Work Group co-chairs report out to this group

9. Phase 1 AG Accomplishments *This document provides an overview of each of the Beacon-EHR Vendor Engagement & Technical Work Group work products developed between January and December 2012

10. C83 Pilot Project Process • Goals of the C83 pilots • Sharing 66 high priority data elements • Ability to keep vendor IP confidential while providing value to the participants • Moving towards Stage 2 Meaningful Use • CCD Workflow

11. Phase 1 - C83 Pilot Metrics GRAND TOTAL (LIVE + PLANNED)

12. Sample CCD Workflow

13. Phase 1 - C83 Pilot Project Results • Recognized benefits of collaboration • Positive impact for patients • Willingness to continue towards MU2 • Direct needs to become “Real” • Vendors/communities are struggling with standards • Natural AG progression from MU Stage 1 focus

14. Mapping Data Elements to MU2

15. Phase 1 - Materials/Case Studies • Recent White Paper: Glide Path from HITSP C83 to C-CDA: Informed decision making for health information stakeholders: http://www.healthit.gov/policy-researchers-implementers/reports • Direct URL: http://www.healthit.gov/sites/default/files/glidepath_hitsp_c83_to_ccda.pdf • Vendors and Communities Working Together: A Catalyst for Interoperability and Exchange: http://www.healthit.gov/providers-professionals/vendors-and-communities-working-together-catalyst-interoperability-and-excha

16. Phase 2 – Problems & Goals • Problems will focus on required and optional transports for Transitions of Care and View online, Download, & Transmit as well as exchange across trust communities • Goals • Educate others • Build off existing work of others • Leverage Beacon AG established work • ID and engage community partners • Support MU2 TOC and VDT member certification • Pilot/test end-to-end connectivity for TOC • Deliver feedback and “Lessons Learned”

17. Affinity Group Participants

18. Phase 2 - Affinity Group Governance • Affinity Leadership Group • ONC Representative • Technical Support – Booz Allen Hamilton • 2 Co-Chairs (Beacon/Vendor) and 2 Vice-Chairs • Full ONC Beacon-EHR Vendor Affinity Group • 13 Beacons and 6 Vendor Representatives that guide the work of the Affinity Group

19. Direct Model • Transport Options • Direct (Required) • Direct + XDR/XDM (Optional) • SOAP + XDR/XDM (Optional) • TOC Alternative Query-based exchange → eHealth Exchange

20. Discussion For more information on the Beacon Community Program, please contact Christina.Markle@hhs.gov and download Beacon Community Fact Sheets at http://www.healthit.gov/policy-researchers-implementers/beacon-community-program