Difference between revisions of "PCC Change Proposals"
Jump to navigation
Jump to search
Tsoutherland (talk | contribs) |
JohnMoehrke (talk | contribs) |
||
| (25 intermediate revisions by 7 users not shown) | |||
| Line 1: | Line 1: | ||
__NOTOC__ | __NOTOC__ | ||
| − | == | + | ==='''Important Links'''=== |
| − | The PCC CP process follows the general IHE CP process described on the Change Proposal process page. | + | * [[Change Proposal Process | IHE Change Proposal Process]] |
| + | * [https://docs.google.com/spreadsheets/d/1kUNTaDr8ePjhWdT5L-FkCVnEeINj0RRij63S9A9LArs/edit?usp=sharing IHE PCC Change Proposal Google Sheet] | ||
| + | * [[PCC_CP_Meeting_Notes | Meeting Notes from PCC calls]] | ||
| + | * [[PCC Change Proposal Integration Process | PCC CP Integration Process]] | ||
| + | * ''Archived'' [[PCC_Change_Proposal_Master_List | PCC Change Proposal Master List]] | ||
| + | * ''Archived'' [[PCC_Historical_Change_Proposal_Tracking | PCC Historical Change Proposal Tracking]] | ||
| + | |||
| + | ==Overview== | ||
| + | The PCC CP process follows the general IHE CP process as described on the [http://wiki.ihe.net/index.php/Category:CPs Change Proposal process page]. In addition, PCC follows the specific guidance provided below. Beginning in 2017 the committee moved away from using the wiki to manage CPs and now uses a Google Sheet that is linked above. | ||
==The PCC specific CP Process == | ==The PCC specific CP Process == | ||
| − | The following text explains what the process used by the ITI | + | The following text explains what the process used by the ITI committee in processing submitted CPs. It is consistent with the general IHE CP process and is informative only. |
| − | # Submission into the [ | + | # Submission into the [https://drive.google.com/drive/folders/1H6Jdd-UnDuBI30DffCD4TvtKsurkFn-W Google Drive - 0_Submitted (Incoming)/] folder. This is typically done via an email to the individual(s) in charge of CPs (currently Michael Clifton) or by directly updating the directory if you have access to the ftp write password. If you do not have the individuals emails you may post/send to [mailto:pcctech@googlegroups.com pcctech@googlegroups.com]. |
| − | # First consideration by the committee. If CP is accepted it is given a CP #, assigned an editor, renamed to CP- | + | # First consideration by the committee. If CP is accepted it is given a CP #, assigned an editor, renamed to CP-PCC-xxxx-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. |
| + | # CP numbering is managed in the [https://docs.google.com/spreadsheets/d/1kUNTaDr8ePjhWdT5L-FkCVnEeINj0RRij63S9A9LArs/edit?usp=sharing IHE PCC Change Proposal Google Sheet]. | ||
# Committee works with editor to draft the CP. Versions are kept in Assigned directory and numbered -00, -01, -02, etc. | # Committee works with editor to draft the CP. Versions are kept in Assigned directory and numbered -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. | # 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. | + | # Co-chair collects Completed CPs into a ballot. The [https://docs.google.com/spreadsheets/d/1kUNTaDr8ePjhWdT5L-FkCVnEeINj0RRij63S9A9LArs/edit#gid=0 Ballot directory] will be used for this. |
# Ballot is released to the general community for voting | # 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 are significant the CP is submitted for another ballot. | # 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. | ||
# CP approved in ballot are put in FinalText and scheduled to be integrated into the Technical Framework or Supplement. | # CP approved in ballot are put in FinalText and scheduled to be integrated into the Technical Framework or Supplement. | ||
| − | |||
| − | |||
== Directory Structure on FTP == | == Directory Structure on FTP == | ||
| Line 23: | Line 30: | ||
** '''Cancelled:''' contains CPs that have been cancelled | ** '''Cancelled:''' contains CPs that have been cancelled | ||
** '''Completed:''' contains the last version of a CP that is in Completed status. It is waiting to be put in a ballot | ** '''Completed:''' contains the last version of a CP that is in Completed status. It is waiting to be put in a ballot | ||
| − | ** ''' | + | ** '''Submitted''' (old CP tracking term 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. |
** '''Incorporated:''' contains the version of the CP that was integrated into the TF. | ** '''Incorporated:''' contains the version of the CP that was integrated into the TF. | ||
** '''Rejected:''' CPs that have been submitted by rejected by the committee | ** '''Rejected:''' CPs that have been submitted by rejected by the committee | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
Latest revision as of 13:17, 28 January 2022
Important Links
- IHE Change Proposal Process
- IHE PCC Change Proposal Google Sheet
- Meeting Notes from PCC calls
- PCC CP Integration Process
- Archived PCC Change Proposal Master List
- Archived PCC Historical Change Proposal Tracking
Overview
The PCC CP process follows the general IHE CP process as described on the Change Proposal process page. In addition, PCC follows the specific guidance provided below. Beginning in 2017 the committee moved away from using the wiki to manage CPs and now uses a Google Sheet that is linked above.
The PCC specific CP Process
The following text explains what the process used by the ITI committee in processing submitted CPs. It is consistent with the general IHE CP process and is informative only.
- Submission into the Google Drive - 0_Submitted (Incoming)/ folder. This is typically done via an email to the individual(s) in charge of CPs (currently Michael Clifton) or by directly updating the directory if you have access to the ftp write password. If you do not have the individuals emails you may post/send to pcctech@googlegroups.com.
- First consideration by the committee. If CP is accepted it is given a CP #, assigned an editor, renamed to CP-PCC-xxxx-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.
- CP numbering is managed in the IHE PCC Change Proposal Google Sheet.
- Committee works with editor to draft the CP. Versions are kept in Assigned directory and numbered -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 are significant 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.
Directory Structure on FTP
- The following directory structure is used to manage CPs that are submitted as word documents.
- 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
- Cancelled: contains CPs that have been cancelled
- Completed: contains the last version of a CP that is in Completed status. It is waiting to be put in a ballot
- Submitted (old CP tracking term 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.
- Incorporated: contains the version of the CP that was integrated into the TF.
- Rejected: CPs that have been submitted by rejected by the committee