ITI Change Proposals 2009

From IHE Wiki
Revision as of 16:05, 5 January 2009 by Witting (talk | contribs) (→Agenda)
Jump to navigation Jump to search

Introduction

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

The ITI 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 ITI Technical Committee co-chair in charge of CPs (currently Karen Witting) 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 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

As CPs are processed through various statuses they move from one directory to another. The directories invoved 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.


ITI CP Tracking

All Change Propoposal management is in ITI 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

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

Canceled CPs

These CPs have been canceled.

CP Title Profiles Affected Date Reason
TBD TBD TBD TBD TBD

Final Text CPs

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

CP Title Profiles Affected
TBD TBD TBD

Completed CPs

Ballot 1 CPs

CP Title Profiles Affected
TBD TBD TBD

Assigned CPs

CP's waiting for Ballot

CP's to be addressed in whitepaper/supplement

Organized by technical area

Agenda and Minutes from CP discussions

January 22, 2009

Agenda

Goal, prepare CPs for ballot in February 2009

  • CPs ready to review
    • CP-ITI-379-00.doc Lynn: Profile dependencies (grouping) inconsistencies
    • CP-ITI-380-00.doc Lynn: BPPC Patient Patient Privacy Enforcement option is missing for the Integ. Doc Source / Rep actor
    • CP-ITI-381-01.doc Karen: homeCommunityId needs definitition in metadata tables
    • CP-ITI-388-00.doc Karen: Unclear what error should result when Retrieve Document Set specifies an unknown uniqueID
    • CP-ITI-390-01.doc Lynn: Document Registry is mentioned in PDO, but no rqmts in Vol 1 material
    • CP-ITI-393-00.doc George: Extend the support for encodedResponse to the HTTP Get and HTTP Post transport methods
    • CP-ITI-394-00.doc John: XCA and XDS.b ATNA Logging Enhancements
  • CPs waiting for Ballot
  • incoming
    • CPs ready for ballot
    • CP Forcare PDQ PIX Acknowledgment Code Inconsistency
    • CP_ITI_DSG_Folder_DSG
    • CP_ITI_NAV_folder
    • cp-iti-bill-rep_return_size_hash
    • CP-ITI-JFM_BPPC_Clarrification_of_terms
    • CP-ITI-JFM_CT_SNTP
    • CP-ITI-JFM_DSG_title_page
    • CP-ITI-JMG_Extend_the_use_of_encodedResponse
    • IHE_Change_Proposal-XUA
    • ITI_LF_PDO-last_upd_datetime_v3

Minutes



January 9, 2009

Agenda

TBD

Minutes



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