Enterprise Architecture

1. Enterprise Architecture Tony McAllister 11. 12. 2013

2. AGENDA • Introduction • Enterprise Architecture • Health IT & EA • Why Should I, a Healthcare Business Bigshot, Care About IT Architecture? • Q & A

3. Objectives / Themes • Gain Understanding of Enterprise Architecture (and it Goals / Methods) • Information (and its Management) • Business Architecture as a Link to IT • Sample the Architecture of some Healthcare companies • Why Should I Care about IT Architecture?

4. Introduction

5. My Background • Education • B.S. Computer Science : Rose-Hulman Institute of Technology • MBA, Finance & Entrepreneurship : Indiana University • Professional Experience • Cummins Inc • Level 3 Communications • Target • Be The Match

9. Enterprise Architecture

10. What is Enterprise Architecture? • Some Definitions…. • ANSI/IEEE – Definition of “IT Architecture”…. • “The fundamental organization of a system, embodied in its components, their relationships to each other and the environment, and the principles governing its design and evolution.” • Gartner– Definition of “Enterprise Architecture”….. • “A discipline for proactively and holistically leading enterprise responses to disruptive forces by identifying and analyzing the execution of change toward desired business vision and outcomes. EA delivers value by presenting business and IT leaders with signature-ready recommendations for adjusting policies and projects to achieve target business outcomes that capitalize on relevant business disruptions. EA is used to steer decision making toward the evolution of the future state architecture.”

11. Enterprise Architecture Structure & Story

13. Basic IT Architecture Example User (Represents the Business) Application Technology / Infrastructure Data

14. An Example - IT Enterprise Architecture

15. The Case for Enterprise Architecture Every organization has an architecture whether it likes it or not…. Some just happen Some are planned

16. The Case for Enterprise Architecture Advantages of a good EA: • A more efficient IT operation: • Lower software development, support, and maintenance costs • Increased portability of applications • Improved interoperability and easier system and network management • Improved ability to address critical enterprise-wide issues like security • Easier upgrade and exchange of system components • Better return on existing investment, reduced risk for future investment: • Reduced complexity in IT infrastructure • Maximum return on investment in existing IT infrastructure • The flexibility to make, buy, or out-source IT solutions • Reduced risk overall in new investment, and the costs of IT ownership • Faster, simpler, and cheaper procurement: • Buying decisions are simpler, because the information governing procurement is readily available in a coherent plan. • The procurement process is faster - maximizing procurement speed and flexibility without sacrificing architectural coherence.

17. EA Framework & Process

18. EA Framework

19. Information Architecture Focus Areas • Information framework • Data modeling • Data naming conventions • Data governance • Business intelligence • Document management & collaboration • Master data management

20. Business Architecture Focus Areas • Corporate business objectives • Business strategies • Business capabilities • Reporting & analytics • Data mapping & validation

21. Technology & Infrastructure Architecture Focus Areas • Technical architectural framework • Network landscape • Capacity management • Technical ROI • Security architecture • Technology governance

22. Solution Architecture Focus Areas • Application portfolio • Integration architecture • Minimal application redundancy • Solution architecture

23. EA Process Business Architecture Architecture Vision EA Governance Enterprise Architecture Repository Strategic Roadmap Current State Future State

24. Business Architecture

25. What is Business Architecture? Source: Business Architecture Guild

26. Use of Business Architecture to Link Business Strategy to IT From Strategy to Execution….

27. Business Process Models

28. Information Architecture

29. What is Information Architecture? Source: Data Management Association

30. Key Themes of Data Management • Data Stewardship – Business Partnership • Data Quality • Data Integration • Enterprise Perspective • Cultural Change Leadership • “Enterprise Information Management”

31. Information Conceptual & Physical Models Conceptual Data Model

32. Information Conceptual & Physical Models Logical Data Model

33. Information Conceptual & Physical Models Physical Data Model

34. Tools for Telling the Story

35. Architecture Program Roadmap Roadmapping & Planning Architecture Vision Architecture Outcomes Roadmap Outcomes are organized into a program view of the roadmap Which provides scope and context for developing detailed project plans. Portfolio Strategies EA Governance Detailed Project Plans Business Plans & Priorities

36. Roadmapping & Planning

37. Healthcare IT Architecture Examples

38. Be The Match Architecture

39. Hospital Digital Platform

40. Healthcare.gov Logical Architecture

41. Why Should I Care About IT Architecture?

42. The Case for Enterprise Architecture • Technology is, and will become even more so, pervasive in the business of healthcare • Technology will become more integrated into business operations and planning • Business leaders will need to understand how to leverage existing investments in technology and how to develop new uses of technology • As the use of technology expands, effective management and coordination will be critical • Big Data will provide many benefits and will require strong information management • Pay for value, no longer pay for fee for service

43. The Case for Enterprise Architecture Advantages of a good EA: • A more efficient IT operation: • Lower software development, support, and maintenance costs • Increased portability of applications • Improved interoperability and easier system and network management • Improved ability to address critical enterprise-wide issues like security • Easier upgrade and exchange of system components • Better return on existing investment, reduced risk for future investment: • Reduced complexity in IT infrastructure • Maximum return on investment in existing IT infrastructure • The flexibility to make, buy, or out-source IT solutions • Reduced risk overall in new investment, and the costs of IT ownership • Faster, simpler, and cheaper procurement: • Buying decisions are simpler, because the information governing procurement is readily available in a coherent plan. • The procurement process is faster - maximizing procurement speed and flexibility without sacrificing architectural coherence.

44. Q & A