Difference between revisions of "ConCall-20070227"
Jump to navigation
Jump to search
WoodyBeeler (talk | contribs) |
WoodyBeeler (talk | contribs) |
||
| Line 1: | Line 1: | ||
T3F - Transitional Technical Task Force | T3F - Transitional Technical Task Force | ||
| − | |||
| − | |||
Tuesday Feb 27, 2007 12:00 PM (US Eastern Time, GMT -5) | Tuesday Feb 27, 2007 12:00 PM (US Eastern Time, GMT -5) | ||
| − | + | =Present= | |
| + | Beeler, Case, McCaslin, McCay, Lorenzi, Parker | ||
| − | + | =Accepted Agenda= | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | = | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
#''(05 min)'' Roll Call & Accept agenda | #''(05 min)'' Roll Call & Accept agenda | ||
#''(50 min)'' Technical Directorate Discussions | #''(50 min)'' Technical Directorate Discussions | ||
| − | #:''( | + | #:''(40 min)'' TD Sub-groups Names and Composition |
| − | |||
#:''(10 min)'' Review changes to TD Charts and list of responsibilities | #:''(10 min)'' Review changes to TD Charts and list of responsibilities | ||
#'' (05 min)'' Next Steps | #'' (05 min)'' Next Steps | ||
| + | |||
| + | =Other Business= | ||
| + | *T3F Monthly Progress report is due tomorrow. Beeler will submit this and copy to the T3F. | ||
| + | *Approved minutes of last week's meeting | ||
| + | |||
| + | =TD Sub-groups Names and Composition= | ||
| + | ==Background== | ||
| + | As a starting point for this discussion, the T3F used a previously developed Strategic Initiative document titled [http://www.hl7.org/documentcenter/public/wg/t3f%5Cgeneral/HL7%20Organizational%20Framework%20-%20V0005.doc "Creation of the Transitional Technical Task Force (T3F)"]. This document from November 2005 included a summary of the committees to be organized and coordinated by the the TD. | ||
| + | |||
| + | The objective of this T3F meeting is to refine and resolve our understanding of what the structure represents, where we think alternate committee assignments might be made and where we feel this structure may cause "problems" in the future. | ||
| + | |||
| + | The findings and outcome of this meeting '''have not been formally adopted.''' We agreed to document the outcome of the discussions and then to re-visit this in the next meeting or so. (This strategy is also being followed with regards to the composition and function of the TD itself.) | ||
| + | |||
| + | ==Organizing Principle== | ||
| + | During the discussions today, the T3F made the following observations: | ||
| + | *HL7 members join committees because of their personal (or corporate) interest in the '''subject matter content''' of the committee, regardless of whether their interest stems from academic, development or implementation activities. | ||
| + | *The original break-out of committees (provided in the [http://www.hl7.org/documentcenter/public/wg/t3f%5Cgeneral/HL7%20Organizational%20Framework%20-%20V0005.doc SI document]) aggregates the committees by commonality of '''what they produce''' and the relationship of that work product to the other Working Group committees. There was a consensus expressed that this is a sound approach. | ||
| + | *One of the key activities of the TD will be to identify and reduce those places where committees are "stepping on each others toes" or "reinventing the wheel" Coordination within the proposed sub-groups will facilitate this activity. | ||
| + | *The existing relationship between TCs and SIGs may need to be "re-thought", because this strategy will clearly place a number of SIGS in a sub-group that is different from that to which their current "parent TC" is assigned. | ||
| + | *It will be important to not disrupt existing collaboration while establishing this organization, and it is clear that many topics will be managed, in "matrix fashion" between committees in two or three sub-groups. | ||
| + | *A number of committees clearly produce products that fit in two or even three of the sub-groups. This will undoubtedly cause the TD to consider whether to recommend that these groups be split. | ||
| + | |||
| + | ==Sub-group Definition and Composition== | ||
| + | The remainder of these minutes reflect changes to that portion of the [http://www.hl7.org/documentcenter/public/wg/t3f%5Cgeneral/HL7%20Organizational%20Framework%20-%20V0005.doc original document] that divided the existing TCs and SIGs into three groups for the purposes of nominating and electing the representatives to the T3F and listed the "Other committees" to be considered. | ||
| + | |||
=[[T3F Agenda item list|Agenda item list (our sand box for future meetings)]]= | =[[T3F Agenda item list|Agenda item list (our sand box for future meetings)]]= | ||
=[[T3F Action item list|Click for T3F Action Item List]]= | =[[T3F Action item list|Click for T3F Action Item List]]= | ||
Revision as of 01:26, 28 February 2007
T3F - Transitional Technical Task Force
Tuesday Feb 27, 2007 12:00 PM (US Eastern Time, GMT -5)
Contents
Present
Beeler, Case, McCaslin, McCay, Lorenzi, Parker
Accepted Agenda
- (05 min) Roll Call & Accept agenda
- (50 min) Technical Directorate Discussions
- (40 min) TD Sub-groups Names and Composition
- (10 min) Review changes to TD Charts and list of responsibilities
- (05 min) Next Steps
Other Business
- T3F Monthly Progress report is due tomorrow. Beeler will submit this and copy to the T3F.
- Approved minutes of last week's meeting
TD Sub-groups Names and Composition
Background
As a starting point for this discussion, the T3F used a previously developed Strategic Initiative document titled "Creation of the Transitional Technical Task Force (T3F)". This document from November 2005 included a summary of the committees to be organized and coordinated by the the TD.
The objective of this T3F meeting is to refine and resolve our understanding of what the structure represents, where we think alternate committee assignments might be made and where we feel this structure may cause "problems" in the future.
The findings and outcome of this meeting have not been formally adopted. We agreed to document the outcome of the discussions and then to re-visit this in the next meeting or so. (This strategy is also being followed with regards to the composition and function of the TD itself.)
Organizing Principle
During the discussions today, the T3F made the following observations:
- HL7 members join committees because of their personal (or corporate) interest in the subject matter content of the committee, regardless of whether their interest stems from academic, development or implementation activities.
- The original break-out of committees (provided in the SI document) aggregates the committees by commonality of what they produce and the relationship of that work product to the other Working Group committees. There was a consensus expressed that this is a sound approach.
- One of the key activities of the TD will be to identify and reduce those places where committees are "stepping on each others toes" or "reinventing the wheel" Coordination within the proposed sub-groups will facilitate this activity.
- The existing relationship between TCs and SIGs may need to be "re-thought", because this strategy will clearly place a number of SIGS in a sub-group that is different from that to which their current "parent TC" is assigned.
- It will be important to not disrupt existing collaboration while establishing this organization, and it is clear that many topics will be managed, in "matrix fashion" between committees in two or three sub-groups.
- A number of committees clearly produce products that fit in two or even three of the sub-groups. This will undoubtedly cause the TD to consider whether to recommend that these groups be split.
Sub-group Definition and Composition
The remainder of these minutes reflect changes to that portion of the original document that divided the existing TCs and SIGs into three groups for the purposes of nominating and electing the representatives to the T3F and listed the "Other committees" to be considered.
