TSC Communications Plan 2010

Communications plan for 2010

Approved ccyymmdd

• This Communications Plan will be maintained as part of the TSC Communication Strategy Project (see TSC Tracker # 1603), facilitated by Ravi Natarajan

With whom does the TSC communicate?

This section of the plan describes how the TSC communicates with different groups, and the purpose and value of that communications. It may also include some examples of the sort of communications that are most valuable for each group.

The board

• Topics to report to the board
  • major product proposals
  • suggestions for new external relationships
  • standards currently in use, and under development
  • financial reporting on funded activities
  • proposals for funded activity
  • delivery plan against roadmap (and progress against that plan)
• Topics to hear from the board
  • roadmap and strategic direction
  • roles and responsibilities

Roadmap Committee

• TSC Steering Division (SD) Co-Chairs are members on the Roadmap Task Force to provide input and facilitate communication

Marketing Committee

• Project status overview - see the Project Insight Searchable Database
• Product Status overview
• cm - assume these are the reports that exist already - would be useful to have a link so that folk can see current versions, and maintenence process

Organizational Relations Committee

The TSC has a liaison appointed to the Organizational Relations Committee, currently served by Helen Stevens

Working Group Meeting Planning Committee

The TSC has a liaison appointed to the committee, currently served by Helen Stevens

The Steering Divisions

• delivery plan against roadmap (and progress against that plan)
• Project status overview
• Product Status overview
• Work Group Health reports (each WGM) - see archive on TSC GForge File Repository

The co-chairs

• weekly Update from the TSC - see archive on HL7 Document Center includes:
  • new project proposals
  • new publication requests (for Informative or DSTU items)
• delivery plan against roadmap (and progress against that plan)

The HL7 membership

• delivery plan against roadmap (and progress against that plan)
• articles by CTO, TSC Chair, Lynn, TSC members in HL7 Technical Newsletters

The Advisory Council

The CTO - John Quinn, and the TSC Chair are members of the Advisory Board.

The Affiliates Council

• Affiliates' Communications will be documented as part of the TSC Communication Strategy Project (see TSC Tracker # 1603), facilitated by Ravi Natarajan

The wider community of HL7 users and stakeholders

• Approved projects and publication requests are published in the Update from the TSC.
• The Update from the TSC is distributed via email to the cochairs and International Council members.
• The Update from the TSC is included for distribution with the HL7 e-news
• The Update from the TSC is uploaded to the HL7 Document Center on the web site under the grouping 'Work Group Project Updates'.
• A link to the document on the Document Center is published to the HL7 International LinkedIn group.

Communication to the TSC

Inward communications to the TSC should occur through several paths, including:

• PIC performs a useful communication path today for individuals and new volunteers and affords the added advantage of a forum for discussing procedural issues before they are added ot the PIC open issues list. This role should be continued with PIC as a TSC-appointed committee, and they should continue to maintain the PIC open issues list.
• The TSC will hold an "open mic" session for Co-chairs at each TSC Retreat (Plenary) Meeting with the issues logged in the minutes
• Issues list- The TSC maintains and tracks a publicly available issues list for topics under TSC consideration. This list will require:
  • Submittal forms
    • the TSC uses the standard Project Scope Statement form for requests for approval of new projects.
    • The TSC uses the DSTU request to publish form for requests to publish DSTU Standards.
    • The TSC uses the Informative Document request to publish form for requests to publish Informative Documents.
    • The TSC can receive any other issues for consideration through the Steering Division co-chairs, ArB or Affiliate Representatives, or from the TSC Feedback site.
  • Submissions Issues for the list would be received from:
    • the TSC "open mic" sessions,
    • form submittal at the TSC Feedback site,
    • Referral from Ballot reconciliation (through SDs) to TSC
• The TSC also uses a list server for internal TSC communications

Communications from the TSC

Outward communications from the TSC should include:

• e-News - routine contributions from TSC mirroring the Update from the TSC
• Newsletter articles
• TSC Report at a WGM General Session
• Summary of TSC Plenary and copies of presentation posted on web site
• TSC Wiki (open for reading)
  • Process information
  • Minutes & Agendas
  • Search capability on TSC Wiki
• Status reports (central, easily found, well tracked) on:
  • Working Group information and Work Group Health
  • Working Group Project Information (including scope statements and status)
    • weekly Update from the TSC - see archive on HL7 Document Center
  • Architecture/Methodology Issues, etc.
  • Search capability
• TSC Gforge Project
  • TSC issue list
  • Ballot title approvals