HL7 Enterprise Architecture Implementation Project Getting There!

HL7 Enterprise ArchitectureHL7 Enterprise ArchitectureImplementation ProjectImplementation Project

Getting There!Getting There!

TSC Conference CallFeb 2, 2009

Disclaimer: This overview / summary of the HL7 EA Implementation Project is valid for the date presented. Updated information will be posted periodically to: http://wiki.hl7.org/index.php?title=EA_IP

V1-01 WORKING DRAFTFor initial TSC discussion

Presentation Purpose

• The purpose of this presentation deck is to document the emerging understanding of the HL7 Enterprise Architecture Implementation Project (HL7 EA-IP).

• The process of initially elaborating and eventually executing the project is an ongoing activity involving a variety of engagement processes – many of which remain to be initiated.

January 2009 2HL7 Enterprise Architecture Implementation Project - Initiation / Planning Phase

Strategic Context

• Strategy #1 - Expand, reinvigorate,and streamline HL7’s production processes, technologies and products:

Deliver a first balloted reference architecture document (Roadmap Project #47)

Initiate the adoption of an approved HL7 Reference Architecture (Roadmap Pjt #44)

January 2009 3HL7 Enterprise Architecture Implementation Project - Initiation / Planning Phase

“The HL7 Roadmap document is a business plan for our products and services and was designed specifically to meet the business needs of our members and stakeholders. Derived from collaborative efforts with our members, government and non-government agencies and other standards development organizations, the Roadmap is comprised of five high-level organizational strategies that are supported by a detailed tactical plan with clearly defined objectives, milestones, and metrics for success.”

(See HL7 Roadmap at http://www.hl7.org/documentcomments/index.cfm)

Presentation Outline

• Background Decisions Made Outputs to Date Some challenges in moving forward ...

• “HL7 Enterprise Architecture Implementation Project (HL7 EA IP)”: An overview Overall Goal “Conceptual Project Phases” Key Planning Considerations and Assumptions Notional Deliverables & Milestones by Phase

• Phase 1 – HL7 EA IP Planning / Initiation Phase The Basics: Scope, Deliverables, etc. Proposed “Alpha Project” Approach Next Steps

January 2009 4HL7 Enterprise Architecture Implementation Project - Initiation / Planning Phase

Background

Decisions Made

• Board decision to pursue the development of an HL7 Enterprise Architecture. [NEED DATE]

• Delegation of “technical” architecture development task to Architecture Board through the Technical Steering Committee and the Chief Technical Office (CTO). [October 2007]

• CTO direction to base architecture on SOA principles [May 2008]

• TSC decision to initiate an HL7 Enterprise Architecture Implementation Project – through an initial planning phase. [January 2009 WGM – Orlando]

January 2009 6HL7 Enterprise Architecture Implementation Project - Initiation / Planning Phase

Outputs To Date

• Architecture Development Technical Architecture

• “Service Aware Enterprise Architecture Framework (SAEAF)” Draft Report first published to ArB wiki [September 21, 2008]

• SAEAF presented to WGM [September 2008 WGM – Vancouver] Business Architecture Development

• Developed initial presentations for Orlando WGM to begin framing the implementation project for discussion and refinement purposes [January 2009].

• Stakeholder Engagement Two quarter overview of architecture at the Vancouver WGM

[September 2008]. Two quarter overview of both architecture progress and initial

implementation project details at Orlando WGM [January 2009].

January 2009 7HL7 Enterprise Architecture Implementation Project - Initiation / Planning Phase

Some Challenges in Moving Forward

• The implementation project will likely require funding and therefore project initiation documentation needs to identify resource requirements and support dialog with the HL7 board’s finance committee, potential funders and – potentially – the HL7 board.

• There is a tension between stakeholders who feel that the new architecture should materially impact existing processes and products and those stakeholders who are concerned about the extent of the changes and their impacts.

• HL7 stakeholders – particularly hands-on participants in HL7 specification development work – are eager to understand the impact of the EAS implementation project on their day-to-day work (“process”) and on existing specification artifacts, such as DMIMs, RMIMs, CMETs, etc. (“product”).

January 2009 8HL7 Enterprise Architecture Implementation Project - Initiation / Planning Phase

Some Challenges in Moving Forward

• In addition to the conceptual challenges in devising both the enterprise architecture as well as the paired business architecture, stakeholders are concerned about the decision making processes for the overall journey. Some of the decisions ...

How will the HL7 EAF/S be finalized and to what level of stakeholder / member review will the associated artifacts be subjected?

How will the various implementation project Phases be approved for launch?

How will the various Business Architecture artifacts be reviewed / endorsed?

January 2009 9HL7 Enterprise Architecture Implementation Project - Initiation / Planning Phase

HL7 Enterprise Architecture Implementation Project (HL7 EA IP)

HL7 EA Implementation Project

• Overall HL7 EA IP Goal

Establishment and implementation of a Business Architecture (BA) that enables HL7 to effectively develop and promulgate specification products that are consistent with the (emerging) HL7 Enterprise Architecture Specification (EAS).

• “Conceptual” Project Phases

Phase 0 – Preparation for a Planning / Initiation Phase: Current activities to complete and seek endorsement for Phase 1 framing documentation as well as to launch Phase 1 [Proposed Duration: < 3 weeks]

Phase 1 – HL7 EA IP Planning / Initiation Phase: Activities to conceptualize, plan, resource and initiate the Implementation Phase [Proposed Duration: Ideally < 3 months but certainly prior to May 2009 WGM - Kyoto]

Phase 2 – HL7 EA IP: Implementation (Roll-out) [Duration: TBD through Phase 1 activities]

January 2009 11HL7 Enterprise Architecture Implementation Project - Initiation / Planning Phase

HL7 EA IP – Key Planning Considerations & Assumptions

• The responsibility for developing the Business Architecture (BA) to drive the HL7 EAS implementation rests with the HL7 Technical Steering Committee (TSC).

• The responsibility to develop a full HL7 EAS rests with the HL7 Architecture Board (ArB); the ArB will use the “Service Aware Enterprise Architecture Framework (SAEAF)” Draft Report as a baseline.

• Interdependencies between the development of the BA and the work to develop / refine the EAS will need to be assessed in Phase 1 and applicable processes devised for Phase 2 to ensure, among other things, Conceptual alignment (e.g. Consistent use of concepts / terms, artifacts,

etc.); Appropriate flow of requirements for tooling and processes and other

knowledge from EAS work to BA work.

January 2009 12HL7 Enterprise Architecture Implementation Project - Initiation / Planning Phase

HL7 EA IP – Key Planning Considerations & Assumptions

• BA / EAS development will require collaboration with real integration projects (“Alpha Projects”) that are willing and able to tackle the development of artifacts covering multiple EAS layers / facets: One or more potential Alpha Projects candidates are ready to engage in

short order; The sponsoring agencies are thought to be interested in taking the full range

of artifacts through a balloting process; Selection criteria and engagement principles for Alpha Projects remain to

be devised and agreed.

• The HL EA IP will be accountable as the primary coordination point between “Alpha Projects” and HL7 - primarily addressing issue management.

January 2009 13HL7 Enterprise Architecture Implementation Project - Initiation / Planning Phase

HL7 EA IP – Key Planning Considerations & Assumptions

• Notwithstanding the fact that a planning / initiation phase (1) is required and that it needs to focus on placing Phase 2 on a proper footing, there are near term “balls in motion” that require other engagement during the Phase 1 timeframe (currently seen as February – May). These include: Continued communication activities; Liaison between the implementation project and the ArB to –

among other things – ensure that emerging plans are aligned; Potentially scheduling certain activities – such as Alpha Project

selection criteria and determination of engagement principles – earlier in Phase 1;

January 2009 14HL7 Enterprise Architecture Implementation Project - Initiation / Planning Phase

HL7 EA IP – Key Planning Considerations & Assumptions

• The anticipated significance of “Alpha Projects” in the elaboration of both the enterprise architecture as well as the associated business architecture places several demands on the overall implementation process: Demands an Incremental Process: Our understanding of the overall

implementation requirements will evolve incrementally as the “Alpha Projects” undertake their activities – in other words, we can’t plan out all the details but rather will need to let the process run its course;

Demands Co-ordination and Knowledge Management: It will be critical to establish an effective process to gather learning from “Alpha Projects” and then to institutionalise this learning.

Demands Flexibility & Buy-In During the Journey: The incremental nature of the process will demand flexibility on behalf of HL7 and it’s members and hence stakeholder buy-in is critical.

Demands Transparency in Decision Making: Notwithstanding the iterative, “prototyping” like approach (or perhaps due to it!), decision making processes must be transparent to ensure durable consensus among stakeholders.

January 2009 15HL7 Enterprise Architecture Implementation Project - Initiation / Planning Phase

HL7 EAF

HL7 EA IP – Notional Phase Deliverables (VERY ROUGH)

January 2009 HL7 Enterprise Architecture Implementation Project - Initiation / Planning Phase 16

SAEAFPhase 1 Launch

Materials

HL7 EAS

ArB Work HL7 EA IP Work

Phase 0

Phase 1

Phase 2

Alpha ProjectAlpha

ProjectAlpha Project(s)

Phase 2 Launch

Materials

Business Architecture

•GOM changes•Process changes•Tooling changes•Etc.

Alpha Project

Selection & Coord

Funding & Approval for

Phase 2

Communication

Collateral

Etc.Etc.

Initial “Momentum Mtce” work and deliverables

Alpha Project Outputs

Phase 1 – HL7 EA IP Planning / Initiation Phase

(EARLY DRAFT)

Phase 1 – The Basics

• Phase 1 Goal

Activities to conceptualize, plan, resource and initiate the Implementation Phase

• Phase 1 Scope

All work needed to successfully launch the implementation Phase (2) of the HL7 EAP Implementation project.

Any activities to maintain momentum by engaging in planned communication and coordination activities (i.e. beginning to work the emerging implementation plan as needed).

January 2009 18HL7 Enterprise Architecture Implementation Project - Initiation / Planning Phase

Internal Stakeholders

Project Team

Phase 1 – The Basics

• Phase 1 Organization

January 2009 19HL7 Enterprise Architecture Implementation Project - Initiation / Planning Phase

A rB

H L 7 S u pp o rt

O th e r T e am M e m be rs (T B D )

P ro jec t M a n a ge r / T e am L ea d er

T S C Consu

lt

Thought Leader Advisory Group

Collaborate

Phase 1 – The Basics

• Phase 1 Deliverables Baseline “framing” artifacts for Phase 2

• General project plan, risks, budget, etc.• Implementation project organization and decision making framework –

Clearly outlining how various types of decisions are expected to be made in completing both the Enterprise Architecture and the Business Architecture!

Stakeholder Engagement Strategy • HL7 Member Engagement• “Alpha Project” Engagement (e.g. Selection criteria; engagement principles &

expectations; etc.) Change Management Plan Framework (to be elaborated in Phase 2)

• Education Plan• Process / Policy change• Tooling / Publishing requirements• Etc.

Approval of Phase 2 through the TSC during Kyoto WGM or prior.

January 2009 20HL7 Enterprise Architecture Implementation Project - Initiation / Planning Phase

Phase 1 – The Basics

• Phase 1 Dependencies Detailed timelines for HL7 EA development ... Etc. (MORE TO BE ADDED BASED ON TSC INPUT)

• Phase 1 Key Success Factors Appropriate resourcing for coordination AND delivery to

maintain momentum and meet timelines need to be in place. A sufficient number of suitable Alpha Projects must be

identified to exercise the various aspects of the architecture framework.

(MORE TO BE ADDED BASED ON TSC INPUT)

January 2009 21HL7 Enterprise Architecture Implementation Project - Initiation / Planning Phase

Phase 1 – The Basics

• Phase 1 Milestones Project team and Thought Leader Advisory group in place by

February 28, 2009 Alpha Project parameters identified by March 31, 2009 Kyoto Meeting Approach Co-ordinated and materials complete

by March 31, 2009 Decision making framework Phase 2 framing draft Deliverables developed by April 30,

2009 (MORE TO BE ADDED BASED ON TSC INPUT)

January 2009 22HL7 Enterprise Architecture Implementation Project - Initiation / Planning Phase

Phase 1 – Proposed “Alpha Project Approach”

• Initiate “Candidate” Alpha Project level setting meeting / telecon Seeking brief project overviews and alpha project stakeholder expectations

• Develop “Alpha Project” selection criteria In collaboration with ARB, Implementation project “Thought Leader

Group” and HL7 PMO devise selection criteria and engagement principles. Devise qualification process

• Call for “Alpha Project” Participation Issue call for participation outlining clear expectations and seeking

applicable data to enable selection

• “Alpha Project” Selection In collaboration with ARB and Implementation project “Thought Leader

Group” recommend selection. Confirm selection through TSC.

• Formally initiate “Alpha Project” Engagement (Phase 2!)

January 2009 23HL7 Enterprise Architecture Implementation Project - Initiation / Planning Phase

Some Next Steps (As at January 27, 2009)

• Seek endorsement of Phase 1 at February 1, TSC call

• Formally establish “Project Team” ... Confirming who will hold the lead pen on various deliverables!

• Initiate TSC dialog pertaining to key decisions and decision making practices

• Convene “Thought Leader Advisory Group” call and initiate bi-weekly calls to begin to work the key streams: Stakeholder Engagement plan and action – HL7 Members Stakeholder Engagement plan and action – Alpha Projects Develop Change Management Plan Framework

• Kick-start “Alpha Project” dialog with candidate projects

January 2009 24HL7 Enterprise Architecture Implementation Project - Initiation / Planning Phase

More Information

January 2009 HL7 Enterprise Architecture Implementation Project - Initiation / Planning Phase 25

[email protected] Point Informatics Ltd.Interim Project Lead

HL EA IP Wiki:http://wiki.hl7.org/index.php?title=EA_IP