Difference between revisions of "Meeting-20090114"

From HL7 TSC
Jump to navigation Jump to search
Line 2: Line 2:
 
'''Wednesday January 14, 2009 Q3 and Q4'''
 
'''Wednesday January 14, 2009 Q3 and Q4'''
 
'''Architecture Rollout – SAEAF'''
 
'''Architecture Rollout – SAEAF'''
*Q3
+
Q3
**John Koisch (JK) presentation:
+
*John Koisch (JK) presentation:
***Messages (v2, v3), Documents (CDA), now Services (unified field theory)
+
**Messages (v2, v3), Documents (CDA), now Services (unified field theory)
***Implementable Working Interoperability:
+
**Implementable Working Interoperability:
***#Computable Semantic Interoperability
+
**#Computable Semantic Interoperability
***#Implementable Specifications
+
**#Implementable Specifications
***#Conformance model
+
**#Conformance model
***Next steps:
+
**Next steps:
****Capturing semantics:
+
***Capturing semantics:
****#Behavioral Framework
+
***#Behavioral Framework
****#Binding instance of a dynamic Model to Static models
+
***#Binding instance of a dynamic Model to Static models
****#Other artifacts
+
***#Other artifacts
***Governance model  
+
**Governance model  
****improves in the current working draft of the saeaf
+
***improves in the current working draft of the saeaf
***Conformance model
+
**Conformance model
****adding details and patterns
+
***adding details and patterns
**Questions:
+
*Questions:
***Bernd Blobel question: performing this activity needs an orientation; define roadmap direction of next step.  Urgent needs of current implementations should not preclude forming small group to define next steps.  Way to improve system for ontology driven architecture. He notes the Scientific domain is missing relationship to academic domain represented in this. What are you going to do for us?
+
**Bernd Blobel question: performing this activity needs an orientation; define roadmap direction of next step.  Urgent needs of current implementations should not preclude forming small group to define next steps.  Way to improve system for ontology driven architecture. He notes the Scientific domain is missing relationship to academic domain represented in this. What are you going to do for us?
***Request for agenda by quarter:  Marc Koehn 5-7 mins on rollout project; capture suggestions and inputs.  What should be done for momentum maintenance?
+
**Request for agenda by quarter:  Marc Koehn 5-7 mins on rollout project; capture suggestions and inputs.  What should be done for momentum maintenance?
**Marc Koehn (MK) presentation:
+
*Marc Koehn (MK) presentation:
***HL7 enterprise architecture implementation project (HL7 EA IP)
+
**HL7 enterprise architecture implementation project (HL7 EA IP)
****Ph 1 EA IP planning/ initiation
+
***Ph 1 EA IP planning/ initiation
****Overall goal: establish business architecture (BA) to enable HL7 to effectively develop and promulgate spec products consistent with emerging Hl7 Enterprise Architecture Spec (EAS)
+
***Overall goal: establish business architecture (BA) to enable HL7 to effectively develop and promulgate spec products consistent with emerging Hl7 Enterprise Architecture Spec (EAS)
****Conceptual project phases:  
+
***Conceptual project phases:  
*****Phase 0 project planning
+
****Phase 0 project planning
*****Phase 1 formal plan, initiate project
+
****Phase 1 formal plan, initiate project
*****Phase 2, implementation.
+
****Phase 2, implementation.

Revision as of 16:33, 15 January 2009

HL7 WGM Joint Session

Wednesday January 14, 2009 Q3 and Q4 Architecture Rollout – SAEAF Q3

  • John Koisch (JK) presentation:
    • Messages (v2, v3), Documents (CDA), now Services (unified field theory)
    • Implementable Working Interoperability:
      1. Computable Semantic Interoperability
      2. Implementable Specifications
      3. Conformance model
    • Next steps:
      • Capturing semantics:
        1. Behavioral Framework
        2. Binding instance of a dynamic Model to Static models
        3. Other artifacts
    • Governance model
      • improves in the current working draft of the saeaf
    • Conformance model
      • adding details and patterns
  • Questions:
    • Bernd Blobel question: performing this activity needs an orientation; define roadmap direction of next step. Urgent needs of current implementations should not preclude forming small group to define next steps. Way to improve system for ontology driven architecture. He notes the Scientific domain is missing relationship to academic domain represented in this. What are you going to do for us?
    • Request for agenda by quarter: Marc Koehn 5-7 mins on rollout project; capture suggestions and inputs. What should be done for momentum maintenance?
  • Marc Koehn (MK) presentation:
    • HL7 enterprise architecture implementation project (HL7 EA IP)
      • Ph 1 EA IP planning/ initiation
      • Overall goal: establish business architecture (BA) to enable HL7 to effectively develop and promulgate spec products consistent with emerging Hl7 Enterprise Architecture Spec (EAS)
      • Conceptual project phases:
        • Phase 0 project planning
        • Phase 1 formal plan, initiate project
        • Phase 2, implementation.