PCC Change Proposals: Difference between revisions

From IHE Wiki
Jump to navigation Jump to search
← Older editNewer edit →
Tsoutherland (talk | contribs)
2,520 edits
No edit summary
Tsoutherland (talk | contribs)
2,520 edits
No edit summary
Line 1: Line 1:
__NOTOC__
__NOTOC__
== '''Submitting CPs''' ==
==Introduction==
PCC offers two options for submitting change proposals:
The PCC CP process follows the general IHE CP process described on the Change Proposal process page. The following sections give more detail on the general process for PCC participants involved in the CP process.


=== Submitting a CP in a Word Document ===
==The PCC specific CP Process ==
Using the [ftp://ftp.ihe.net/Document_templates/IHE_Change_Proposal-Template-V10.1.doc latest change proposal template] complete sections as necessary and email to co-chairs.
The following text explains what the process used by the ITI commitee in processing submitted CPs. It is consistent with the general IHE CP process and is informative only.


=== Submitting a CP on the Wiki ===
# Submission into the [ftp://ftp.ihe.net/Patient_Care_Coordination/Maintenance2009/CPs/Incoming Incoming] directory. This is typically done via an email to the PCC Technical Committee co-chair in charge of CPs (currently Tone Southerland) or by directly updating the directory if you have access to the ftp write password.
Add a new row to the table above, and give your CP a number by inserting the following into the table above:
# First consideration by the committee. If CP is accepted it is given a CP #, assigned an editor, renamed to CP-ITI-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.
  {{R | [[CP-PCC-####]] | Title | [[User:Kboone|Kboone]] | 15:08, 3 March 2008 (CST) }}
# Committee works with editor to draft the CP.  Versions are kept in Assigned directory and numbered -00, -01, -02, etc.
Where #### is the next sequential number for the CP.  The strings of ~ characters will insert your name and the current time.
# Committee decides CP is ready for ballot.  Latest version of CP is moved to Completed diretory and old versions are moved to old_versions. 
Save the updated page, and then click on the new link to your CP.  On the new CP page, insert the following text:
# Co-chair collects Completed CPs into a ballot.  The Ballot directory will be used for this.
  <b><noinclude>{{subst::</noinclude>Change Proposal Template|</b>Title|Profile|Rationale<b>|Patient Care Coordination|Unassigned}}</b>
# Ballot is released to the general community for voting
Replacing the title, profile and rationale as appropriate.  Save that page, and open it again for editing.  Upon re-editing, you will see the procedure template inserted into the new document.  Add the content to your CP and save it.
# 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.




== '''Processing CPs''' ==


=== Directory Structure on FTP ===
== Directory Structure on FTP ==
* The following directory structure is used to manage CPs that are submitted as word documents.   
* 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
** '''Assigned:''' contains CPs that have been assigned an editor and are being actively worked on by the committee, i.e. Assigned status
Line 27: Line 27:
** '''Rejected:''' CPs that have been submitted by rejected by the committee
** '''Rejected:''' CPs that have been submitted by rejected by the committee


=== Other Notes ===
=== Other Notes ===  
* Versioning of individual CPs is handled through Change Tracking in Microsoft Word - this greatly simplifies the maintenance effort for linking from our wiki CP Tracking page.
<div style="display:none;">
* When CPs are processed they will be classified into one two categories
** Changes that DO NOT affect profile behavior
** Changes that DO affect profile behavior
</div>
''Also see [[Change Proposal Process]] page.''
''Also see [[Change Proposal Process]] page.''


[[PCC_Change_Proposal_Tracking | Click here for PCC Change Proposal Tracking]]
[[PCC_Change_Proposal_Tracking | Click here for PCC Change Proposal Tracking]]

Revision as of 16:22, 29 September 2009

Introduction

The PCC CP process follows the general IHE CP process described on the Change Proposal process page. The following sections give more detail on the general process for PCC participants involved in the CP process.

The PCC specific CP Process

The following text explains what the process used by the ITI commitee in processing submitted CPs. It is consistent with the general IHE CP process and is informative only.

  1. Submission into the Incoming directory. This is typically done via an email to the PCC Technical Committee co-chair in charge of CPs (currently Tone Southerland) or by directly updating the directory if you have access to the ftp write password.
  2. First consideration by the committee. If CP is accepted it is given a CP #, assigned an editor, renamed to CP-ITI-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.
  3. Committee works with editor to draft the CP. Versions are kept in Assigned directory and numbered -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.


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

Other Notes

Also see Change Proposal Process page.

Click here for PCC Change Proposal Tracking

Retrieved from "http://wiki.ihe.net/index.php?title=PCC_Change_Proposals&oldid=37065"