1 / 13

Beacon Community Program Build and Strengthen – Improve – Test innovation

Beacon Community Program Build and Strengthen – Improve – Test innovation. Beacon-EHR Vendor Full Affinity Group July 19, 2013. Today’s Goals. Full AG Roll call – Lynda Rowe

cassady-roy
Download Presentation

Beacon Community Program Build and Strengthen – Improve – Test innovation

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Beacon Community ProgramBuild and Strengthen – Improve – Test innovation Beacon-EHR Vendor Full Affinity Group July 19, 2013

  2. Today’s Goals • Full AG Roll call – Lynda Rowe • Update on Beacon Transport Pilot Progress – Chuck Tryon/Lynda Rowe/Bruce Wiegand/ Lou Della Posta/Daniel Thomas/Kim Chaundy • HeatheWay Presentation Discussion/Questions – Greg Dengler • Wrap up/Next Steps – Chuck Tryon

  3. Beacon Pilot Progress • Tulsa – In Progress • Working on developing pilot option 9+ as well as the details behind numerator denominator calculations • Mississippi – In Progress • Discussions in progress with Allscripts around pilot options, call scheduled for 10:00am Monday 7/22 • South East Michigan – In Progress • Went online with one Allscripts practice this week using XDS.b as the transport mechanism in an effort to work toward eHealth exchange • Looking to add an additional Allscripts practice in the next week as well • In reference to User Story 2b, SE Michigan is working with Success EHS to pilot PIX and XDS.b Query & Retrieve, with automatic triggers to query our MPI and XDS.brepository to retrieve a longitudinal CDA • Keystone – Not Able to Run Pilots at This Time • RIQI – In Progress • Pilot: ToC: CEHRT to an HIO/HIE/HISP - Query by Provider B • Currently: data is being sent from Provider A, Blackstone Valley, and it is being stored within the HIE (discrete data and the document itself). • To be completed as soon as next week: Quantifying view of the data by Provider B. • WNY – In Progress • Direct accounts have been established for Elmwood and staff training has commenced on the use of Direct email. • Mirth is working on the automation process, in the meantime Neva will send files to Elmwood. • Go live is planned for 07/23 with Direct function to be implemented shortly there after.

  4. Possible Pilot Scenarios 1 - 5

  5. Possible Pilot Scenarios 6 - 10

  6. Vendor Pilot Options

  7. Vendor Pilot Options

  8. HealtheWay Presentation Important Points • HealtheWay is looking for continued collaboration with Beacon Communities • Benefits of eHealth Exchange Membership • Standardized exchange structure • One “trust community” to join allows trust relationships across many systems • MU 2 ToC Support • Standardized on-boarding process with testing using CCHIT • Management of digital certificates by the eHealthExchange • Annual cost is variable depending on an organizations annual revenue • < $1M = $4,750/year • $1 - $10M = $9,950/year • More than $10M = $19,900/year

  9. HealtheWay Interoperability • What do the eHealth Exchange HIE Certified Stamps Mean • Framework for tightly specified implementation- level requirements for production level interoperability built on the national standards set forth by ONC/CMS which are able to be tested • 3 Seals able to be obtained by Vendors (HIE/EHR) to show plug and play capability with eHealth Exchange members

  10. eHealth Exchange HIE Certified – Community • Geared toward a “Gateway” and the organizations behind a “Gateway” • A “Gateway” is simply the ability of an HIE to take records from their internal community and transpose them if needed into the exchange standards needed to be part of the eHealth Exchange, or vice versa • EMRs to an “ eHealthExchange Gateway” or “Gateway “to “Gateway” • Superset of the Network exchange and encompasses HIE to HIE exchange as well as exchange inside an HIE • Allows information to be shared within your own “HIE community” as well as HIE communities outside your own (ie Beacon to Beacon Tulsa to Detroit)

  11. eHealth Exchange HIE Certified – Direct • Interoperability standards and security for the Direct project • Allows organizations without a full established HIE community to have trust relationships with any other eHealth Exchange member, therefore a Direct message could be sent to any participating eHealth Exchange member

  12. eHealth Exchange HIE Certified – Network • Maps 1:1 with the eHealthExchange specifications: • Patient discovery • Query for Documents • Aligns to eHealthExchange message platform and underlying framework which allow for the transport to be secure and ensures patient consent • An HIE whose sole purpose is to exchange information between eHealth Exchange members (No underlying community of health systems and practices the HIE facilitates exchange between)

  13. Wrap Up/Next Steps • Final comments • All attendees • Co-Chairs: Chuck Tryon • Next steps • Conclusion

More Related