4
Beacon Community Program Build and Strengthen – Improve – Test innovation Beacon-EHR Vendor Full Affinity Group May 3, 2013

Beacon Community Program Build and Strengthen – Improve – Test innovation Beacon-EHR Vendor Full Affinity Group May 3, 2013

Embed Size (px)

DESCRIPTION

Work Plan Update 2 Work Plan Document Displayed on WebEx Update on Technical Discovery Guide – Behind Progress 7 Beacons have submitted information Western New York Southeast Michigan Tulsa Rhode Island Still Waiting on 6 Beacon Submissions Bangor, Utah, San Diego, New Orleans, Keystone Due next week Identification of Beacons/Vendors that will fit into each Transport Use Case (Behind Schedule) Identification of Specific Scenarios for Testing (Behind Schedule) Create a Schematic That Identifies Needed Actors for Each Scenario Southeast Minnesota Inland Northwest Mississippi

Citation preview

Page 1: Beacon Community Program Build and Strengthen – Improve – Test innovation Beacon-EHR Vendor Full Affinity Group May 3, 2013

Beacon Community ProgramBuild and Strengthen – Improve – Test innovation

Beacon-EHR Vendor Full Affinity GroupMay 3, 2013

Page 2: Beacon Community Program Build and Strengthen – Improve – Test innovation Beacon-EHR Vendor Full Affinity Group May 3, 2013

• Roll call – Greg Dengler• User Stories Update

• Finalized User Story – Bruce & Ed (Final Acceptance)• VDT User Story review – Kim & Alan (Displayed on Webex)

• Update on Having Paul Tuten’s Module from the MU2 Summit Presented to AG – Tone & Others• State HIE Joining Affinity Group – Chuck• Provider Friendly Slick Outlining Transport Pilots

Update – Chuck• Work Plan Progress – Greg Dengler • WIKI Development Update – Greg Dengler• TDG for Beacons Update – Greg Dengler• Wrap up/Next Steps – Tone

Today’s Goals

2

Page 3: Beacon Community Program Build and Strengthen – Improve – Test innovation Beacon-EHR Vendor Full Affinity Group May 3, 2013

3

Work Plan Update

• Work Plan Document Displayed on WebEx• Update on Technical Discovery Guide – Behind Progress

• 7 Beacons have submitted information• Western New York• Southeast Michigan• Tulsa• Rhode Island

• Still Waiting on 6 Beacon Submissions• Bangor, Utah, San Diego, New Orleans, Keystone

• Due next week• Identification of Beacons/Vendors that will fit into each

Transport Use Case (Behind Schedule)• Identification of Specific Scenarios for Testing (Behind

Schedule)• Create a Schematic That Identifies Needed Actors for Each

Scenario

• Southeast Minnesota• Inland Northwest• Mississippi

Page 4: Beacon Community Program Build and Strengthen – Improve – Test innovation Beacon-EHR Vendor Full Affinity Group May 3, 2013

Wrap Up/Next Steps

4

• Final comments• All attendees• Co-Chairs: Tone Southerland, Chuck Tyron

• Next steps• Conclusion

• Notable Links– EHRA White Paper

• http://himssehra.org/docs/EHRAStage2SecureHealthTransportCertificationandMeaningfulUse.pdf

– MU2 Summit Meeting Materials• http://wiki.statehieresources.org/Meaningful+Use+Stage+2+Excha

nge+Summit+-+April+18,+2013