HealtheVet Overview

1. HealtheVet Overview

2. 2 Agenda: HealtheVet Overview Definition Customer objectives and expectations HealtheVet components and technical approach Assumptions, Risks, and Challenges Summary

3. 3 HealtheVet Overview HealtheVet: “This initiative will incorporate new technology, new or reengineered applications, and data standardization to improve the sharing of, and access to, health information, which in turn, will improve the status of veterans’ health through more informed clinical care.” Statement of the Honorable R. James Nicholson, Secretary of Veterans Affairs, before the House Committee on the Budget, March 1, 2007 In effect, the reengineering and rehosting of VistA

4. 4 HealtheVet Overview: VHA Objectives

5. 5 HealtheVet Overview: Customer Expectations

6. 6 HealtheVet Overview: Baseline Scope

7. 7 HeV Blocks Core HealtheVet (HeV) - Blocks I and II to progress as quickly as can be executed Remaining HeV Blocks - Integrated schedule and sequence to be developed based on dependencies, ability to execute, funding, and VHA priorities

8. 8 Core HealtheVet Program Capability

9. 9 Core HealtheVet Program Capability

10. 10 HealtheVet Block I Initial Operational Capability (IOC): Fiscal Year (FY) 2008 Full Operational Capability (FOC): FY 2013 Build Common Services, Database and Testing Capabilities Health and Administrative Data Repositories (HDR/ADR) Clinical Data Warehouse Identity Management (Person and Organization Services) Security Archive and Audit Services Messaging & Interface Services/Enterprise Service Bus Deployment Toolkit Transition Application Modules Enrollment Scheduling Major Milestones: FY08: Enrollment Beta & National Release; Scheduling Alpha Release FY09: Scheduling Beta & National Release

11. 11 HealtheVet Block II IOC: FY 2008 FOC: FY 2015 Continue Building Out Common Services Workflow Engine Business Rules Engine Standards and Terminology Services Transition Application Modules Laboratory Pharmacy Bar Code Expansion Major Milestones: FY08: Deploy Pharmacy Drug Dosage Checking (PEPS 0.5) FY09: Deploy Pharmacy Drug Dosage Checking (PEPS 1.0) FY10: Begin National Fielding of Laboratory FY11: Begin National Fielding Re-Engineered Pharmacy for HeV

12. 12 HealtheVet Block III IOC: To Be Determined (TBD) FOC: TBD

13. 13 HealtheVet Block IV Intake/Output Order Check Expert Order Entry/Results Reporting Outpatient Clinical Care Problem List Progress Notes Remote Order Entry System Text Integration Utilities Vitals/Measurements Women’s Health

14. 14 HealtheVet Block V

15. 15 HealtheVet Block VI

16. 16 Development Strategy HealtheVet Phased transition constrained by budget, program executability, and risk First block includes development of software infrastructure and development of core applications Common software services such as security, identity management, alerts and audits Data stores; software architecture consistent with any mix of local and regional data processing centers, as required to meet Service Level Agreement requirements for reliability, availability, maintainability (continuity of business operations), and system speed as perceived by end-user Hardware and networking required to run HealtheVet, and assure continuity of healthcare operations Robust testing capability Scheduling and Enrollment applications

17. 17 Development Strategy – Cont. HealtheVet Subsequent blocks target implementation of clinical and administrative capabilities Service-Oriented Architecture framework Collaboration with DoD wherever possible and practical VistA Legacy Annual investment that will be prioritized yearly Address critical capabilities and patient safety Issues

18. 18 HealtheVet Timeline

19. 19 FY08 - FY10 Program Priorities

20. 20 HealtheVet Assumptions Baseline scope is correct (as depicted on slide 6) Architectural decisions pertaining to development have been made Acquisition strategy will be developed providing rigor, oversight, and approval authorities Governance processes will be developed Cost-benefit analysis has been conducted Ongoing changes to VistA will be documented in HealtheVet requirements Business rules reverse engineered from VistA will be validated by customer Scope changes required to satisfy cost or schedule constraints will be recognized as work still required

21. 21 HealtheVet Risks Requirements documentation Suppressed over time due to budget or HealtheVet planning factors Integration Governance Resources Funding Staffing Prolonged parallel operations of VistA and HealtheVet Cost to sustain multiple efforts

22. 22 HealtheVet Challenges Oversight of HealtheVet development Maintain customer awareness and involvement Ability to monitor satisfaction of requirements leading to system testing and acceptance Coordinate transition from VistA to HealtheVet Enhancements to old vs. new systems Turn-off plan for VistA Assessment of HealtheVet content to ensure: No harm to current VistA functionality Process reengineering as appropriate Migration to HealtheVet meets customer needs

23. 23 HealtheVet Oversight Oversight is a function of governance, and is responsibility of business owners Enterprise Systems Management (ESM) Office is responsible for gathering business requirements VHA, as the business representative, coordinates with the Office of Information & Technology Office of Enterprise Development (OED) Oversight is collaborative VHA provides requirements OED develops solutions to requirements Monitoring progress a shared responsibility Oversight important to allow ability to forecast satisfaction of requirements, redirect as required

24. 24 HealtheVet Governance Governance, primarily the understanding or roles and responsibilities, works both ways; providing visibility to: Customer requirements development and maturation Developer activities to satisfy requirements Governance processes exist but not yet fully integrated Additional work required to manage the seam between the two – or how VHA and OI&T will act with each other Working to resolve gaps and understand shared responsibilities

25. 25 Validating HealtheVet Content Goal: To ensure all functionality within VistA is migrated to HealtheVet Process: Identify required stakeholders Define scope of effort, establish timeline Map HealtheVet components to business architecture Identify gaps, redundancies in how systems provide support Ensure requirements are complete and up to date

26. 26 Reengineering Functionality Goal: Establish HealtheVet as a world-class health system by ensuring that appropriate process reengineering occurs in HealtheVet planning and development; Process: Assess the degree of application process reengineering needed in requirements development Validate VistA processes and business rules Update business rules to current standards Maintain focus on VA-DoD initiatives that might influence processes and rules Incorporate changes in HealtheVet requirements documents

27. 27 Validating HealtheVet Sequencing Goal: To ensure that HealtheVet is developed in the appropriate sequence to: Provide most needed functionality first Recognize dependencies between systems Support technical ability to develop Common services first since they support all subsequent applications (in progress) Examination of clinical and administrative systems and their inter-dependencies Recommendation for change, if required

28. 28 Summary Familiarization with, and participation in, HealtheVet is crucial because: Leads to better engagement by customer Results in better definition and understanding of requirements Fosters effective collaboration within VA Increases probability of HealtheVet success

29. 29

30. 30 Backup Slides

32. 32 Security June 27, 2007 VA Internal Use Only

33. 33 Messaging/Enterprise Service Bus June 27, 2007 VA Internal Use Only

34. 34 Deployment Toolkit June 27, 2007 VA Internal Use Only

35. 35 Laboratory June 27, 2007 VA Internal Use Only

36. 36 Pharmacy June 27, 2007 VA Internal Use Only

37. 37 Workload Management June 27, 2007 VA Internal Use Only

38. 38 Patient Information Management System (PIMS) June 27, 2007 VA Internal Use Only

39. 39 Person Services June 27, 2007 VA Internal Use Only

40. 40 Scheduling June 27, 2007 VA Internal Use Only

41. 41 Revenue Improvement and System Enhancements (RISE) June 27, 2007 VA Internal Use Only

42. 42 Text Integration Utility (TIU) June 27, 2007 VA Internal Use Only