This wiki has undergone a migration to Confluence found Here

HL7 Business Architecture

From HL7Wiki
Jump to navigation Jump to search

This page is the starting place for the HL7 Business Architecture Project.

Tasks

Gforge tasks

Project Scope Statement

  1. The purpose of this project is to produce a working draft, i.e. a document and associated set of diagrams that collectively describe a "goal state" business architecture model (BAM) for HL7. A goal state architecture is a high-level description of an ideal architecture based on best practices, principles, objectives and other conceptual architecture constructs. A goal state architecture provides the “goal posts” that time-specific target states (or transition states) aim to achieve or demonstrate traceability to. The term "business architecture model" includes the identification of the key concepts, relationships, and processes that collectively define the "business organization" that is HL7. The BAM will leverage industry standard business models and meta-models, including the business layer of the OpenGroup Archimate specification (http://www.opengroup.org/archimate/doc/ts_archimate/) and OMG’s Business Motivation Model (http://www.omg.org/spec/BMM/1.1/), to identify core constructs including, but not limited to:
    1. Constraints and Motivations (e.g. requirements, drivers, policies, goals and objectives, strategic initiatives, etc.) that shape HL7's business operations and internal/external relationships
    2. Actors and Roles (e.g., TSC, ArB, Steering Divisions, Work Groups, members, and consumers of HL7 specifications) . Note: the BAM will not extend “above” the TSC, (i.e., the BAM will not address relationships, roles, etc. of the Executive Committee, the HL7 Board of Directors, etc.).
    3. Processes (including business use cases). The BAM will use the HL7 GOM as a source of input for understanding existing processes, policies, constraints, internal and external obligations, etc. Note: an important output from process documentation and analysis will be the identification of context-neutral "capabilities" that can serve as the reusable building blocks for re-engineered "to be" processes
    4. Products, i.e. deliverables produced by Capabilities and context-specific processes
    5. Collaborations and interactions between Actors, Roles, Products and Processes or other static constructs produced by the business (e.g. Specifications)
  2. Where appropriate, the BAM will highlight and leverage current-state business architecture constructs that “have stood the test of time” and demonstrate the desirable goal-state characteristics. To do this, the project scope will also include an informal review and assessment of current state motivations, constraints, roles, actors, processes, products and collaborations.
  3. The BAM will use the following as core organizing principles to guide the overall structure:
    1. Organization around Product Lines, e.g. FHIR, V3, V2, CDA, etc.
    2. Separation of governance, management, and methodology activities, responsibilities, and deliverables.
  4. The BAM will focus on incorporating constructs from the SAIF CD Governance Framework as they apply to the HL7 BAM with the goal that HL7 is moving in the direction of having a Business Architecture which is “SAIF CD compliant.”

Statement of work

Deliverables

  1. BAM lite- describing the product/family model.
  2. BAM - model the full process.