EA IP

See SAIF Architecture Program wiki

• back to Technical Steering Committee . . . Architecture Board . . . SAIF_main_page
  
  

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

• TSC Sunday night meeting
• 20101006_arb_minutes_jointw_with_O&O_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 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

• EA IP Meeting Agenda and Minutes
• 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)

Comments

Please use the discussion tab above.