CM comments on TD definition from Strategic Recommendations

Technical Directorate

The Technical Directorate (TD) is responsible for product project approval and management oversight. It will rely on both staff and volunteers with increasing levels of professional staffing as the financial model allows. Note: Volunteer representatives to the TD should have sufficient support from their employers to ensure an average of 3-4 hours/week participation.

Responsibilities:

The list of items in here are the same ones Charlie posted on 1/30. All I have done is to "define" a trio of categories and then assign each of the original items to one of the categories. (One item was copied into two categories.) I did reorder them for better consistency. WoodyBeeler

Oversee development of standards (products)

Assures that the efforts of the Working Group (WG) to produce standards proceeds at a reasonable pace

• Oversees standards development
  • Current: ?MnM, ?TSC, ?not happening
  • Propose: Establish visibility required, TD to work with TSC on process (JTC: Enforcement on adherence to methodology? It is common for there to be a lack of HDF components being submitted for ballot)
• Oversees the TD sub-groups in the establishment 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
    • Current: TSC
    • Proposed: TD
  • Approve, monitor, and perhaps intervene in product project development
    • Current: ARB and project office, and self regulation by committees
    • Propose: TD sets remit for ARB and project office
• Works with the sub-groups to oversee the establishment and 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
    • Current: None
    • Proposed: TD Provide targets and overview for PMO
  • Review requests for new projects. Upon acceptance of the proposal, solicits input for appropriate committee placement
    • Propose: Direct project request to appropriate committee to develop initial Project Scope / Proposal
  • Recommend project probation or dissolution to the Board following collaboration with the TSC
    • Propose: TD to establish process where ineffective projects close without need for intervention
• Participate in (or drive?) development of an HL7 Product and Services strategy for adoption by the HL7 Board
• Performs top-level review and authorizations as specified in the formal development process, such as:
  • Reviews and approves requests from Technical Committees to initiate a ballot

Provide 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 specifications

• Supports CTO in development and implementation of HL7 Technical Architecture and standards development
  • Current: Done by ARB, MnM (HDF), PIC/ORC, Transition teams
  • Propose: Process Group established to maintain definitive process (HDF), or review focus of HDF/PIC group
• Defines international harmonization mechanism and manages process
  • Current: MnM
  • part of process task

Resolve Issues and Omissions within the Scope and Work Product of WG

Assures that the WG works smoothly together and covers the work scope in a consistent manner

• Oversees continuous quality process
  • Current: TSC?, PIC, ARB
  • Proposed: Technical Quality and Process Quality split between son-of-ARB and HDF/PIC
• Identifies gaps, overlaps and conflicts in domain content and recommends resolution
  • generic responsibility -- catch-all for making technical solution better - this is a TD responsibility
  • Current: MnM / add hoc (eg Clinical Statement, Common orders)
  • Proposed: TD working through sub-groups

Operation of the TD:

• Meets bi-weekly between Working Group Meetings (WGM)
• Meets on the opening and closing day of each WGM
• Meetings are open to the public, unless called into executive session by CTO; non-members may ask to be recognized