ITI Change Proposals 2008

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
xds_030_06.doc	Standardizaton of XDS Documents	XDS	July 2007	Failed ballot
xds_227_01.doc	Provide list of Content Integration Profiles	XDS	July 2007	Failed ballot

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-241-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

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.

CP	Title	Profiles Affected
CP-ITI-228-03.doc	FindDocumentQuery eventCode problem	XDS

Completed CPs

CP	Title	Profiles Affected

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

• CP-ITI-264-00.doc - Allow the deletion of Documents within XDS (if ready)

Return to

• ITI Technical Committee