Difference between revisions of "ITI Change Proposals 2008"

From IHE Wiki
Jump to navigation Jump to search
(New page: = Introduction = See Change Proposal process page. Return to ITI Technical Committee = ITI CP Tracking = All Change Propoposal management is in [ftp://ftp.ihe.n...)
 
Line 6: Line 6:
  
 
= ITI CP Tracking =
 
= ITI CP Tracking =
All Change Propoposal management is in [ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2006-2007/CPs/ ITI CP ftp site].  The tracking spreadsheet can be accessed at [ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2006-2007/CPs/Status Status directory].  It is the file with the most recent date in that directory.
+
All Change Propoposal management is in [ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2007-2008/CPs/ ITI CP ftp site].  The tracking spreadsheet can be accessed at [ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2007-2008/CPs/Status Status] directory.  It is the file with the most recent date in that directory.
  
  
Line 48: Line 48:
 
! Reason
 
! Reason
 
|-
 
|-
| [ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2006-2007/CPs/Canceled/xds_030_06.doc xds_030_06.doc]
+
| TBD
| Standardizaton of XDS Documents
+
| TBD
| XDS
+
| TBD
| July 2007
+
| TBD
| Failed ballot
+
| TBD
|-
 
| [ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2006-2007/CPs/Canceled/xds_227_01.doc xds_227_01.doc]
 
| Provide list of Content Integration Profiles
 
| XDS
 
| July 2007
 
| Failed ballot
 
 
|-
 
|-
 
|}
 
|}
Line 70: Line 64:
 
! Profiles Affected
 
! Profiles Affected
 
|-
 
|-
| [ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2006-2007/CPs/FinalText/CP-ITI-234-FT.doc CP-ITI-234-FT.doc]
+
| [ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2007-2008/CPs/FinalText/CP-ITI-234-FT.doc CP-ITI-234-FT.doc]
 
| ATNA Maintaining a List of Certificates for Trusted Nodes/Applications
 
| ATNA Maintaining a List of Certificates for Trusted Nodes/Applications
 
| ATNA
 
| ATNA
 
|-
 
|-
| [ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2006-2007/CPs/FinalText/CP-ITI-237-FT.doc CP-ITI-237-FT.doc]
+
| [ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2007-2008/CPs/FinalText/CP-ITI-237-FT.doc CP-ITI-237-FT.doc]
 
| Submission of Association Objects
 
| Submission of Association Objects
 
| XDS
 
| XDS
 
|-
 
|-
| [ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2006-2007/CPs/FinalText/CP-ITI-241-FT.doc CP-ITI-241-FT.doc]
+
| [ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2007-2008/CPs/FinalText/CP-ITI-241a&b-FT.doc CP-ITI-241a&b-FT.doc]
 
| Document source replace support from required to optional
 
| Document source replace support from required to optional
 
| XDS
 
| XDS
 
|-
 
|-
| [ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2006-2007/CPs/FinalText/CP-ITI-249-FT.doc CP-ITI-249-FT.doc]
+
| [ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2007-2008/CPs/FinalText/CP-ITI-249-FT.doc CP-ITI-249-FT.doc]
 
| XDS Demographics
 
| XDS Demographics
 
| XDS
 
| XDS
 
|-
 
|-
| [ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2006-2007/CPs/FinalText/CP-ITI-252-FT.doc CP-ITI-252-FT.doc]
+
| [ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2007-2008/CPs/FinalText/CP-ITI-252-FT.doc CP-ITI-252-FT.doc]
 
| XDM allignment on XDS.b
 
| XDM allignment on XDS.b
 
| XDM
 
| XDM
 
|-
 
|-
| [ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2006-2007/CPs/FinalText/CP-ITI-253-FT.doc CP-ITI-253-FT.doc]
+
| [ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2007-2008/CPs/FinalText/CP-ITI-253-FT.doc CP-ITI-253-FT.doc]
 
| Option update and allignment on XDS.b
 
| Option update and allignment on XDS.b
 
| XDR
 
| XDR
Line 100: Line 94:
 
|}
 
|}
  
== Balloted CPs moved back to Assigned ==
+
 
