T3F Cologne Deliverable

From HL7 TSC
Jump to navigation Jump to search

Report to HL7 Board from Transitional Technical Task Force


The following documents the recommendations of the Technical Transition Task Force (T3F) with regards to completing the definition of the Technical Directorate and proceeding to establish same.

The T3F began work in earnest at the Winter Working Group Meeting in January 2007. The T3F met three times face-to-face at that meeting and have held a conference call every week but one since then. The group used a number of sources in its efforts -- Strategic Initiative documents, ORC reports, work from the project life-cycle team, etc. In addition, the group has benefited greatly by having consistent attendance at its meetings from the TSC (Quinn and Hammond), the ARB (Walker) and the project life-cycle group (McCaslin), and wishes to thank each of these groups for their support.

Early on in its efforts, the T3F determined that its primary initial task was to provide a complete definition of the roles and composition of the Technical Directorate that could be adopted at the May Working Group Meeting. This would afford the opportunity to review these recommendations in Cologne and allow the Technical Directorate to be formed as rapidly as possible thereafter.


Mission Statement (Woody)

The HL7 Technical Directorate oversees and coordinates the technical effort contributed by the HL7 volunteers who make up the HL7 Working Group. Its mission is to assure that the efforts of the Working Group are focused on the overall HL7 mission established by the HL7 Board.

The Technical Directorate and the HL7 Working Group operate in such a way so as to:

  • respect the contributions and ideas of the talented individuals who make up the Working Group;
  • maintain an effective focus on the goals of HL7;
  • assure that the all major decisions are based on consensus of the stakeholders;
  • maximize sharing and "re-use" of work products between elements of the Working Group;
  • use project management to assure that project goals are articulated and met;
  • reduce competition and conflict between the elements of the Working Group; and
  • assure that HL7 standards are developed on a solid architectural foundation that assures consistency and interoperability.

The Technical Directorate criteria for success must center around three concepts -- assuring the continuity and vitality of the HL7 volunteer-based Working Group; maintaining coherent inter-operable standards while minimizing duplication of effort; and providing sound consensus-based standards that meet the needs and schedule requirements of HL7's clients.

Success Criteria (Charlie)

Responsibilities (Virginia)

(draft based on editing of Charlie's/and Woody;'s edit of the strat initiatives. also based on Woody's mission. Also includes pulling forward TSC responsibilities from Bylaws and Policies and Procedures.)

Oversees execution of standards development

Assures that the efforts of the Working Group (WG) is effectively focused on accomplishing the product and services strategy set forth by the board.
  • Participates in development of an HL7 Product and Services strategy for adoption by the HL7 Board
  • Oversees the TD sub-groups in the establishment and management of projects and project teams to accomplish the product and services strategy set by the Board. To that end, it works through the sub-groups to:
    • Approve new work groups based on priority projects
    • Dissolve work groups no longer required based on the HL7 Products and Services strategy
    • Works with sub-groups to align and prioritize projects in accordance with the products and services strategy
    • Working with the subgroups, helps to ensure the availability of project resources
      • people, rooms, etc.
      • includes ensuring the continuity, vitality, and effectiveness of the HL7 volunteer-based Working Group
  • Approve, monitor, and perhaps intervene in overall product development
    • Works with the sub-groups and the PMO to oversee the tracking of projects to meet HL7 objectives. The sub-groups will function to assure that they or the committees under them set milestones, monitor and ensure that quality assurance has been done
  • Performs top-level review and authorizations as specified in the formal development process:
    • Working with the subgroups, reviews, approves, and prioritizes requests for new projects.
    • Working with the subgroups, recommends project probation or dissolution to the Board
    • Sets remit for ARB and project office and serves as escalation point for issues not resolved at commitee or subgroup level.
    • ensures that quality checks in the project development process are satisfied.
    • Reviews and approves requests from Technical Committees to initiate a ballot and serves as escalation point for ballot response handling.

Provides a Coherent Architecture and Development Process

Establishes (or reviews) the Technical Architecture, the development methodologies, and the work processes to be used by the WG in developing HL7 consensus-based standards specifications
  • has overall responsibility for the development and adherence to an HL7 Technical Architecture and the development, maintenance, and execution of an HL7 standards development process
    • working through sub-groups, makes sure that architecture and process is developed, maintained and enhanced.
      • through Committees such as MnM, Vocabulary, and PIC as well as the ARB.
  • ensures that the balloting of any HL7 protocol

specification, or portion thereof, is carried out in accordance with HL7 Bylaws and ANSI rules.

    • Defines and manages international harmonization mechanism

Oversees the technical operations of the Working Group

Serves as technical authority of HL7 and assures that the WG works smoothly together and covers the work scope in a consistent manner.
  • Ensures that Working Group policies and procedures and bylaws are followed
    • With the subgroups, oversees execution of procedures for committee creation, dissolution, and co-chair elections.
    • ensures that meetings and calls are carried out according to policy
  • Oversees continuous quality process
  • Works through sub-groups to identify cross-domain and cross-function gaps, overlaps, discrepancies, potentials for collaboration, and conflicts and recommends resolution
  • responsible for any official interpretation of the HL7 standards.
  • serves as technical escalation point for HL7
    • resolves conflicts within the Working Group and prioritizes resources according to project priority (example, room balancing at WGMs)
    • ensures the impartial handling of substantive and procedural

complaints regarding any action or inaction as related to the production of HL7 specifications.

Composition (Woody - based on minutes)

Relationships (Woody - based on minutes)

Decision Making Practices (Jim)

Tactical Plan to Establish Technical Directorate (Craig)

Project Plan for Architecture (Berndt)