ITI Change Proposals 2016

Introduction

This page contains the details of Change Proposal (CP) processing in the ITI domain for the 2015-2016 publication cycle.

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

The ITI-specific CP Process

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

1. Write a change proposal. Here is IHE's Change_Proposal_Template
2. Submit into the Incoming directory. This is typically done by directly updating the directory if you have access; otherwise send it an email to the ITI Technical Committee members in charge of CPs (currently Lynn Felhofer).
3. The new CPs are considered by the committee at periodic CP review calls. 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.
4. Committee works with editor to draft the CP. Versions are kept in Assigned directory and numbered -00, -01, -02, etc.
5. Committee decides CP is ready for ballot. Latest version of CP is moved to Completed diretory and old versions are moved to old_versions.
6. Co-chair collects Completed CPs into a ballot. The Ballot directory will be used for this.
7. Ballot is released to the general community for voting
8. 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.
9. 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 involved are:

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.

Assigned

contains CPs that have been assigned an editor and are being actively worked on by the committee, i.e. Assigned 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.

Integrated

contains the version of the CP that was integrated into the TF.

Rejected

CPs that have been submitted by rejected by the committee

Canceled

contains CPs that have been canceled, i.e. Canceled status

Ballots

contains Ballots that have been released for voting by the general community

Status

contains spreadsheets describing the status of CPs.

Change Proposal pages from previous years

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

• ITI Change Proposals 2015
• ITI Change Proposals 2014
• ITI Change Proposals 2013
• ITI Change Proposals 2012
• ITI Change Proposals 2011
• ITI Change Proposals 2010
• ITI Change Proposals 2009
• ITI Change Proposals 2008
• ITI Change Proposals 2007

ITI CP Tracking

Location of CPs, and CP status

All Change Proposal management is done on the IHE ftp site here.

Since March 2015, the ITI tracks status of its Change Proposals on the "CPs tracking" tab in this google doc: https://docs.google.com/spreadsheets/d/1gdr_Y8xZBvbb326J4z67cqprxOexFgtkPj_VlD3rB9E/edit?usp=sharing

Approved CPs to be integrated in 2016

CPs that have passed ballot in this cycle, and that will be integrated into Version 12.0 of the Technical Framework and the 2016 version of Supplements in September 2016 are listed on the "Ballot Log" tab of the tracking spreadsheet.

In Aug 2016, CPs will be integrated & checked following this process (currently draft): http://wiki.ihe.net/index.php?title=ITI_CP_Integration_Process

Ballots

Ballot 29

Out for ballot: Aug 13 - Sep 16 2015

The Ballot 29 announcement is here: https://groups.google.com/forum/#!topic/ititech/apwaveVKzqU

Ballot 29 CPs, comments, and votes are archived here: ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2016/CPs/Ballots/ballot_29/

CPs approved in this ballot are here:

Comments/votes will be reviewed reviewed on the Sep 24 CP call. Resolution is in the table below.

CP-ITI	Title	Ballot Result
559-02	MPQ profiles queries vs. Metadata Update option
801-03	Update Vol 1 references to RFC 3881
872-03	Add ATNA Repository Forwarding and re-doc ITI-20 transaction

Assigned CPs

For a list of CPs that are currently assigned see the 'CP tracking' tab in the CP status google doc. Assigned CPs are stored here: ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2016/CPs/1_Assigned/

Upcoming CP discussions

ITI CP review calls are typically held the 1st Friday and 3rd Thursday of each month from 9-11am Central US. Additional sessions may be scheduled during ITI Tech F2F meetings.

Sep-4-2015

9-11am CDT

This call is cancelled.

Sep-24-2015

Note: for this month, the third Thursday CP call is rescheduled to the fourth Thurs

9-11am CDT

Agenda

(1) Review Ballot 29 votes/comments ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2016/CPs/Ballots/ballot_29/

Agenda and Minutes from past CP calls

Aug-7-2015

Agenda and minutes are here: http://wiki.ihe.net/index.php?title=ITI_CPs_2015-08-07

Aug-24-2015

Agenda and minutes are here: http://wiki.ihe.net/index.php?title=ITI_CPs_2015-08-24