Revision as of 13:44, 9 September 2011

Introduction

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

Current Change Proposals are in FTP site Change Proposal directory. The tracking spreadsheet can be accessed at FTP CP status directory. It is the file with the most recent date in that directory.

CPs from earlier years may be found in:

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.

See CP Process for IHE specific processing.

Submission into the Incoming directory
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.
Committee works with editor to draft the CP. Versions are kept in Assigned directory and numbered starting with -00, -01, -02, etc.
Committee decides CP is ready for ballot. Latest version of CP is moved to Completed diretory and old versions are moved to old_versions.
Co-chair collects Completed CPs into a ballot. The Ballot directory will be used for this.
Ballot is released to the general community for voting
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.
CP approved in ballot are put in FinalText and scheduled to be integrated into the Technical Framework or Supplement.

@@ Line 9: / Line 9: @@
 = PCD CP Tracking =
 Current Change Proposals are in [ftp://iheyr2@{{SERVERNAME}}/Patient_Care_Devices/TF_Maintenance-2010-2011/CPs FTP site Change Proposal directory].  The tracking spreadsheet can be accessed at [ftp://iheyr2@{{SERVERNAME}}/Patient_Care_Devices/TF_Maintenance-2010-2011/CPs/Status FTP CP status directory].  It is the file with the most recent date in that directory.
+CPs from earlier years may be found in:
+*[ftp://iheyr2@{{SERVERNAME}}/Patient_Care_Devices/TF_Maintenance-2009-2010/CPs 2009-2010 CP directory]
+*[ftp://iheyr2@{{SERVERNAME}}/Patient_Care_Devices/TF_Maintenance-2008-2009/CPs 2008-2009 CP directory]