This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Difference between revisions of "EA IP"

From HL7Wiki
Jump to navigation Jump to search
 
(18 intermediate revisions by the same user not shown)
Line 1: Line 1:
__TOC__
+
__NOTOC__
 +
See [[SAIF Architecture Program]] wiki
 +
 
 +
 
 +
*back to [[Technical Steering Committee]]  .  .  .  [[Architecture Board]]  .  .  .  [[SAIF_main_page]] <br/><br/>
 +
 
 +
Orignal EA IP wiki page content has been moved to [[EA_IP_Phase1_%28alpha_project_approach%29]]
 +
 
 +
 
 +
This Wiki page is for the current incarnation of the HL7 Enterprise Architecture Implementation <s> Project </s> '''Program''' (EA IP).  The HL7 Enterprise Architecture is based on the Services-Aware Interoperability Framework developed by the Architecture Review Board (ArB).
 +
The [[Architecture Board]] is a Technical Steering Committee (TSC)-appointed committee to define an architecture for the work of the HL7 body.  The TSC is responsible for the rollout of that architecture.  This site is intended to both provide and elicit communication on, for and about the Implementation Program.
 +
 
 +
See [[SAEAF_201001_Document|SAIF document location]]
  
*back to [[Technical Steering Committee]]
 
=Enterprise Architecture Implementation Project (EA IP)=
 
  
This Wiki page was created for the HL7 Enterprise Architecture Implementation Project (EA IP).
 
The [[Architecture Board]] is a TSC-appointed committee to define an architecture for the work of the HL7 body.  The TSC is responsible for the rollout of that architecture.  This site is intended to both provide and elicit communication on, for and about the Implementation Project.
 
 
==Implementation Plans==
 
==Implementation Plans==
 +
Initial implementation approaches were to allow self-identifying 'alpha' projects to make use of the SAIF framework and identify what architectural components would develop.  This approach worked well for some (PASS) but not for others, and the need for a more focused effort was recognized.  See [[EA_IP_Phase1_%28alpha_project_approach%29]] for more information.
 +
 +
 +
 +
The new program was discussed at length at the 2010October Working Group Meeting.  For those discussions captured in meeting minutes, see
 +
