PCD Change Proposals 2009-2010

From IHE Wiki
Jump to: navigation, search

Introduction

Italics represent areas for specific attentions

The PCD 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 PCD participants involved in the CP process.

The PCD specific CP Process

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

  1. Submission into the [1] directory. This is typically done via an email to the Technical Committee co-chair in charge of CPs 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-xxx-00.doc and placed in the table as Assigned status. If the 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 Cirectory 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 note - the CP process differs - it requires public comment
  7. Votes and comments are collected. If the CP vote is "Yes" to approve the CP, the CP is moved to FinalText. "No" votes are resolved by the committee. Sometimes a CP is withdrawn, sometimes a NO vote is changed to a YES vote after explanations. The 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 the ballot are put in FinalText and scheduled to be integrated into the Technical Framework or Supplement.

Directory Structure

As CPs are processed through various statuses they move from one directory to another. would we use a single page/table? The directories are:

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.

Archived Change Proposal pages

ITI examples Ongoing work on CPs is placed on the current year CP page. Prior years work can be accessed at:

do we want a single page per year or a page with multiple years at least until the volume is much higher?

ITI CP Tracking

ITI examples All Change Proposal management is in CP ftp site. The tracking spreadsheet can be accessed at Status directory. It is the file with the most recent date in that directory.

Integrated CPs

ITI examples These CPs have been integrated into the Version 5.0 of the Technical Framework and the 2008 version of Supplements.

CP Title Profiles Affected Date
TBD TBD TBD TBD


Final Text CPs

These CPs are ready for integration into the Technical Framework and Supplements.

the following are some of the ITI CPs as examples

CP Title Profiles Affected
259 parentDocumentRelationship (parentDocumentId) is unclear XDS
296 Improve Submission Set Description XDS
316 Clarify Method to Uniquely Identify AuthorInstitutions in Registry Stored Query Response XDS
318 Query Example Typo XDS.a
359 XDS document relations in a single submission set XDS
363 Web Services Parameter Nomenclature Appendix V
Many


Completed CPs

ITI examples

Ballot 1 CPs

Note: All CPs passed ballot and are reflected in the Final Text table. Several ITI items are included FYI

CP Title Profiles Affected
296 Improve Submission Set Description XDS
318 Query Example Typo XDS.a
359 XDS document relations in a single submission set XDS
379 Profile dependencies (grouping) inconsistencies Many

Ballot 2 CPs

ITI examples

CP Title Profiles Affected

Assigned CPs

CPs to be addressed in whitepaper or supplement

ITI examples

CP assignment

ITI example

For a list of CPs as they are currently assigned see the latest CP-ITI-Tracking-2009-nn-nn.xls file in the Status directory.

Agenda and Minutes from CP discussions

Examples from ITI

October 9, 2009

Agenda

TBD

Minutes

TBD

September 11, 2009

Agenda

TBD

Minutes

TBD

August 14, 2009

Agenda

  • Teddy, Karen, Walco
    • 420 - Teddy, Karen, Walco to produce a version for review
  • Jim
    • 377 - Jim to produce a version for review
  • Vassil
    • 376 - Vassil to produce a version for review
  • John
    • 398 - John to produce a version for review
    • 406 - John to do a little research and possibly produce a version for review
    • 415 - John to produce a version for review
  • Mark
    • 403-00 - Review
    • 418-00 - Review
    • 419-00 - Review
  • Karen
    • 434 - Karen to produce a version for review
    • 444 - Karen to produce a version for review
  • Rob
    • 427 - consider if this should be addressed in ITI-42
    • 428 - consider if this should be addressed in XDS.b
    • 429 - John will review
  • Lynn
    • 441 - Lynn to produce a version for review
  • Incoming
    • CP-ITI-SMM-BPPC_clarify_transaction_numbers_and_options.doc - Lynn to update status

Minutes

TBD