PCD Change Proposals

From IHE Wiki
Jump to: navigation, search


See Change Proposal process page and PCD Change Proposal List.

PCD procedures are based on corresponding ITI ones. CP Balloting follows PCD voting rules described in PCD Process.

Return to PCD Technical Committee

PCD CP Tracking

Current and Past Change Proposals are listed in http://wiki.ihe.net/index.php?title=PCD_CP_grid. The tracking spreadsheet will provide links to the CPs on the ftp site.

Directory Structure

contains CPs that have been assigned an editor and are being actively worked on by the committee, i.e. Assigned status
contains Ballots that have been released for voting by the general community
contains CPs that have been canceled, i.e. Canceled status
contains the last version of a CP that is in Completed status. It is waiting to be put in a ballot
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.
contains the version of the CP that was integrated into the TF.
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.
Contains old versions of Completed and FinalText CPs
CPs that have been submitted by rejected by the committee
contains spreadsheets describing the status of CPs.

The PCD 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-PCD-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: duplicate, 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 aresignificant 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.


Return to PCD Technical Committee