Difference between revisions of "2009 Publication Schedule"

From IHE Wiki
Jump to navigation Jump to search
Line 1: Line 1:
===ITI new & updated publications===
+
=== 2009 Schedule of Publication===
 +
<b>PROPOSED</b><br>
 +
<u>Last CP ballot for CPs being integrated into 2009 document</u><br>
 +
* 2009-05-22 Released
 +
* 2009-06-19 Due
 +
<u>Integration of approved CPs into TI and TF documents</u><br>
 +
* 2009-06-22 Begin
 +
* 2009-07-01 Completion for all TI being moved to FT
 +
* 2009-07-03 Completion for all TI and TF, including integrating TI becoming FT into the TF
 +
<u>Review by committee</u><br>
 +
* 2009-07-06 Begin
 +
* 2009-07-10 Due
 +
<u>Integration and resolution of commitee comments</u><br>
 +
* 2009-07-13 Begin
 +
* 2009-07-27 Complete
 +
 
 +
=== Helpful Hints for integration tasks ===
 +
<b> Integrating new Final Text profiles into Vol. 1 & 2 </b><br>
 +
For Trial Implementation (TI) profiles which are becoming Final Text (FT)for the first time in 2009 a special mechanism is used to copy and paste from the TI document to the Vol. 1 and 2 Technical Framework (TF)document.  The purpose of this mechanism is to maintain the change tracking of new CPs integrated in 2009.  The CPs are first integrated into the existing TI document.  Then the sections of the TI document are inserted into the correct parts of the Vol. 1 and Vol. 2 TF.  The process for this insertion is:
 +
# Turn OFF change tracking in the TI document (supplement)
 +
# Copy the section into the clipboard (Ctrl C or equivalent)
 +
# Turn OFF change tracking in the TF Volume
 +
# Paste the section from the clipboard
 +
# Turn change tracking back on in the TF Volume for future updates
 +
 
 +
=== Table of ITI new & updated publications schedule and status ===
 
The following table is designed for use by ITI technical committee editors, committee members, sponsors and connectathon staff for understanding the details for release of updated documents from the ITI Technical committee.  It describes:
 
The following table is designed for use by ITI technical committee editors, committee members, sponsors and connectathon staff for understanding the details for release of updated documents from the ITI Technical committee.  It describes:
 
* Document Title - the title of the document, including short acronym if appropriate. Note that some documents are listed twice in the table.  A double listing indicates that the document will be released a second time.  An explanation of the purpose of the second release is included in this column.
 
* Document Title - the title of the document, including short acronym if appropriate. Note that some documents are listed twice in the table.  A double listing indicates that the document will be released a second time.  An explanation of the purpose of the second release is included in this column.

Revision as of 10:51, 20 February 2009

2009 Schedule of Publication

PROPOSED
Last CP ballot for CPs being integrated into 2009 document

  • 2009-05-22 Released
  • 2009-06-19 Due

Integration of approved CPs into TI and TF documents

  • 2009-06-22 Begin
  • 2009-07-01 Completion for all TI being moved to FT
  • 2009-07-03 Completion for all TI and TF, including integrating TI becoming FT into the TF

Review by committee

  • 2009-07-06 Begin
  • 2009-07-10 Due

Integration and resolution of commitee comments

  • 2009-07-13 Begin
  • 2009-07-27 Complete

Helpful Hints for integration tasks

Integrating new Final Text profiles into Vol. 1 & 2
For Trial Implementation (TI) profiles which are becoming Final Text (FT)for the first time in 2009 a special mechanism is used to copy and paste from the TI document to the Vol. 1 and 2 Technical Framework (TF)document. The purpose of this mechanism is to maintain the change tracking of new CPs integrated in 2009. The CPs are first integrated into the existing TI document. Then the sections of the TI document are inserted into the correct parts of the Vol. 1 and Vol. 2 TF. The process for this insertion is:

  1. Turn OFF change tracking in the TI document (supplement)
  2. Copy the section into the clipboard (Ctrl C or equivalent)
  3. Turn OFF change tracking in the TF Volume
  4. Paste the section from the clipboard
  5. Turn change tracking back on in the TF Volume for future updates

Table of ITI new & updated publications schedule and status

The following table is designed for use by ITI technical committee editors, committee members, sponsors and connectathon staff for understanding the details for release of updated documents from the ITI Technical committee. It describes:

  • Document Title - the title of the document, including short acronym if appropriate. Note that some documents are listed twice in the table. A double listing indicates that the document will be released a second time. An explanation of the purpose of the second release is included in this column.
  • Type - the type of document: TI = Trial Implementation Supplement, FT = Final Text, TF = Technical Framework, WP = White Paper
  • Review - the date that integration of all approved CPs will be complete and the document will be released for review by the committee.
  • Release - the date that the technical committee will have completed all review and updates of the document and release it to sponsors for publication
  • Publication - the day, one week after the Release to Sponsors date, that the document will be officially published on ihe.net.
  • Status - the status of the work:
    • Done means the updated version of the document is on www.ihe.net
    • Released means that the updated version of the document has been completed by the committee and is being processed for official publication on www.ihe.net
    • Ready means that the updated version of the document has been completed by the committee and is being integrated into the Technical Framework for release as Final Text.
    • Late means that some of the dates preceding creating of the updated version of the document have been missed. The publication date may be in jeopardy.
    • On Schedule means that all the dates preceding creating of the updated version of the document have been met. The publication of the document is on schedule.
    • Unknown means that it is unknown whether the document will need to be re-released.
Document Title Type Editor Review Release Publication Status
Publish / Subscribe Infrastructure TI Vassil TBD TBD TBD TBD
Cross-Community Patient Identification TI Karen TBD TBD TBD TBD
Multi-patients query TI Ana TBD TBD TBD TBD
SOA White Paper TI Alean TBD TBD TBD TBD
Access Control White Paper TI Joerg TBD TBD TBD TBD
TF Vol 1. Version 6.0 TF TBD TBD TBD TBD TBD
TF Vol 2. Version 6.0 TF TBD TBD TBD TBD TBD