1 3:00 PM, EST

2 Don Hewitt Vice President, Business Operations OSEHRA Ramina Toy Program Manager Brad Triebwasser BITS Team Lead Overview of VA Open Source Technical Support Contract Welcome to the OSEHRA Innovation Webinar

Open Source Technical Support and Working Group Services for VA VistA April 19, 2016

Refine understanding of VA’s unfilled requirements Advance community understanding and establish collaborative exploration of VA requirements Provide a visualization toolset to assist the community in understanding current VistA structure and interfaces Identify relevant candidate open source software and products for intake by VA “Tee up” these candidates for intake through analysis, prioritization, and certification Key Goals

Identifying The Right Candidates for VA Intake Open Source Search Open Source Software Repositories Technical Working Groups CBA Package for Quarterly Review Intake Recommendations VA Class III Code Analysis and Certification QUARTERLY IPR VA EPIP OIT PD VHA Designated Items

Analysis and Deliverables

Identify open source opportunities across VistA, focusing on Feature Set 3 for the initial quarters Develop the overarching concept for the gap analysis and mature it over several quarters Assess higher level gaps early, and increase the level of detail over several quarters Define the relationships of other content to the gap analysis, mature and synergize over time Analysis Approach

Quarterly Cycle Overview Prioritization Description Document Technical Working Groups Elaborate, Refine, and Prioritize Needs CBA Package for Quarterly Review Requirements Gap Analysis VA Product/ Software Selection Criteria SWOT Analyses  Features  Boundary Conditions  Identified Gaps  Code Maturity  Quantitative Selection Metric  Proposed Candidate Summaries  Analysis of Alternatives  Risk Analysis  Recommendations  SWOT Analysis  Gap Analysis  Selection Criteria  Prioritization Description Document Recurring Quarterly Cycle

Using the GFI provided: VistA 4 Product Roadmap, VistA 4 Product Architecture Document, Business Requirements Documents (BRD) Requirements Specification Documents (RSD) Produce a Gap Analysis of priority features and functions required to make progress with VA’s VistA vision, with primary emphasis on how that vision is elaborated in the Feature Set delivery schedule per the VistA 4 Product Roadmap. Gap Analysis

Implementation risk gap – where specific tactical implementation plans (applications, feature sets) may not be met – What VistA development projects are at risk of not meeting schedule or functional performance in the next two years? – What open source products can be used to mitigate this risk? Implementation Risk Gap Description

Vision gap – where the VistA Evolution strategic vision may not be met by currently planned implementations – What areas of VistA are not being developed due to other higher priority needs? – What open source products can be used to fill this vision gap? Vision Risk Gap Description

Purpose – Formally identify the Strengths, Weaknesses, Opportunities, and Threats associated with selected candidates for open source code intake Approach – Document the Business Objective of SWOT Analysis: Research and continuously scan the business and medical software and standards environment for trends and emerging elements. Conduct market research. – Identify the strengths of VA / VistA in context of the marketplace and industry – Assess and List – Opportunities for VA / VistA in the context of the marketplace and industry – Threats to the continuation and stability of VA / VistA – Integrate the lists of strengths, weaknesses, opportunities and threats – Rank Opportunities and Threats – Develop and enhance VA / VistA strategy to take advantage of the opportunities, overcome and mitigate threats, build on the strengths and reduce the weaknesses over time – Include the results of the SWOT strategy analysis in broader strategic and business planning SWOT Analysis

Purpose – To measure the degree to which open source candidates may fulfill the capability gaps. Approach – Identified open source software and product selection criteria based on industry best practices and experience – Added identified Feature Set 3 gaps as criteria for the initial quarters – Developed a selection criteria scoring tool to support analysis of candidates – Plan to mature the content over the next several quarters Open Source Software and Product Selection Criteria

Purpose – Document analysis findings for intake candidates Approach – Use SWOT and open source selection criteria analysis as input – Expand assessment with additional detail across multiple areas – Position candidate for VA intake assessment process – Mature approach over subsequent quarters Prioritization Description Document

Technical Working Groups (TWGs)

Designed to provide collaborative venues that combine VA and other community members Modeled after existing OSEHRA Groups, and fully integrated into group ecosystem Technical Working Groups

VistA Security Human Centric Design Cloud-Based Healthcare Delivery First Three Technical Working Groups

OSEHRA Web Site Enhancements

Suggestions for candidate software Participation on Technical Working Groups Feedback on posted documents Submission of code to OSEHRA Repository Participation in Certification Process – Code and documentation review – Certification calls Success is dependent upon community participation How Can You Help?

25 Questions?

Join Us For The 2016 OSEHRA Open Source Summit! Sponsorship & Exhibitor Opportunities Are Still Available! June 27-29, 2016: Bethesda North Marriott Hotel & Conference Center, MD summit.osehra.org