*[http://hl7t3f.org/wiki/index.php?title=2010-10-03_TSC_WGM_Agenda TSC Sunday night meeting]
 +
*[[20101006_arb_minutes_jointw_with_O%26O_and_MnM_on_EA_IP_Transition]]
 +
 +
The premise remains that there are certain problems the Enterprise Architecture was intended to address:
 +
*Functional models and technical models and the relationship between them
 +
*Consistency across our paradigms
 +
* Behaviour in dynamic model
 +
* Reusable functional components
 +
 +
Remaining to be addressed are definitions of success criteria by which progress will be measured.
 +
 +
 +
The proposed new approach for the EA Implementation [[Program Management|Program]] is a shift of EA-IP to a “program management” model that is intended to monitor and report rather than “manage” the implementation and its related activities.  The EA IP would provide oversight, and make visible to the organization the plans, interdependencies, the critical path, and progress.
 +
 +
The projects operating within the Program include a Reference Implementation Project and foundational Work Groups will develop and define infrastructure to support that project.  The Composite Orders project by Orders and Observations has been named the reference implementation project.
 +
*OO WG - Composite Order project, ([http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?action=edit&ProjectNumber=38 Project Insight # 38]) led by Austin Kreisler, ArB liaison Patrick Loyd
 +
*[http://gforge.hl7.org/gf/download/docmanfileversion/5424/6837/HL7AlphaProjectCharter-OO-CompositeOrderSEP09.doc Draft Charter]
 +
*See [[SAIF Alpha OO]] wiki page
 +
*Anticipated participation by WG developing infrastructure: initial list of activities discussed if identified
 +
**ArB: responsible for providing SAIF reference materials
 +
**ITS
 +
**Implementation and Conformance
 +
**Infrastructure and Messaging: determines how to move / adapt wrappers to the service-contract description
 +
**Modeling and Methodology: address the modeling formalisms and the impact of the SAIF on HDF methodology
 +
***2011Jan WGM with ArB reviewed draft 'artifact definition' to determine type of content of such definition - see [[:category:SAIF Artifact Definition]]; working with SOA, Structured Docs, EHR as well as ArB to formally define all artifact types in forthcoming SAIF-based methodology. (from HL7 MnM Roundtable.ppt by Lloyd McKenzie 1/13/2011 4:05 AM to MnM list)
 +
**Project Services: determines how the methodology and deliverables are integrated into the balloting life cycle
 +
**Publishing
 +
**SOA: define the service contract paradigm, as well as perhaps a guide for application of SOA
 +
**Tooling
 +
*TSC will assert and resolve governance on an ongoing basis.
 +
**emerging Governance Framework based on concepts outlined by Thomas Erl discussed at WGM and distributed PPT to SOA listserv 1/13 2:41 am by Galen Mulrooney.
 +
 +
  
* (draft) Alpha Project [http://gforge.hl7.org/gf/download/trackeritem/747/1038/HL7AlphaProjectCharter-TEMPLATE.doc charter template]
 
* (draft) Alpha Project [http://gforge.hl7.org/gf/download/trackeritem/747/1039/HL7EA-IP-AlphaProjectConsiderationsDRAFT-V2.doc considerations]
 
**The goal is to use these charters to validate our overall Alpha strategy by, among other things, confirming the level of coverage over the thing-formerly-known-as-SAEAF that we can achieve through our collaboration. Receipt of the charter would be the trigger to formalize Alpha status through the TSC and to coordinate various kick-off calls with the ArB.
 
===Alpha Project progress===
 
See update from [[2009-09-23_EA_IP_TSC_WGM_Minutes|September 2009 WGM Progress Report]]
 
*[[EA_Alpha_PASS|PASS Alpha Project]] - Privacy, Access and Security Services Functional Model, by SOA WG
 
*[[EA_Alpha_CTS2|CTS2 Alpha Project]] - Common Terminology Services Release 2, by Vocab WG
 
*[[EA_Alpha_Blueprint|Infoway Blueprint Alpha Project]] Infoway Blueprint - led by Ron Parker
 
*ITS - proposed project - 'The ITS <s>Is</s> Might Be Broken', led by Dale Nelson.
 
**Project Insight # 544 [http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?action=edit&ProjectNumber=544 summary]
 
*EHR WG - Electronic Health Record System Functional Model Release 2 (EHR-S FM R2),
 
**Led by Pat Van Dyke (Delta Dental Plans Association), ArB liaison John Koisch
 
*OO WG - Composite Order proposed project, led by Austin Kreisler, ArB liaison Patrick Loyd
 
*:Update: 11/19/2009 - Project is on hold awaiting resource availability. Currently there is no approved project scope statement. Developing and approving a project scope statement are the next steps when resources are available to work on this project.
 
*:Update 11/30/2009 - Charters... not started, Patrick and John Koisch will work on this. A number of working documents in progress for artifacts.  Noted barriers to success: Time, scope of problem, scope of project, and expectations. John notes the working documents will show lessons learned.  No dependencies on other projects noted.
 
*caEHR - proposed project from NCI, led by John Koisch
 
*CDA R3 - Structured Documents proposed project, led by Keith Boone. 
 
**Project Insight #477 [http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?action=edit&ProjectNumber=477 summary]
 
  
 +
===Overview===
 +
 +
A new scope statement will be drafted.  See [[SAIF Architecture Program]] wiki
 +
 +
===Next Steps===
 +
*Need to refine the problem statements and provide success criteria to know if we are making progress and how we will know we are done.
 +
*Close the effort with existing Alphas with a structured interview process with each alpha that harvests the learnings:
 +
*#Marc and Ron develop [http://gforge.hl7.org/gf/download/docmanfileversion/5915/7650/AlphaClosureInterview_b.doc interview questions],
 +
*#Lynn conduct interviews,
 +
*#Marc consolidate responses into [http://gforge.hl7.org/gf/download/docmanfileversion/6244/8269/EA-IPClosureReport.docx closing report] to be posted on the Wiki.
 +
*Draft requirements and expectations
 +
**Mission of transparency, surfacing artifacts, supporting projects, calling upon actors to provide support
 +
*#What are the expectations of Composite Order project
 +
*#What are the expectations of the Foundations work groups and their engagement in the Composite Order activity
 +
*#What are the expectations by Composite Order of other groups working on SAIF implementation activity (e.g. Project Services' SAIF and Sound)
 +
*#What resources are needed to manage such a program with an enterprise view?
 +
*Track risks and mitigations identified at [[20101006_arb_minutes_jointw_with_O%26O_and_MnM_on_EA_IP_Transition]]
  
 
==General Information==
 
==General Information==
 
* [[EA IP Meeting Agenda and Minutes]]
 
* [[EA IP Meeting Agenda and Minutes]]
 +
*[http://gforge.hl7.org/gf/download/docmanfileversion/6244/8269/EA-IPClosureReport.docx EA IP Alpha Closure Summary]
 +
 +
==Links==
 +
*NCI's CBIIT SAIF implementation wiki at https://wiki.nci.nih.gov/display/SAIF/CBIIT+SAIF+Wiki
 +
**https://wiki.nci.nih.gov/display/SAIF/CBIIT+SAIF+FAQs - CBIIT SAIF FAQs
 +
*http://gforge.hl7.org/gf/project/saeaf/ (ArB SAIF GForge Repository)
 +
*http://gforge.hl7.org/gf/project/tsc/docman/?subdir=240 (TSC “Architecture” documents GForge directory)
 +
* http://gforge.hl7.org/gf/project/hdf/frs/ (HDF)
 +
  
* [http://healthlevelseven.projectinsight.net/Content/Files/Download.aspx?2009JAN_PROJSCOPE_ArB_Charlie_Mead_Enterprise_Architecutre_Spec.doc Architecture Definition Project Statement]
 
* [http://gforge.hl7.org/gf/download/docmanfileversion/873/1949/Koehn_status_20090126.pdf Status Report] from Marc Koehn 20090126
 
* [http://gforge.hl7.org/gf/download/trackeritem/747/955/HL7EA-IPPSSv2009.1.doc Project Scope Statement] for EA IP Phase 1
 
* [http://gforge.hl7.org/gf/download/docmanfileversion/4091/5183/20090720TSC_EAIP_Rpt4.pdf Status Report] from marc Koehn 20090720
 
* Proposed next steps (5 Oct 2009)
 
**Value proposition
 
***start work on the SAEAF value proposition
 
**Alpha support
 
***Build Knowledge harvesting plan
 
***Confirm project liaison list
 
***Document approval process for other projects
 
***Consider establishing some sort of “issue” management process ... or leveraging a PMO or other process to ensure that we can capture and resolve issues
 
***more?
 
**Communication
 
***Consider building a "SAEAF" focused WIKI page for context and links ... i.e. setting up a key page that can be linked to from EA-IP, from the main site, from the ArB, etc. but that is geared around non-techy intro materials
 
*** SAEAF Alpha status page – this should be part of the above to provide a list of the projects, access to charters, current status, etc.
 
**Training
 
***Future Training Plan
 
*SAEAF 'book' [http://gforge.hl7.org/gf/download/docmanfileversion/5404/6794/SAEAFprojecttimeline.pdf project timeline] as of 28 Dec 2009
 
  
==Presentation Materials==
 
* [http://gforge.hl7.org/gf/download/trackeritem/747/942/HL7_SAEAF_impacts_20090110.ppt Draft Impact Statements] Presented at Jan2009 WGM
 
*[http://gforge.hl7.org/gf/download/docmanfileversion/767/1842/HL7-EA-IP-Phase1-WedQ3Overview.ppt Jan2009 WGM Wednesday Q3 Overview]
 
*[http://gforge.hl7.org/gf/download/trackeritem/747/954/HL7-EA-IP-Phase1-GettingThere_V20090202.ppt Draft slide deck] for 20090202 TSC Conference Call discussion
 
*[http://gforge.hl7.org/gf/project/saeaf/scmsvn/?action=browse&path=%2Ftrunk%2Fdocs%2Fpresentations%2F SAEAF Slide decks] released 2009-03-02
 
* 2009MayWGM Wednesday [http://gforge.hl7.org/gf/download/trackeritem/747/1036/HL7-EA-IP-Phase1-MovingCloserV1-03.ppt Q3 Slide Deck]
 
*2009MayWGM [http://gforge.hl7.org/gf/project/saeaf/scmsvn/?action=browse&path=%2Ftrunk%2Fdocs%2Fpresentations%2FECCFApril09-v5.ppt&view=log ECCF Slide deck]
 
*2009-07-15 SAEAF Specification Stack Webinar [http://gforge.hl7.org/gf/download/docmanfileversion/3992/5083/HL7SAEAF_SpecificationStack-July09.ppt slides]
 
*2009SeptWGM Wednesday Q4 [http://gforge.hl7.org/gf/download/docmanfileversion/5336/6631/HL7-EA-IP-Atlanta2009-WedQ4Ver1.ppt Slides]
 
  
==Discussion Items==
 
*[http://gforge.hl7.org/gf/download/docmanfileversion/750/1825/HL7RASCIv1.1.xls RASCI Responsibility Matrix] draft per [http://gforge.hl7.org/gf/download/docmanfileversion/801/1876/KenRubinemail.pdf Ken Rubin]
 
*[http://gforge.hl7.org/gf/download/docmanfileversion/816/1891/HL7RASCIv2.1-postARBdiscussion.xls RASCI Responsibility Matrix v2.1] revision from Jan2009WGM - 20090115 ArB discussion
 
* draft [http://gforge.hl7.org/gf/download/trackeritem/747/1046/HL7EA-IP-InternalEngagementPlanDraft-Outline.doc Internal Engagement Plan]
 
  
 
==Comments==
 
==Comments==
 
Please use the [http://wiki.hl7.org/index.php?title=Talk:EA_IP discussion tab] above.
 
Please use the [http://wiki.hl7.org/index.php?title=Talk:EA_IP discussion tab] above.

Latest revision as of 21:19, 28 April 2011

See SAIF Architecture Program wiki


Orignal EA IP wiki page content has been moved to EA_IP_Phase1_(alpha_project_approach)


This Wiki page is for the current incarnation of the HL7 Enterprise Architecture Implementation Project Program (EA IP). The HL7 Enterprise Architecture is based on the Services-Aware Interoperability Framework developed by the Architecture Review Board (ArB). The Architecture Board is a Technical Steering Committee (TSC)-appointed committee to define an architecture for the work of the HL7 body. The TSC is responsible for the rollout of that architecture. This site is intended to both provide and elicit communication on, for and about the Implementation Program.

See SAIF document location


Implementation Plans

Initial implementation approaches were to allow self-identifying 'alpha' projects to make use of the SAIF framework and identify what architectural components would develop. This approach worked well for some (PASS) but not for others, and the need for a more focused effort was recognized. See EA_IP_Phase1_(alpha_project_approach) for more information.


The new program was discussed at length at the 2010October Working Group Meeting. For those discussions captured in meeting minutes, see

The premise remains that there are certain problems the Enterprise Architecture was intended to address:

  • Functional models and technical models and the relationship between them
  • Consistency across our paradigms
  • Behaviour in dynamic model
  • Reusable functional components

Remaining to be addressed are definitions of success criteria by which progress will be measured.


The proposed new approach for the EA Implementation Program is a shift of EA-IP to a “program management” model that is intended to monitor and report rather than “manage” the implementation and its related activities. The EA IP would provide oversight, and make visible to the organization the plans, interdependencies, the critical path, and progress.

The projects operating within the Program include a Reference Implementation Project and foundational Work Groups will develop and define infrastructure to support that project. The Composite Orders project by Orders and Observations has been named the reference implementation project.

  • OO WG - Composite Order project, (Project Insight # 38) led by Austin Kreisler, ArB liaison Patrick Loyd
  • Draft Charter
  • See SAIF Alpha OO wiki page
  • Anticipated participation by WG developing infrastructure: initial list of activities discussed if identified
    • ArB: responsible for providing SAIF reference materials
    • ITS
    • Implementation and Conformance
    • Infrastructure and Messaging: determines how to move / adapt wrappers to the service-contract description
    • Modeling and Methodology: address the modeling formalisms and the impact of the SAIF on HDF methodology
      • 2011Jan WGM with ArB reviewed draft 'artifact definition' to determine type of content of such definition - see category:SAIF Artifact Definition; working with SOA, Structured Docs, EHR as well as ArB to formally define all artifact types in forthcoming SAIF-based methodology. (from HL7 MnM Roundtable.ppt by Lloyd McKenzie 1/13/2011 4:05 AM to MnM list)
    • Project Services: determines how the methodology and deliverables are integrated into the balloting life cycle
    • Publishing
    • SOA: define the service contract paradigm, as well as perhaps a guide for application of SOA
    • Tooling
  • TSC will assert and resolve governance on an ongoing basis.
    • emerging Governance Framework based on concepts outlined by Thomas Erl discussed at WGM and distributed PPT to SOA listserv 1/13 2:41 am by Galen Mulrooney.



Overview

A new scope statement will be drafted. See SAIF Architecture Program wiki

Next Steps

  • Need to refine the problem statements and provide success criteria to know if we are making progress and how we will know we are done.
  • Close the effort with existing Alphas with a structured interview process with each alpha that harvests the learnings:
    1. Marc and Ron develop interview questions,
    2. Lynn conduct interviews,
    3. Marc consolidate responses into closing report to be posted on the Wiki.
  • Draft requirements and expectations
    • Mission of transparency, surfacing artifacts, supporting projects, calling upon actors to provide support
    1. What are the expectations of Composite Order project
    2. What are the expectations of the Foundations work groups and their engagement in the Composite Order activity
    3. What are the expectations by Composite Order of other groups working on SAIF implementation activity (e.g. Project Services' SAIF and Sound)
    4. What resources are needed to manage such a program with an enterprise view?
  • Track risks and mitigations identified at 20101006_arb_minutes_jointw_with_O&O_and_MnM_on_EA_IP_Transition

General Information

Links



Comments

Please use the discussion tab above.