“Architecture” Webinar 3 in capacity building to support the development and delivery of...

1

“Architecture”Webinar 3 in capacity building to support the

development and delivery of National eHealth Strategies

Peter Drury, PhD.

Capacity building to support eHealth Strategies

. [email protected] .

eHealth CapacityBuilding

Capacity building to support eHealth Strategies 2

Purpose• This webinar is third of an 8-part series commissioned by the

Asia eHealth Information Network and designed to increase awareness of participants on how you can support their ministries achieve their country's national eHealth strategy.

• To help understand how eHealth strategy, planning, an architectural approach, standards and quality, frame the requirements for capacity development and

• To identify how appropriate skills and training from different sources can support the projects and programmes needed to deliver different aspects of eHealth strategies and action plans.

• Part of the AeHIN Academy “eHealth Capacity Building Roadmap”.


Themes

1. Leadership that delivers an eHealth action plan2. Institutional readiness3. Architecting the interoperable enterprise

(scalability)4. Standards and Interoperability5. Health Information Exchange6. Delivery7. Monitoring and Evaluation8. Review, refine, refresh, retrain


Webinar 3: architecting the interoperable enterprise (scalability)

• Architecture as a process, and one that enables the continuum of an enterprise to interoperate.

• Toolkit: – Part 1 Capabilities required to deliver the Vision– Part 2 Generic & specific architectures and solutions

to deliver Action Plan– Part 3 M&E improving EAs

• Different architectural frameworks


Architecture• Enterprise Architecture (EA) is a well- defined practice

for conducting enterprise analysis, design, planning, and implementation, using a holistic approach at all times, for development and execution of strategy.

• EA applies architecture principles and practices to guide organizations through the business, information, process, and technology changes necessary to execute their strategies.

• EA can apply its methods at different organizational levels from departments to complex organisations

Source: A Common Perspective on Enterprise Architecture Developed and Endorsed by The Federation of Enterprise Architecture Professional Organizations

7Capacity building to support eHealth Strategies

Source: A Common Perspective on Enterprise Architecture . The Federation of Enterprise Architecture Professional Organizations. Architecture & Governance vol 9 issue 4 p 11-17

Execute on those plans

Reflect on where you are

at

Determine where you need to go

Create plans to get there

The general process of Enterprise Architecture

8

Domains and Models


Four architecture domains are commonly accepted as subsets of an overall enterprise architecture:• Business• Data• Applications• TechnologyThe individual models produced in the EA process generallyinclude (but are not limited to):• Goals and objectives• Capabilities, values streams, and information (enablers)• Portfolio of business solutions (services and applications)• Technologies and resources (infrastructure)

9

6. Establish the strategic context

Establish the strategic contextProvides the foundation for planning and informed decisions on how to harness ICT for the health system.Outputs• The strategic health goals, challenges and priorities• The potential role for eHealth in addressing them

WHO/ITU National eHealth Strategy Toolkit


10

Understanding the strategic context is critical

• Research population health and demographics• Describe the health system• Review health strategy, goals and priorities• Identify development goals related to health• Review existing strategies for eHealth, ICT or health

information systems• Select goals and challenges where eHealth will have

the most impact• Describe how eHealth will support selected goals



11

6.6 Select goals and challenges where eHealth will have the most impact

Approach• The information collected should be consolidated, to

form a manageable number of goals and challenges. • Between 5-8 strategic goals and challenges are

recommended- more than this increases complexity.• A large number of goals/challenges can be grouped

into themes, and the vision can be drafted to respond to these themes.

• The strategic goals/challenges should be reviewed with stakeholders and refined: consensus is important since the eHealth vision will address these goals.



12

eHealth components: EnablersWHO/ITU National eHealth Strategy Toolkit

Standards and interoperability

Legislation, policy and

complianceWorkforce Adoption

• Data structure • Clinical coding • Data

presentation • Security • Messaging • Software

accreditation

• Privacy regulations

• Consent management policy

• Compliance services

• Electronic record licensing

• Care provider workforce development

• Health IT workforce development

• Professional networks

• Awareness campaigns

• Professional accreditation

• Engagement forums

• Procurement standards

13

eHealth components: Services and ApplicationsWHO/ITU National eHealth Strategy Toolkit

Health information

Electronic health record

Health service delivery

Health care management

• Consumer health knowledge sources

• Care provider knowledge portal

• Distance learning and electronic resources

• Patient demographics

• Allergies• Current

health profile• Medications• Health diary• Test results• Event

summaries• Access

control

• Referrals• Event

summaries• Care plans• Appointments• Alerts • Decision

support• Prescriptions• Lab results• Chronic disease• Telemedicine

and mHealth

