The Patient Choice Technical Project Pilots Working Group May 20, 2016.

Slides:



Advertisements
Similar presentations
EDOS Workgroup Update July 16, 2013 Laboratory Orders Interface Initiative.
Advertisements

EDOS Workgroup Update June 4, 2013 Laboratory Orders Interface Initiative.
EDOS Workgroup Update Laboratory Orders Interface Initiative.
EDOS Workgroup Pilots – Kickoff Teleconference October 2, 2012.
EDOS Workgroup Update Laboratory Orders Interface Initiative.
EDOS Workgroup Update June 18, 2013 Laboratory Orders Interface Initiative.
1 April 2010 TX SET Timeline Project Conceptualization 11 weeks Market Requirements 12 weeks ERCOT Requirements 12 weeks Conceptual Design 6 weeks Detail.
ELTSS Plan Content Sub-Work Group Week 7 Meeting June 16, :00am–12:00pm 1.
Longitudinal Coordination of Care Pilots WG Monday, March 10, 2014.
Automate Blue Button Initiative Push Workgroup Meeting January 7, 2013.
Automate Blue Button Initiative Push Workgroup Meeting December 17, 2012.
Electronic Submission of Medical Documentation (esMD) Author of Record Workgroup Wednesday, July 18,
Electronic Submission of Medical Documentation (esMD) Complete Documentation Templates IG Ballot Reconciliation April 2, 2014.
Data Access Framework (DAF) All Community Meeting September 4th, 2013.
1 Collaboration and Concept Exploration Nationwide Health Information Organization (NHIO) Gateway March 28, 2007.
Data Access Framework All Hands Community Meeting 1 September 23, 2015.
SIM- Data Infrastructure Subcommittee November 14, 2013.
Electronic Submission of Medical Documentation (esMD) Author of Record Workgroup and Harmonization of UC 1&2 Workgroup Friday, September 21,
EsMD PPA Use Case 2 WG Meeting Wednesday, March 21 st, 2012.
EHR-S Functional Requirements IG: Lab Results Interface Laboratory Initiative.
Data Access Framework All Hands Community Meeting February 5, 2014.
Automate Blue Button Initiative Pull Workgroup Meeting November 20, 2012.
Electronic Submission of Medical Documentation (esMD) eDoC eClinical Templates on FHIR using Structured Data Capture Use Case May 13, 2015.
Data Access Framework All Hands Community Meeting June 18, 2014.
Data Provenance Tiger Team May 27 th, 2014 Johnathan Coleman Johnathan Coleman - Initiative Coordinator Lynette ElliottLynette Elliott – Tiger Team Support.
EsMD Structured Content Use Case 2 WG Meeting Friday, April 20 th, 2012.
EDOS Workgroup Update May 21, 2013 Laboratory Orders Interface Initiative.
Health eDecisions (HeD) HL7 Ballot Examples November 28, 2012.
Longitudinal Coordination of Care (LCC) Workgroup (WG) HL7 Tiger Team Service Oriented Architecture (SOA) Care Coordination Services (CCS) May 1, 2013.
Electronic Submission of Medical Documentation (esMD) AoR L2 Harmonization July 3, 2013.
Electronic Submission of Medical Documentation (esMD) eDoC eClinical Templates on FHIR using Structured Data Capture Use Case May 13, 2015.
Data Segmentation for Privacy November 16 th, 2011.
Electronic Submission of Medical Documentation (esMD) eDoC Workgroup November 4, 2015.
Longitudinal Coordination of Care (LCC) Workgroup (WG) LCC All Hands Meeting April 4,
Data Access Framework All Hands Community Meeting 1 November 4, 2015.
Data Access Framework All Hands Community Meeting April 2, 2014.
The Patient Choice Project Project Kickoff December 14 th, 2015.
Electronic Submission of Medical Documentation (esMD) Electronic Determination of Coverage PMD User Story & Harmonization August 7, 2013.
Data Access Framework All Hands Community Meeting 1 November 18, 2015.
Electronic Submission of Medical Documentation (esMD) Author of Record Workgroup Friday, June 29,
Electronic Submission of Medical Documentation (esMD) Author of Record Workgroup April 3, 2013.
The Patient Choice Project Use Case Working Session January 8 th, 2016.
Electronic Submission of Medical Documentation (esMD) eDoC Home Health April 9, 2014.
Structured Data Capture (SDC) All Hands Meeting February 21, 2013.
Structured Data Capture (SDC) Pilots Template Insert the Name of Your Pilot / Organization Here MM/DD/YYYY.
Electronic Submission of Medical Documentation (esMD) Electronic Determination of Coverage Harmonization August 14, 2013.
Data Access Framework All Hands Community Meeting April 9, 2014.
The Patient Choice Project Use Case Working Session February 12 th, 2016.
The Patient Choice Project Use Case Working Session February 5 th, 2016.
The Patient Choice Project Use Case Working Session January 22 nd, 2016.
The Patient Choice Project Use Case Working Session January 29 th, 2016.
EDOS Workgroup Update Laboratory Orders Interface Initiative.
Workgroup Introduction & Trust Mark Briefing Transport & Security Standards Workgroup September 22, 2014.
Health eDecisions (HeD) All Hands Meeting November 29, 2012.
Data Provenance Tiger Team June 2, 2014 Johnathan Coleman Johnathan Coleman - Initiative Coordinator Lynette ElliottLynette Elliott – Tiger Team Support.
Electronic Submission of Medical Documentation (esMD) eDoC eClinical Templates on FHIR using Structured Data Capture Use Case May 27, 2015.
Data Access Framework All Hands Community Meeting 1 February 10, 2016.
Data Access Framework (DAF) All Community Meeting July 31, 2013.
[INSERT THE NAME OF YOUR PILOT ORGANIZATION] INSERT DATE.
Data Provenance All Hands Community Meeting May 19th, 2016.
Electronic Submission of Medical Documentation (esMD) Author of Record L2 Harmonization March 26, 2014.
EDOS Workgroup Pilots – Engagement Plans. Meeting Etiquette Remember: If you are not speaking keep your phone on mute Do not put your phone on hold –
Longitudinal Coordination of Care LCP SWG Thursday, April 25, 2013.
Data Access Framework All Hands Community Meeting 1 March 23, 2016.
Structured Data Capture (SDC) All Hands Meeting May 26, 2016.
Automate Blue Button Initiative Push Workgroup Meeting December 10, 2012.
Structured Data Capture (SDC) Community Meeting August 18, 2016.
Laboratory Orders Interface Initiative
The School Point of View
Project Kick-off <Customer Name> <Project Name>
Presentation transcript:

