ITI Change Proposals 2020-21

This page contains the details of Change Proposal (CP) processing in the ITI domain for the 2020-21 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 folder on the IHE Google Drive. This is typically done by directly uploading the CP into the folder (if you have access); otherwise, send it an email to the ITI Technical Committee members in charge of CPs (currently Lynn Felhofer or to an ITI Technical Committee co-chair).
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 the Assigned folder. If CP is rejected it is moved to the Rejected folder and the 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 the Completed folder and old versions are moved to old_versions.
6. ITI Tech co-chair or CP manager collects Completed CPs into a ballot. The Ballots folder will be used for this.
7. Ballot is released to the general community for voting for 4 weeks
8. Votes and comments are collected. All yes votes means the CP passed ballot and moved to Final Text. 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 Final Text status and scheduled to be integrated into the Technical Framework or Supplement.
10. CP status and ballots are tracked here

Change Proposal pages from previous years

Prior years work can be accessed at:

• ITI Change Proposals 2018-19
• ITI Change Proposals 2017-18
• ITI Change Proposals 2016-17
• ITI Change Proposals 2015-16
• ITI Change Proposals 2014-15
• ITI Change Proposals 2013-14
• ITI Change Proposals 2012-13
• ITI Change Proposals 2011-12
• ITI Change Proposals 2010-11
• ITI Change Proposals 2009-10
• ITI Change Proposals 2008-09
• ITI Change Proposals 2007-08
• ITI Change Proposals 2006-07

ITI CP Tracking

Location of CPs

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

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. Its contents are approved by the Technical Committee and the CP 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 in the upcoming publication cycle.

Integrated

contains the version of the CP that was integrated into the TF, organized by year.

Rejected

CPs that have been submitted but rejected by the committee

Cancelled

contains CPs that were once assigned but have been cancelled, i.e. Cancelled status

Ballots

contains Ballots that have been released for voting by the general community, organized by year.

CP status

ITI tracks status of its Change Proposals in this google doc: https://docs.google.com/spreadsheets/d/1gdr_Y8xZBvbb326J4z67cqprxOexFgtkPj_VlD3rB9E/edit?usp=sharing The Active CPs tab contains those that are Assigned, Completed, or Final Text in this cycle. There are also archive tabs for prior years.

Approved CPs integrated into the ITI Technical Framework

CPs that have passed ballot in since 2015, and that have been, or will be, integrated into the ITI Technical Framework are listed on this Log of Approved CPs.

CPs that have already been integrated into the Technical Framework are stored here: ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance/CPs/4_Integrated/

The ITI Technical Committee integrates CPs into Technical Framework documents following this process : ITI CP Integration Process

Ballots

Ballot 54

Out for ballot: June 14 - July 17, 2019. Comments/votes resolved on the Aug 1 & 8, 2019 CP review calls.

Ballot 54 CPs are here: ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance/CPs/Ballots/2020/Ballot_54/

Comments, votes & resolution are here

CP-ITI	Title	Ballot Result
897-03	Clarify that rqmts in ITI-19 provide a baseline set, and are not mandated at all deployments	Approved
1047-02	Remove mandatory User Authentication from ITI-19	Approved w/ updates to rationale
1151-02	ATNA ITI-19 Authenticate-Node clarity – Update options in Vol 1 and 2a	Approved w/ updates
1174-01	PDQm – clarify search parameter behaviour	Approved w/ updates