• Adverse events

• Risk analysis• Compliance

monitoring• Operations

management• Clinical

practice improvement

• Health care research

13

14

eHealth components: InfrastructureWHO/ITU National eHealth Strategy Toolkit

Examples of common infrastructure components

• Broadband connectivity• Computer systems• Practice, patient and clinical management

systems• Universal health identifier• National authentication service• Provider and service directories• National product catalogue• Prescription transfer service• Health information data sets

This is the foundation for electronic information exchange, comprising physical infrastructure (e.g. networks), core services and applications that underpin a national eHealth environment.

15

5.1 Define main action linesAction Line Example characteristicsFoundations • eHealth components that secure national

information exchange and/or are more cost-effective if done once at a national level.

Solutions • eHealth components that access, interact with and use national foundations and infrastructure to access and share information.

Change and adoption

• Motivate and support the health system, establish incentives, and needed changes in work practices.

Governance • Coordination, visibility, structures, mechanisms for accountability and effective leadership.


16

5.2 Define a process for national monitoring and evaluationDescribes the process for monitoring and evaluation during the implementation of the action plan, including the governance.


17

Q&A AND SHARING SESSION


18

Different EA Methodologies• Business Technology

Management (BTM)• COBIT - Part 1 | Part 2• CORBA• C4ISR Architecture Framework• DODAF• Enterprise Architecture

Planning (EAP)• Federal Enterprise

Architecture: Practical Guide• FEAF• Gartner

• ISO RM-ODP• ISO/IEC TR 14252 (IEEE Std

1003.0)• NCR Enterprise Architecture

Framework• SABSA• SPIRIT Platform Blueprint

Issue 3.0• TEAF • TOGAF• Zachman


http://www.mikethearchitect.com/togaf/#sthash.YZ00kOQJ.dpufhttp://www.opengroup.org/public/arch/p4/others/others.htm

http://www.mikethearchitect.com/togaf/#sthash.YZ00kOQJ.dpuf

http://www.mikethearchitect.com/togaf/#sthash.YZ00kOQJ.dpuf

http://www.opengroup.org/public/arch/p4/others/others.htm

http://www.opengroup.org/public/arch/p4/others/others.htm


19

Comparing EA methodologiesCriteria Meaning

Taxonomy completeness Usefulness in classifying architectural artifacts

Process Completeness Guidance on process for creating an EA

Reference Model Guidance Usefulness in building relevant reference models

Practice Guidance Ease of developing an organisational culture for EA use

Maturity model Effectiveness of maturity assessments of organisations

Business focus Usefulness in driving down expenses or increase income

Governance Guidance Usefulness in creating effective governance models for EA

Partitioning Guidance Effectiveness of autonomous partitioning of enterprise

Prescriptive Catalogue Setting up catalogue of reusable architectural assets

Vendor Neutrality Risk of lock-in to specific consulting organisation

Information Availability Quantity and quality of inexpensive information about it

Time to Value Time before being able to build high value solutionsSource: Comparison of the Top Four Enterprise Architecture Methodologies. Roger Sessions 2007 http://msdn.microsoft.com/en-us/library/bb466232.aspx

The Zachman EA (Taxonomy)

Capacity building to support eHealth Strategies /Source: http://www.sjaaklaan.com/?e=133

When all the cells are filled an overview of the complete enterprise architecture is created. But it is really of use only for architects. Infrastructure architects could use the Zachman framework to create documents to describe the infrastructure, and the relevant fields for infrastructure architecture are grayed in the picture below.

http://www.zachman.com

21

FEAF – The EA for Federal Government (USA)


The FEA is built using common framework of reference models designed to facilitate cross-agency analysis and the identification of gaps, overlaps etc. There are models for:• Performance• Business• Service

component• Data• Technical.

http://www.whitehouse.gov/sites/default/files/omb/assets/fea_docs/FEA_CRM_v23_Final_Oct_2007_Revised.pdf

22

Gartner EA Practice


Gartner's Enterprise Architecture Framework (Formerly Meta) is more appropriately described as a "Practice" that encompasses the Zachman Taxonomy with the TOGAF process and provides it as a service to large Enterprises.

TOGAF 9.1 – The Enterprise Continuum

24

Architecture and Solutions


The Enterprise Continuum provides an overall context for architectures and solutions and classifies assets that apply across the entire scope of the enterprise.

TOGAF assists in generating or maintaining any type of architecture within the Continuum while leveraging assets already defined, internal or external to the organization. http://pubs.opengroup.org/

architecture/togaf9-doc/arch/chap39.html


25

Ratings of 4 EA MethodologiesCriteria Zachman TOGAF FEA Gartner