These CPs had comments from the ballot that suggested they are not ready for final text yet.  Have been moved back to assigned status.
+
== Completed CPs ==
  
 
{| style="width:95%" border="1" cellpadding="1"
 
{| style="width:95%" border="1" cellpadding="1"
Line 108: Line 102:
 
! Profiles Affected
 
! Profiles Affected
 
|-
 
|-
| [ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2006-2007/CPs/Completed/CP-ITI-228-03.doc CP-ITI-228-03.doc]
+
| [ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2007-2008/CPs/Completed/CP-ITI-231-01.doc CP-ITI-231-01.doc]
| FindDocumentQuery eventCode problem
+
| PDQ Clarify Domains in Query
| XDS
+
| PDQ
 
|-
 
|-
|}
+
| [ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2007-2008/CPs/Completed/CP-ITI-276-00.doc CP-ITI-276-00.doc]
 
+
| XCA Audit messages contain XCA transactions names/numbers
== Completed CPs ==
+
| XCA
 
 
{| style="width:95%" border="1" cellpadding="1"
 
! CP
 
! Title
 
! Profiles Affected
 
 
|-
 
|-
 
|}
 
|}

Revision as of 12:55, 7 December 2007

Introduction

See Change Proposal process page.

Return to ITI Technical Committee

ITI CP Tracking

All Change Propoposal management is in ITI CP ftp site. The tracking spreadsheet can be accessed at Status directory. It is the file with the most recent date in that directory.


Directory Structure

Assigned
contains CPs that have been assigned an editor and are being actively worked on by the committee, i.e. Assigned status
Ballots
contains Ballots that have been released for voting by the general community
Canceled
contains CPs that have been canceled, i.e. Canceled status
Completed
contains the last version of a CP that is in Completed status. It is waiting to be put in a ballot
FinalText
contains the last version of a CP that is in FinalText status. It is has been approved by ballot and is waiting to be integrated into the TF.
FinalText/Integrated
contains the version of the CP that was integrated into the TF.
Incoming
contains CPs which have been submitted but have not been assigned a CP number or an editor. This is the place that new incoming CPs are placed prior to the first stage of processing by the committee.
old_versions
Contains old versions of Completed and FinalText CPs
Rejected
CPs that have been submitted by rejected by the committee
Status
contains spreadsheets describing the status of CPs.

Integrated CPs

These CPs have been integrated into the Version 4.0 of the Technical Framework and the 2007 version of Supplements.

CP Title Profiles Affected Date
TBD TBD TBD August 2008 (expected)

Canceled CPs

These CPs have been canceled.

CP Title Profiles Affected Date Reason
TBD TBD TBD TBD TBD

Final Text CPs

These CPs are ready for integration into the Technical Framework and Supplements.

CP Title Profiles Affected
CP-ITI-234-FT.doc ATNA Maintaining a List of Certificates for Trusted Nodes/Applications ATNA
CP-ITI-237-FT.doc Submission of Association Objects XDS
CP-ITI-241a&b-FT.doc Document source replace support from required to optional XDS
CP-ITI-249-FT.doc XDS Demographics XDS
CP-ITI-252-FT.doc XDM allignment on XDS.b XDM
CP-ITI-253-FT.doc Option update and allignment on XDS.b XDR


Completed CPs

CP Title Profiles Affected
CP-ITI-231-01.doc PDQ Clarify Domains in Query PDQ
CP-ITI-276-00.doc XCA Audit messages contain XCA transactions names/numbers XCA

The ITI specific CP Process

See CP Process for IHE specific processing.

  1. Submission into the Incoming directory
  2. First consideration by the committee. If CP is accepted it is given a CP #, assigned an editor, renamed to CP-ITI-xxx_00.doc and placed in Assigned. If CP is rejected it is moved to Rejected and submitter is informed of explanation for rejection. Likely reasons for rejection are: dublicate, merged, withdrawn or not enough information to understand the request. Rejected CPs can be resubmitted with more information for reconsideration.
  3. Committee works with editor to draft the CP. Versions are kept in Assigned directory and numbered starting with -00, -01, -02, etc.
  4. Committee decides CP is ready for ballot. Latest version of CP is moved to Completed diretory and old versions are moved to old_versions.
  5. Co-chair collects Completed CPs into a ballot. The Ballot directory will be used for this.
  6. Ballot is released to the general community for voting
  7. Votes and comments are collected. All yes votes means the CP passed ballot and moved to FinalText. No votes are resolved by the committee. Sometimes CP is withdrawn, sometimes NO voter changes to yes vote after explanations. CP may be updated in this process. If updates are insignificant (clarification only) the CP is considered passed. If updates are significant the CP is submitted for another ballot.
  8. CP approved in ballot are put in FinalText and scheduled to be integrated into the Technical Framework or Supplement.

February 13, 2008

  • CPs in Incoming directory
    • cp-iti-bill-xds_typos.doc
    • CP-ITI-bill-xds_ss_description.doc
    • cp-iti-bill-xds_doc_rel_model.doc
    • cp-iti-bill_getsscontents.doc


Return to