The Patient Choice Technical Project Pilots Working Group May 20, 2016

Call Logistics 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 This meeting is being recorded Feel free to use the “Chat” feature for questions, comments or any items you would like the moderator or participants to know 2

Agenda Announcements Pilots Working Group »Department of Veteran Affairs Pilots Introductions Questions and Discussion 3

Announcements The Pilots Working Group meeting time/day will continue to be held bi- weekly on Fridays at 11am ET »The next meeting will be held Friday June 3 rd, 2016 The final Phase 1: Basic Choice Use Case has been posted to the project confluence » 4

Move Health Data Forward Challenge The Move Health Data Forward Challenge encourages participants to create an application programming interface (API) solution that uses the implementation specifications created by the HEART Workgroup (Heart WG) to allow people to securely authorize the movement of their health data to destinations they choose. The Challenge will have three phases and two finalists each winning $75,000. »Phase 1 will award $5,000 for up 10 finalists each based on the proposals they submit to the Challenge. »Phase 1 winners will move to Phase 2, which will award $20,000 for up to 5 finalists each based on the prototype of their Solution. »Phase 2 winners will move to Phase 3, which will award $50,000 for up to two winners each based on the participant’s ability to implement their Solution. Submission Dates: 12 a.m. ET, May 10, :59 p.m. ET, Sep 08, 2016 For more information visit data-forward-challenge/ data-forward-challenge/ 5

The High Impact Pilots (HIP) ONC is excited to announce a new cooperative agreement program called the High Impact Pilots (HIP). This new approach implements HIT Standards Committee recommendations, continues ONC’s investment toward implementing the Nationwide Interoperability Roadmap, and fits within the ONC Tech Lab’s focus on pilots for standards and technology. The program is intended to catalyze the implementation of standards and technology that can be used to: »Improve the sharing of health information among health care stakeholders »Improve care delivery »Demonstrate how health IT can positively impact patient experience. The total funding available for HIP awards is $1.25 million (no less than 3 awards and no more than 7 awards are expected). The award period is expected to be a 12-month period of performance. Interested applicants are encouraged to attend the Information Session from 2:00 p.m. – 3:00 p.m. ET on May 23 (HIP). The FOA is open now until July 8, 2016.Information Session For more information visit 6