Taxonomy completeness 4 2 2 1

Process Completeness 1 4 2 3

Reference Model Guidance 1 3 4 1

Practice Guidance 1 2 2 4

Maturity model 1 1 3 2

Business focus 1 2 1 4

Governance Guidance 1 2 3 3

Partitioning Guidance 1 2 4 3

Prescriptive Catalogue 1 2 4 2

Vendor Neutrality 2 4 3 1

Information Availability 2 4 2 1

Time to Value 1 3 1 4

Suggested focus Taxonomy Process Methodology Practice

Key: 1= very poor; 2= inadequate; 3=acceptable; 4=very good

Source: Comparison of the Top Four Enterprise Architecture Methodologies. Roger Sessions 2007 http://msdn.microsoft.com/en-us/library/bb466232.aspx

26

Q&A AND SHARING SESSION


27

Archimate


The ArchiMate® modelling language is an open and independent EA standard supporting the description, analysis and visualisation of architecture within and across business domains. This helps architects to better communicate and collaborate with stakeholders from diverse functional areas. As a result, the alignment of business and IT can be increased. Free ArchiMate ModellingTools are available ttp://www.archimatetool.com/ http://blog.opengroup.org/

2012/08/08/archimate-2-0-ready-for-the-future-of-enterprise-architecture/

http://www.bizzdesign.com/blog/case-experiences-and-best-practices-using-archimate-and-togaf/

http://www3.opengroup.org/subjectareas/enterprise/archimate

http://www3.opengroup.org/subjectareas/enterprise/archimate

http://www.archimatetool.com/

http://www.archimatetool.com/

28

Enterprise Architecture Skills (TOGAF)

Capacity building to support eHealth Strategieshttp://pubs.opengroup.org/architecture/togaf9-doc/arch/

TOGAF provides definitions of the architecting skills and proficiency levels required of personnel, internal or external, to perform architecting roles.

29Capacity building to support eHealth Strategies

The Open Group supports two different routes to certification: The first route is direct certification by The Open Group. The second is indirect, through third-party Accredited Certification Programs (ACPs). http://www.opengroup.org/openca/cert/

Certification Fee: (per Candidate for a 3-year certification period) $1,250http://www.opengroup.org/openca/cert/docs/OpenCA_Fee_Schedule.html

Open Group: Certified training – ArchiMate and Certified Architect

There are two levels of certification:ArchiMate Foundation: Knowledge of the notation, terminology, structure, and concepts of the ArchiMate modeling language. ArchiMate Certified: + the ability to analyze and apply the ArchiMate modeling language.18 Accredited Training Courseshttp://blog.opengroup.org/2014/01/24/the-archimate-certification-for-people-program-2014-updates/

Other sources of training


USA, Canada, UK C$1600 for Framework Foundations http://www.zachmaninternational.com/index.php/zachman-certified/57

Zachman/FEAF /DODAF http://feacvirtualuniversity.org/course/category.php?id=89

FEAC Commercial Black Belt Certified Enterprise Architect $11,000.00 inclusive of classroom training and exams, both written and practicum.

Zachman International and FEAC Institute e-learning portal http://feacvirtualuniversity.org/

Live online Workshops provide the opportunity to become a Certified Enterprise Architect from the comfort of their desktop. The cost of the Workshop for an individual is $3,195.00. Team discounts are available for three or more Workshop attendees. http://www.eacoe.org/distance-learning-faq.php

Institute for Enterprise Architecture Developments – provides an overview of certification initiatives http://www.enterprise-architecture.info/EA_Certification.htm


QUIZTIME!1. Does your national health system use an EA?2. Is EA a project or a process-oriented activity?3. In EA frameworks, are “technologies and resources” usually considered as

enablers, services and applications, or infrastructure?4. How many strategic goals for eHealth are recommended? 1-3; 4-7; 5-8; 6-10?5. Is consumer health knowledge part of an eHealth component?6. Is governance an input to monitoring and evaluation?7. Which of the following EAs offers least vendor neutrality: Zachman, TOGAF, FEA

or Gartner?8. What is the prime focus of the Zachman Framework? Taxonomy; Process;

Methodology; Practice?9. Is Archimate concerned with modelling within domains, between domains, or

both?10. In TOGAF, do Members or sponsors need to have “expert” skills in any aspect if

it?


Trailer for Webinar 4

• Topic: Standards and Interoperability• Date: Monday May 16th

• Time: 15:00 UTC/GMT+8


Final feedback

• Any further questions?• Any suggestions?

“Architecture” Webinar 3 in capacity building to support the development and delivery of...

Documents

Transcript of “Architecture” Webinar 3 in capacity building to support the development and delivery of...