Difference between revisions of "T3F Agenda item list"

From HL7 TSC
Jump to navigation Jump to search
Line 1: Line 1:
 
['''''This is a place for T3F members to list or amend items that may (should) be used as Agenda items for a T3F Conference Call or Meeting''''']
 
['''''This is a place for T3F members to list or amend items that may (should) be used as Agenda items for a T3F Conference Call or Meeting''''']
 
+
* '''Architecture Project Proposal''' - Goal to define a project proposal for submission and adoption, as soon as feasible. Include - major steps, participants, level of detail, schedule. Three pieces - Models of Function, Static information, and Requirements (business).
*'''Substantivity''' - do we need to address ownership of, and processes surrounding, substantivity? --[[User:Craig|Craig]] 11:14, 17 January 2007 (PST)
+
* '''Model/pattern Harmonization''' - Sibling models for Clinical Statement; Role of CMETs. (From Cologne)
*''From Mead Walker:'' The future role of the ARB. --[[User:Craig|Craig]] 14:20, 17 January 2007 (PST)
+
* '''"Dynamic" Model''' - its generality, for future alignment with Architecture
*''T3F deliverables'' - review what we will produce and when [[User:Charliemccay|Charliemccay]] 04:41, 12 March 2007 (PDT)
+
* '''How to fit Functional Models into HL7 Framework'''
*''T3F success criteria'' - how do we know if the deliverables are good enough [[User:Charliemccay|Charliemccay]] 04:41, 12 March 2007 (PDT)
+
* '''Quality Issues of Ballot Content''' - Need to advise, oversee, understand and seek solutions.
 +
* '''Review TD responsibilities for potential processes'''
 +
* '''Revise TD foundation document'''
 +
* '''Quality Assessment criteria''' - how do we know if the deliverables from HL7 are at the desired level  and addressing the expectations and requirements of the users. (Relates to the quality gates of Project Life Cycle team.)

Revision as of 16:44, 22 May 2007

[This is a place for T3F members to list or amend items that may (should) be used as Agenda items for a T3F Conference Call or Meeting]

  • Architecture Project Proposal - Goal to define a project proposal for submission and adoption, as soon as feasible. Include - major steps, participants, level of detail, schedule. Three pieces - Models of Function, Static information, and Requirements (business).
  • Model/pattern Harmonization - Sibling models for Clinical Statement; Role of CMETs. (From Cologne)
  • "Dynamic" Model - its generality, for future alignment with Architecture
  • How to fit Functional Models into HL7 Framework
  • Quality Issues of Ballot Content - Need to advise, oversee, understand and seek solutions.
  • Review TD responsibilities for potential processes
  • Revise TD foundation document
  • Quality Assessment criteria - how do we know if the deliverables from HL7 are at the desired level and addressing the expectations and requirements of the users. (Relates to the quality gates of Project Life Cycle team.)