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
Line 21: Line 21:
 
*OO WG - Composite Order proposed project, led by Austin Kreisler, ArB liaison Patrick Loyd
 
*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/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
 
*caEHR - proposed project from NCI, led by John Koisch
 
*CDA R3 - Structured Documents proposed project, led by Keith Boone.   
 
*CDA R3 - Structured Documents proposed project, led by Keith Boone.   

Revision as of 13:59, 1 December 2009

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

  • (draft) Alpha Project charter template
  • (draft) Alpha Project 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 September 2009 WGM Progress Report

  • PASS Alpha Project - Privacy, Access and Security Services Functional Model, by SOA WG
  • CTS2 Alpha Project - Common Terminology Services Release 2, by Vocab WG
  • ITS - proposed project - 'The ITS Is Might Be Broken', led by Dale Nelson.
  • 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.
  • Infoway Blueprint - led by Ron Parker

General Information

  • Architecture Definition Project Statement
  • Status Report from Marc Koehn 20090126
  • Project Scope Statement for EA IP Phase 1
  • 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

Presentation Materials

Discussion Items

Comments

Please use the discussion tab above.