Difference between revisions of "TSC Communications Plan 2010"

From HL7 TSC
Jump to navigation Jump to search
 
(3 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
=Communications plan for 2010=
 
=Communications plan for 2010=
 
Approved ccyymmdd
 
Approved ccyymmdd
−
==Who does the TSC communicate with?==
+
*This Communications Plan will be maintained as part of the [http://gforge.hl7.org/gf/download/trackeritem/1603/7390/HL7PSS-TSCCommunicationPlan20100712.doc TSC Communication Strategy Project] (see [http://gforge.hl7.org/gf/project/tsc/tracker/?action=TrackerItemEdit&tracker_item_id=1603 TSC Tracker # 1603]), facilitated by Ravi Natarajan
 +
 
 +
<!--Should we consider a communications report indicating how the TSC was intending to communicate and whether we actually did so, should we create a report for each WGM, indicating which issues we have with each of the groups-->
 +
 
 +
 
 +
==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.
 
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 ===
 
=== The board ===
Line 14: Line 19:
 
** roadmap and strategic direction
 
** roadmap and strategic direction
 
** roles and responsibilities
 
** 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 ===
 
=== Marketing Committee ===
−
* delivery plan against roadmap (and progress against that plan)
+
* Project status overview - see the [http://www.hl7.org/permalink/?searchableProjectIndex Project Insight Searchable Database]
−
* Project status overview
 
 
* Product Status overview
 
* 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 ===
 
=== The Steering Divisions ===
Line 24: Line 39:
 
* Project status overview
 
* Project status overview
 
* Product Status overview
 
* Product Status overview
 +
*Work Group Health reports (each WGM) - see archive on [http://gforge.hl7.org/gf/project/tsc/frs/?action=FrsReleaseBrowse&frs_package_id=121 TSC GForge File Repository]
  
 
=== The co-chairs ===
 
=== The co-chairs ===
−
*new project proposals
+
* weekly Update from the TSC - see archive on [http://www.hl7.org/documentcenter/index.cfm?action=dc.home&documenttype_id=23 HL7 Document Center] includes:
−
*new publication requests (for Informative or DSTU items)
+
**new project proposals
 +
**new publication requests (for Informative or DSTU items)
 
* delivery plan against roadmap (and progress against that plan)
 
* delivery plan against roadmap (and progress against that plan)
  
 
=== The HL7 membership ===
 
=== The HL7 membership ===
 
* delivery plan against roadmap (and progress against that plan)
 
* delivery plan against roadmap (and progress against that plan)
 +
* articles by CTO, TSC Chair, Lynn, TSC members in [http://www.hl7.org/documentcenter/index.cfm?action=dc.home&documenttype_id=21 HL7 Technical Newsletters]
 +
 
=== The Advisory Council ===
 
=== The Advisory Council ===
−
The CTO - John Quinn, and the TSC Chair attend the meetings of the Advisory Board.
+
The CTO - John Quinn, and the TSC Chair are members of the Advisory Board.
 +
 
  
 
=== The Affiliates Council ===
 
=== The Affiliates Council ===
−
See [http://gforge.hl7.org/gf/project/tsc/tracker/?action=TrackerItemEdit&tracker_item_id=1603&start=0 TSC Tracker # 1603] for the TSC Communication Strategy Project, facilitated by Ravi Natarajan  
+
*Affiliates' Communications will be documented as part of the [http://gforge.hl7.org/gf/download/trackeritem/1603/7390/HL7PSS-TSCCommunicationPlan20100712.doc TSC Communication Strategy Project] (see [http://gforge.hl7.org/gf/project/tsc/tracker/?action=TrackerItemEdit&tracker_item_id=1603 TSC Tracker # 1603]), facilitated by Ravi Natarajan
 +
 
  
 
=== The wider community of HL7 users and stakeholders ===
 
=== The wider community of HL7 users and stakeholders ===
−
Approved projects and publication requests are published in the Update from the TSC.
+
*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 distributed via email to the cochairs and International Council members.
−
The Update from the TSC is uploaded to the [http://www.hl7.org/documentcenter/index.cfm? HL7 Document Center] on the web site under the grouping 'Work Group Project Updates'.
+
*The Update from the TSC is included for distribution with the HL7 e-news
−
A link to the document on the Document Center is published to the [http://www.linkedin.com/groups?gid=2478980&trk=hb_side_g HL7 International LinkedIn group].  
+
*The Update from the TSC is uploaded to the [http://www.hl7.org/documentcenter/index.cfm? 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 [http://www.linkedin.com/groups?gid=2478980&trk=hb_side_g HL7 International LinkedIn group].  
  
 
==Communication to the TSC==
 
==Communication to the TSC==
 
Inward communications to the TSC should occur through several paths, including:
 
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.
 
*'''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 written, logged and formally tracked
+
*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:
+
*'''Issues list'''- The TSC maintains and tracks a publicly available [http://gforge.hl7.org/gf/project/tsc/tracker/?action=TrackerItemBrowse&tracker_id=313 issues list] for topics under TSC consideration.  This list will require:
−
**'''Submittal form''' - the TSC should develop a standard form for documenting issues. This form should allow the submitter to classify the type and severity of the problem, should identify the perspective from which the individual is submitting the issue, a description of the issue, and the submitters desired or recommended action to resolve the issue. This form would be used for both the "open mic" sessions and for e-mail submissions.
+
**'''Submittal forms'''  
−
**'''Issue posting''' Active issues should be posted and tracked on the TSC Wiki
+
***the TSC uses the standard [http:///www.hl7.org/permalink/?ProjectScopeStatement Project Scope Statement] form for requests for approval of new projects.  
 +
***The TSC uses the [http://www.hl7.org/permalink/?DSTUTemplate DSTU request to publish form] for requests to publish DSTU Standards.
 +
***The TSC uses the [http://www.hl7.org/permalink/?InformativeDocTemplate 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 [http://www.hl7.org/Special/committees/tsc/suggest.cfm TSC Feedback site].
 
**'''Submissions''' Issues for the list would be received from:
 
**'''Submissions''' Issues for the list would be received from:
 
***the TSC "open mic" sessions,  
 
***the TSC "open mic" sessions,  
−
***form submittal (below) or by
+
***form submittal at the [http://www.hl7.org/Special/committees/tsc/suggest.cfm TSC Feedback site],
 
***Referral from Ballot reconciliation (through SDs) to TSC
 
***Referral from Ballot reconciliation (through SDs) to TSC
−
*Maintain a '''list server''' for internal TSC communications
+
*The TSC also uses a '''list server''' for internal TSC communications
−
*Establish, for those persons not wishing to escalate issues or questions through their Steering Division Representative, an online form for anonymous input through which new issues (using the form) and  questions can be submitted.  This is available at [http://www.hl7.org/special/committees/tsc/suggest.cfm TSC Feedback Site].
+
 
  
 
==Communications from the TSC==
 
==Communications from the TSC==
 
Outward communications from the TSC should include:
 
Outward communications from the TSC should include:
−
*'''e-News''' - routine contributions from TSC
+
*'''e-News''' - routine contributions from TSC mirroring the Update from the TSC
 
*'''Newsletter articles'''
 
*'''Newsletter articles'''
 
*'''TSC Report at a WGM General Session'''  
 
*'''TSC Report at a WGM General Session'''  
 
*'''Summary of TSC Plenary''' and copies of presentation posted on web site
 
*'''Summary of TSC Plenary''' and copies of presentation posted on web site
−
*'''TSC Wiki (open for reading)'''  
+
*'''[http://hl7tsc.org/wiki/ TSC Wiki] (open for reading)'''  
−
**Maintain a "message" for TSC at the root of the Wiki
+
**Process information
 
**Minutes & Agendas  
 
**Minutes & Agendas  
−
**TSC issue list
+
**Search capability on TSC Wiki
−
**Search capability '''' on TSC Wiki
 
 
*'''Status reports''' (central, easily found, well tracked) on:
 
*'''Status reports''' (central, easily found, well tracked) on:
−
**Ballots
+
**Working Group information and [[Work Group Health]]
−
**Projects (scope statements and status)
+
**Working Group Project Information (including scope statements and status)  
−
**Normative content
+
***weekly Update from the TSC - see archive on [http://www.hl7.org/documentcenter/index.cfm?action=dc.home&documenttype_id=23 HL7 Document Center]
 
**Architecture/Methodology Issues, etc.
 
**Architecture/Methodology Issues, etc.
 
**Search capability
 
**Search capability
 +
*[http://gforge.hl7.org/gf/project/tsc/ TSC Gforge Project]
 +
**[http://gforge.hl7.org/gf/project/tsc/tracker/?action=TrackerItemBrowse&tracker_id=313 TSC issue list]
 +
**Ballot title approvals

Latest revision as of 13:41, 16 July 2010

Communications plan for 2010

Approved ccyymmdd


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


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
    • 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)
    • Architecture/Methodology Issues, etc.
    • Search capability
  • TSC Gforge Project
Retrieved from "https://tscwiki.hl7.org/w/index.php?title=TSC_Communications_Plan_2010&oldid=6720"