ConCall-20070130

T3F - Transitional Technical Task Force

Tuesday Jan 30, 2007 12:00 PM (US Eastern Time, GMT -5)

Present

Beeler, Blobel, Buitendijk, Lorenzi, McCay, Parker

Prior Homework

Review/update working items as:

• Review description of Technical Directorate from Strategic Task Force Documentation (http://www.hl7.org/rwj/documentcenter/Strategic%20Initiatives%20Recommendations%207-26-06.doc)
• An alternative description which may be more relevant and up to date is posted under the Governance page at: http://www.hl7.org/documentcenter/public/wg/sito/SIIP%20Transition%20View%20of%20Org%20Model%20(3).doc
• CM_comments_on_TD_definition_from_Strategic_Recommendations

Accepted Agenda

1. (05 min) Roll Call & Accept agenda
2. (25 min) Core Challenges

   TD Organization, What is TD

3. (10 min)Architecture
4. (10 min) Document List

Core Challenges, particularly TD role & Organization

Whole meeting was devoted to discussion of this topic using two additional documents submitted by Lorenzi and Parker.

Charts from Virginia Lorenzi

Virginia Lorenzi had assembled a Power point of Charts that she prepared to reflect the TD relationships as they were expressed in either other charts or textual descriptions from th SI effort. These included:

• Simplified version of chart produced by ORC - Discussed why ARB, Cross-domain and PMO were separate from TD. Presume this is because it was felt that these were Board interests that were separable from TD.
• TD as presented by graphically by the consultants - Notes: PMO is part of TD; No overt resolution group (including ARB); Production (Ed, Tooling, Pubs added) and "Product Management" above the three areas.

  (Some discussion of what "Product" Management is (person, group, subset of TC chairs, etc.))

  In narrative, as noted, the Chairs of the three TC boxes are part of TD.

• Composition of TD, as presented in the consultants text - Suggests a good bit of "power" to CTO. However, the essence of the TD is to get and keep the organization moving forward in a coordinated fashion.

  Discussion of the CTO as a paid vs a volunteer position.

  • Pros - Full attention to the problem;
  • Cons - subsumes an influential position that volunteer leaders might aspire to and desire.

• Revised SI diagram based on feedback from Board and others - Notes: One worrisome feature is the "final authority" designation of the CTO. Note also, it includes the notion of a TSC.

Sketched chart from Craig Parker

Noting that the charts provided tended to mix and match between organizational responsibilities (hierarchy) and organizational relationships (horizontal), Craig Parker assembled a sketched chart that reflects both sets of relations on a single slide.

This wa discussed briefly. We concluded that a single format such as this is desirable as an end-product.

Comments from Charlie McCay on TD definition

Charlie McCay had prepared annotations on the TD definitions. The group agreed this is a good direction and would like to expand and refine this list in our next conference call.

Next Steps

Agreed for next meeting to:

1. Use the source documents, Virginia's charts, and Charlie's notes to refine a list of TD:
   • Responsibilities
   • Relationships
   • Consituencies
2. Using the above, and the charts provided by Craig and Virginia to craft a refined chart for TD that the T3F can endorse.