Difference between revisions of "TSC Agenda item list"

From HL7 TSC
Jump to navigation Jump to search
 
(6 intermediate revisions by the same user not shown)
Line 1: Line 1:
* Review HQ proposal of cost of providing secretarial support to the WGs [http://hl7projects.hl7.nscee.edu/tracker/index.php?func=detail&aid=745&group_id=52&atid=313 TSC Tracker # 745]
+
*By what mechanism/how does HL7 produce white papers? (from 20090922 Tuesday lunch discussion)
 +
 
 
*Tooling - what change the working group will see and when, and what does the TSC need to do (See [http://hl7projects.hl7.nscee.edu/tracker/index.php?func=detail&aid=323&group_id=52&atid=313 TSC Tracker # 323] and [http://hl7projects.hl7.nscee.edu/tracker/index.php?func=detail&aid=588&group_id=52&atid=313TSC Tracker # 588])
 
*Tooling - what change the working group will see and when, and what does the TSC need to do (See [http://hl7projects.hl7.nscee.edu/tracker/index.php?func=detail&aid=323&group_id=52&atid=313 TSC Tracker # 323] and [http://hl7projects.hl7.nscee.edu/tracker/index.php?func=detail&aid=588&group_id=52&atid=313TSC Tracker # 588])
*Classcode for medical diagnoses and related topics - between different committees. Patient Care statement collector DSTU, concern tracker DSTU and allergy model DSTU, noted by dr. William Goossen in reference to dr. Kai Heitmann's mention of a Dutch project.
+
 
 
*Formalization in DMPs of method and process used for e-voting.
 
*Formalization in DMPs of method and process used for e-voting.
* Review and discuss [http://hl7projects.hl7.nscee.edu/frs/?group_id=52 Work Group Health documents], and determine a plan to agree what the metrics should be in the spreadsheets, and what we show on the Monday evening cochairs meeting in Atlanta
+
* Questions for the Advisory Committee (AC) - prior to their conference calls.  Examples:
 +
**It would be useful to get a better idea of what the Advisory Council picture when they ready the roadmap strategies, and so I would like to hear one or more examples of SMART objectives for each of the strategies, or other quantifiable measures that they they would recommend as indicators that we are delivering successfully against each of the strategies. <br/>It may be that this is something that the roadmap taskforce should be doing -- but I think that this would be a good way to obtain a better understanding of what those outside HL7 would see as successful delivery
 +
**What information about HL7 projects, products and workgroups do they need to be able to more effectively generate unsolicited advice to HL7? Are there examples of how other organisations work with advisory councils, and the sort of information that is available and reviewed?
 +
**For each of the questions that HL7 asks the advisory council, what briefing information would it be useful to have about projects, products and workgroups? 
 +
**Once the advisory council is working on a question, how can HL7 ensure that they have the relevant information about HL7 projects, products and workgroups?
 +
**How do we better ensure that we are collecting and publishing information about projects, products and workgroups that is useful and used by the Advisory council and others, and how do we get feedback to those providing the information?
 +
*What categories or hierarchy does the TSC wish to see in the product list?  Need guidance for updates to the Project Scope Statement and display on the website  [[User:Llaakso|LynnL]] 16:34, 15 October 2009 (UTC)
 +
*FUTURE AGENDA ITEM: Look at a revision at an upcoming conference call of the CTO side, not necessarily the TSC side (2010MayWGM) from [[2010-05-15_TSC_WGM_Agenda]]

Latest revision as of 15:09, 25 May 2010

  • By what mechanism/how does HL7 produce white papers? (from 20090922 Tuesday lunch discussion)
  • Formalization in DMPs of method and process used for e-voting.
  • Questions for the Advisory Committee (AC) - prior to their conference calls. Examples:
    • It would be useful to get a better idea of what the Advisory Council picture when they ready the roadmap strategies, and so I would like to hear one or more examples of SMART objectives for each of the strategies, or other quantifiable measures that they they would recommend as indicators that we are delivering successfully against each of the strategies.
      It may be that this is something that the roadmap taskforce should be doing -- but I think that this would be a good way to obtain a better understanding of what those outside HL7 would see as successful delivery
    • What information about HL7 projects, products and workgroups do they need to be able to more effectively generate unsolicited advice to HL7? Are there examples of how other organisations work with advisory councils, and the sort of information that is available and reviewed?
    • For each of the questions that HL7 asks the advisory council, what briefing information would it be useful to have about projects, products and workgroups?
    • Once the advisory council is working on a question, how can HL7 ensure that they have the relevant information about HL7 projects, products and workgroups?
    • How do we better ensure that we are collecting and publishing information about projects, products and workgroups that is useful and used by the Advisory council and others, and how do we get feedback to those providing the information?
  • What categories or hierarchy does the TSC wish to see in the product list? Need guidance for updates to the Project Scope Statement and display on the website LynnL 16:34, 15 October 2009 (UTC)
  • FUTURE AGENDA ITEM: Look at a revision at an upcoming conference call of the CTO side, not necessarily the TSC side (2010MayWGM) from 2010-05-15_TSC_WGM_Agenda