Phase 1 - Timeline 7 Nov Dec Jan FebMar AprMayJunJulyAugSeptOctNov (Today) Begin Pilot Work Kick Off Pilot Activities Use Case Working Group Kick Off Session Conduct Pilots Needs Assessment Review and development of formal use cases Develop Best Practices IG Draft Basic Choice Standard

Pilots Working Group 8

Pilots Updates The Department of Veteran Affairs will be joining us as a piloting organization »Specific details will be discussed on their pilots introduction presentation 9

Department of Veteran Affairs Presentation 10

Department of Veteran Affairs May 20, 2016

DVA: Introduction Participating Organization(s) »DVA, EPIC Point of contact(s) »Mike Davis, VHA Security Architect, »Joseph Kevin, Background »VA currently operates under 38USC7332 restrictions which requires patient consent prior to sending information regarding HIV, Sickle Cell Anemia or Drug/Alcohol Abuse. 12

DVA: Business Drivers & Use Case What is the real world problem/challenge this pilot will help solve? »Solving obtaining patient authorizations from external partners as an obstacle to care. How does this challenge align with The Patient Choice Technical Project Use Case scenarios? »Scenario 1: Provider pushes Consent Directive to Consent Directive Repository (PUSH) Are there alternative scenarios that you would intend to pilot? TBD 13

DVA: Scenario 1: Provider pushes Consent Directive to Consent Directive Repository (PUSH) What is your high-level information flow? »Per Patient Choice sequence diagram »What components of the information flow currently exist and which will be new for the pilot? –Veteran Authorization Preferences Repository –Enterprise Access Control Service Describe your technical solution and implementation plan? »Architecture-Integrate CD received from external source into current automated CD system upgrade program. »Standards used - 14

DVA: Timeline & Resources Timeline »Projected Start Date: June 2016 »Projected End Date: September 2016 Dependencies/Major Milestones: »Project approval June 2016 »Contract TO award June 2016 »Receive and Store CD Jul 2016 »Deprecate existing CD as needed Jul 2016 »Go-live Aug 2016 Resources »Available resources »VHA Architecture Emerging Health Technologies Advancement Center Lab »VAP Developer Team »VHA ROI, Privacy Staff »EPIC Development Team Resource constraints »All resources have multiple commitments. Risks »Failure to execute new Contract TO 15

[INSERT THE NAME OF YOUR PILOT ORGANIZATION] INSERT DATE

[Insert Organization Name]: Introduction Participating Organization(s) »[insert] Point of contact(s) »[Insert Name + Title], [Insert ] Background »[Any information relevant to patient choice and piloting] 17

[Insert Organization Name]: Business Drivers & Use Case What is the real world problem/challenge this pilot will help solve? How does this challenge align with The Patient Choice Technical Project Use Case scenarios? »Scenario 1: Provider pushes Consent Directive to Consent Directive Repository (PUSH) »Scenario 2: Provider pushes Consent Directive to HIE and Immunization Registry (PUSH) »Scenario 3: HIE Consent Directive Repository (PULL) »Scenario 4: HIE/Immunization Registry Consent Directive Repository (PULL) »Scenario 5: Hospital Consent Directive Repository (PULL) Are there alternative scenarios that you would intend to pilot? 18

[Insert Organization Name]: [Insert relevant use case scenario title] What is your high-level information flow? »Block diagram, sequence diagrams etc. »What components of the information flow currently exist and which will be new for the pilot? Describe your technical solution and implementation plan? »Architecture »Standards used 19

[Insert Organization Name]: Timeline & Resources Timeline »Projected Start Date: [Insert date] »Projected End Date: September 2016 »Dependencies/Major Milestones: [Insert date(s)] Resources »Available resources –staff, partnerships(business agreements) etc. »Resource constraints –Include possible solution/work-around Risks 20

Questions? 21

Next Steps The Pilots Working Group meeting time/day will continue to be held bi- weekly on Fridays at 11am ET »The next meeting will be held Friday June 3 rd, 2016 Continue to coordinate and support development of introductory slides 22

Project Links Project Homepage hnical+Project+Homepage hnical+Project+Homepage Use Case Development Pilots Homepage Project Materials and References 23

Project Contact Information OCPO-ONC LeadJeremy Project CoordinatorJohnathan Project ManagerAli Project SupportTaima Staff SMEKathleen Staff SMEDavid 24

Thank you!