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

Difference between revisions of "Product SAEAF"

From HL7Wiki
Jump to navigation Jump to search
Line 1: Line 1:
−
==Product Brief - Enterprise Architecture Specification==
+
=Product Brief - Enterprise Architecture Specification==
 +
__TOC___
  
 
:back to [[Main_Page]]
 
:back to [[Main_Page]]
 
:back to [[Product_List|Product List]]
 
:back to [[Product_List|Product List]]
 
===Product Name===
 
===Product Name===
−
Services-Aware Enterprise Architecture Specification (SAEAF)
+
HL7 Services-Aware Enterprise Architecture Specification (SAEAF)
  
 
===Topics===
 
===Topics===
Line 19: Line 20:
  
 
===Summary===
 
===Summary===
−
The HL7 SOA-Aware Enterprise Architecture provides HL7 with an Enterprise Architecture Framework, i.e. a set of constructs, Best Practices, processes, etc. that enable HL7 specifications to achieve cross-specification consistency and coherancy irrespective of the chosen interoperability paradigm (messages, documents, or services). SAEAF consists of four core "frameworks": Information (including RIM, data types, vocabulary bindings, etc.), Behavior (subsuming the existing Dynamic Model), Enterprise Conformance and Compliance (including HL7's existing Implementation and Conformance standards), and Governance.
+
SAEAF (The HL7 SOA-Aware Enterprise Architecture Framework) provides HL7 with an Enterprise Architecture Framework, i.e. a set of constructs, Best Practices, processes, etc. that enable HL7 specifications to achieve cross-specification consistency and coherancy irrespective of the chosen interoperability paradigm (messages, documents, or services). SAEAF consists of four core "frameworks": <br/>
−
The SAEAF  provides a framework for specification of standardized services that can be used by the HL7 community. It identifies artifacts and a constraint pattern that provides traceability from requirements. These specifications align with different levels of conformance that aid HL7 consumers in adopting standards in different contexts, and supports specific integration patterns between collaborators as they seek to achieve computable semantic interoperability.  
+
(1) Information (including RIM, data types, vocabulary bindings, etc.),  
 +
<br/>(2) Behavior (subsuming the existing Dynamic Model),  
 +
<br/>(3) Enterprise Conformance and Compliance (including HL7's existing Implementation and Conformance standards), and  
 +
<br/>(4) Governance.  
  
 
===Description===
 
===Description===
Line 30: Line 34:
  
 
===Benefits===
 
===Benefits===
−
*The main benefits that will be derived from developing specifications using the SAEAF including:  consistency of specifications, enhanced ability to manage loosely-coupled complex interactions between multiple trading parters, increased cross-organization reuse of architecture primitives (realizing the value proposition of CMETs and extending that proposition to include behavioral as well as static semantic constructs).
+
The main benefits that will be derived from developing specifications using the SAEAF include:  consistency of specifications, enhanced ability to manage loosely-coupled complex interactions between multiple trading partners, increased cross-organization reuse of architecture primitives (realizing the value proposition of CMETs and extending that proposition to include behavioral as well as static semantic constructs)
  
 
===Implementations/ Case Studies (Actual Users)===
 
===Implementations/ Case Studies (Actual Users)===
Line 51: Line 55:
 
====Presentations====
 
====Presentations====
 
*[http://wiki.hl7.org/index.php?title=Architecture_Board ArB wiki]
 
*[http://wiki.hl7.org/index.php?title=Architecture_Board ArB wiki]
 +
*SAEAF document locations currently on GForge http://gforge.hl7.org/gf/project/saeaf/scmsvn/?action=browse&path=%2Ftrunk%2Fdocs%2Fpresentations%2F
 +
*Tutorials offered at WGM on Services and Service-Awareness in HL7, and The SAEAF Behavior Framework
 +
*See more at http://www.hl7.org/implement/training.cfm
 
====Relationship to/ Dependencies on, other standards====
 
====Relationship to/ Dependencies on, other standards====
 
*Information Framework:  RIM, data types, vocabulary…
 
*Information Framework:  RIM, data types, vocabulary…
 
*Behavior Framework:  UML, CDL…  
 
*Behavior Framework:  UML, CDL…  
−
*Governance Framework:  TSC operationalization:    
+
*Governance Framework:  TSC operationalization...    
 
*Conformance and Compliance Framework:  TSC operationaliztion…  
 
*Conformance and Compliance Framework:  TSC operationaliztion…  
 
*OVERALL:  RM-OPD, ISO 19763, 21090
 
*OVERALL:  RM-OPD, ISO 19763, 21090
 
====Links to current projects in development====
 
====Links to current projects in development====
−
*[http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?action=edit&ProjectNumber=365 Project Insight # 365]
+
*[http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?action=edit&ProjectNumber=365 Project Insight # 365] Enterprise Architecture Specification (Roadmap Project #44, 47)
−
*[http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?action=edit&ProjectNumber=469 Project Insight # 469]
+
*[http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?action=edit&ProjectNumber=469 Project Insight # 469] Enterprise Architecture Implementation Project (EA IP) Phase 1 (Roadmap Pjt 442)

Revision as of 17:20, 3 November 2009

Product Brief - Enterprise Architecture Specification=

_

back to Main_Page
back to Product List

Product Name

HL7 Services-Aware Enterprise Architecture Specification (SAEAF)

Topics

Standard Category

Modeling Standards

Integration Paradigm

Documents, Messages, Services

Type

Releases

Summary

SAEAF (The HL7 SOA-Aware Enterprise Architecture Framework) provides HL7 with an Enterprise Architecture Framework, i.e. a set of constructs, Best Practices, processes, etc. that enable HL7 specifications to achieve cross-specification consistency and coherancy irrespective of the chosen interoperability paradigm (messages, documents, or services). SAEAF consists of four core "frameworks":
(1) Information (including RIM, data types, vocabulary bindings, etc.),
(2) Behavior (subsuming the existing Dynamic Model),
(3) Enterprise Conformance and Compliance (including HL7's existing Implementation and Conformance standards), and
(4) Governance.

Description

See the SAEAF Overview Snapshot presentation from September 2009 here.


Business Case (Intended Use, Customers)

  • Enterprise interoperability projects including those building large-scale integrated health IT infrastructures at the national level

Benefits

The main benefits that will be derived from developing specifications using the SAEAF include: consistency of specifications, enhanced ability to manage loosely-coupled complex interactions between multiple trading partners, increased cross-organization reuse of architecture primitives (realizing the value proposition of CMETs and extending that proposition to include behavioral as well as static semantic constructs)

Implementations/ Case Studies (Actual Users)

  • National Cancer Institute (NCI),
  • Canada Health Infoway (CHI),
  • Open Health Tools (OHT) Architecture Project team

Resources

Work Groups

  • ArB - Architecture Board

Education

  • SAEAF 'book' under development
  • SAEAF document locations currently on GForge here
  • Tutorials offered at WGM on Services and Service-Awareness in HL7, and The SAEAF Behavior Framework
  • See more at http://www.hl7.org/implement/training.cfm
Certification Available
  • none

Presentations

Relationship to/ Dependencies on, other standards

  • Information Framework: RIM, data types, vocabulary…
  • Behavior Framework: UML, CDL…
  • Governance Framework: TSC operationalization...
  • Conformance and Compliance Framework: TSC operationaliztion…
  • OVERALL: RM-OPD, ISO 19763, 21090

Links to current projects in development

Retrieved from "https://wiki.hl7.org/w/index.php?title=Product_SAEAF&oldid=28694"