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

Difference between revisions of "September2008WGM arb doc"

From HL7Wiki
Jump to navigation Jump to search
m (Undo revision 17690 by Ajulian (Talk))
Line 23: Line 23:
 
#Artifacts for SOA
 
#Artifacts for SOA
  
−
===Stack of specifications that support ISCS's===
+
==Enterprise Architecture Framework ==
−
[[Services_Aware_Enterprise_Architecture_Framework|Return to SAEAF Table of Contents]]
+
AMS: belongs in Stack of Specifications that support ISCS above
−
==Reference==
+
 
−
#Reference Information Model (Rim)
+
JK: I am not sure it belongs there
−
#Abstract data types (adt)
+
 
−
#HL7 Development framework
+
#Interoperability service contract specifications
−
##Message Development framework
+
#Levels of Interoperability Service Contract Specifications(ISCS) (formerly known as trading partner agreements(TPA))
−
##Services Development framework
+
#Stack of specifications that support ISCS's
−
##Structured Document Development framework
+
##Reference
−
##Electronic Health Record Functional Model  
+
###Reference Information Model (Rim)
−
###Profile
+
###Abstract data types (adt)
−
#cpp (Email to Grahame)
+
###HL7 Development framework
−
#Guidance for using vocabulary in information structures(terminfo)
+
####Message Development framework
−
#Structured Vocabulary (sv)
+
####Services Development framework
−
#dmel
+
####Structured Document Development framework
−
#IV (email to Grahame )
+
####Electronic Health Record Functional Model  
−
#Service Specification Methodology
+
#####Profile
−
== Blueprint==
+
###cpp (Email to Grahame)
−
#Domain analysis Model(DAM)
+
###Guidance for using vocabulary in information structures(terminfo)
−
#Domain Message Information Model(DMIM)
+
###Structured Vocabulary (sv)
−
#Service Functional Model SFM
+
###dmel
−
#Electronic Health Record Functional Model (EHR-FM)
+
###IV (email to Grahame )
−
==Platform Independent Model==
+
###Service Specification Methodology
−
#Refined Message Information models(RMIM)
+
## Blueprint
−
#Templates  
+
###Domain analysis Model(DAM)
−
#CDA lgs   
+
###Domain Message Information Model(DMIM)
−
#IHE Profiles(parts)
+
###Service Functional Model SFM
−
#Dynamic Models (Instance)
+
###Electronic Health Record Functional Model (EHR-FM)
−
#Logical Service Model
+
##Platform Independent Model
−
==Platform specific model==
+
###Refined Message Information models(RMIM)
−
#Implementable/Implementation Technology Specification (ITS)
+
###Templates  
−
#Serialization models
+
###CDA lgs   
−
#Web Services Description Language (WSDL) Fragments
+
###IHE Profiles(parts)
−
#Vertical Bar (AKA Version 2) (VBAR)
+
###Dynamic Models (Instance)
−
==Platform Instance==
+
###Logical Service Model
−
#Full WSDLs
+
##Platform specific model
−
#Simple Object Access Protocol (SOAP)
+
###Implementable/Implementation Technology Specification (ITS)
−
#JAVA POJO/EJB
+
###Serialization models
−
#Lower Level Protocol (LLP)
+
###Web Services Description Language (WSDL) Fragments
 +
###Vertical Bar (AKA Version 2) (VBAR)
 +
##Platform Instance
 +
###Full WSDLs
 +
###Simple Object Access Protocol (SOAP)
 +
###JAVA POJO/EJB
 +
###Lower Level Protocol (LLP)
 +
#Structure of HL7 delivers support for customers to craft ISCS
 +
#Taxonomy and roadmap of the standards
 +
#Ballot Quality

Revision as of 13:39, 7 August 2008

September Table of Contents

Services Aware Enterprise Architecture Framework

  1. 2bBAM
    1. Drivers(Goals, customer needs, Performance measurements) Tony
    2. Organization (participants and roles) Tony
    3. Organization Structures Tony
    4. Organization Processes Tony
    5. Artifacts Jane
      1. Taxonomy and roadmap of the standards
    6. Levels of Interoperability Service Contract Specifications(ISCS) (formerly known as trading partner agreements(TPA))
    7. Stack of specifications that support ISCS's John (from EA Framework below?)
    8. Structure of HL7 delivers support for customers to craft ISCS
  2. Interoperability Service Specification
    1. Interoperability service contract specifications John (Conformance and Compliance document from NCI as content)
      1. Service enabled Dynamic Framework Mead
      2. Static Model
    2. Meta-Model
    3. Taxonomy of Services
  3. Conformance
    1. Conformance Criteria (assertions)
    2. Conformance adherence (Realization)
    3. Conformance Validation (Inspection/testing)
  4. Artifacts for SOA

Enterprise Architecture Framework

AMS: belongs in Stack of Specifications that support ISCS above

JK: I am not sure it belongs there

  1. Interoperability service contract specifications
  2. Levels of Interoperability Service Contract Specifications(ISCS) (formerly known as trading partner agreements(TPA))
  3. Stack of specifications that support ISCS's
    1. Reference
      1. Reference Information Model (Rim)
      2. Abstract data types (adt)
      3. HL7 Development framework
        1. Message Development framework
        2. Services Development framework
        3. Structured Document Development framework
        4. Electronic Health Record Functional Model
          1. Profile
      4. cpp (Email to Grahame)
      5. Guidance for using vocabulary in information structures(terminfo)
      6. Structured Vocabulary (sv)
      7. dmel
      8. IV (email to Grahame )
      9. Service Specification Methodology
    2. Blueprint
      1. Domain analysis Model(DAM)
      2. Domain Message Information Model(DMIM)
      3. Service Functional Model SFM
      4. Electronic Health Record Functional Model (EHR-FM)
    3. Platform Independent Model
      1. Refined Message Information models(RMIM)
      2. Templates
      3. CDA lgs
      4. IHE Profiles(parts)
      5. Dynamic Models (Instance)
      6. Logical Service Model
    4. Platform specific model
      1. Implementable/Implementation Technology Specification (ITS)
      2. Serialization models
      3. Web Services Description Language (WSDL) Fragments
      4. Vertical Bar (AKA Version 2) (VBAR)
    5. Platform Instance
      1. Full WSDLs
      2. Simple Object Access Protocol (SOAP)
      3. JAVA POJO/EJB
      4. Lower Level Protocol (LLP)
  4. Structure of HL7 delivers support for customers to craft ISCS
  5. Taxonomy and roadmap of the standards
  6. Ballot Quality
Retrieved from "https://wiki.hl7.org/w/index.php?title=September2008WGM_arb_doc&oldid=17691"