Introduction

This page contains the details of Change Proposal (CP) processing in the ITI domain for the 2016-17 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.

Write a change proposal. Here is IHE's Change Proposal Template
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).
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.
Committee works with editor to draft the CP. Versions are kept in Assigned directory and numbered -00, -01, -02, etc.
Committee decides CP is ready for ballot. Latest version of CP is moved to Completed diretory and old versions are moved to old_versions.
Co-chair collects Completed CPs into a ballot. The Ballot directory will be used for this.
Ballot is released to the general community for voting for 4 weeks
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.

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 CP Tracking

Location of CPs, and CP status

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

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 integrated into the ITI Technical Framework

CPs that have passed ballot in since 2015, and that have been, or will be, integrated into the TIT Technical Framework are listed on the "Ballot Log" tab of the tracking spreadsheet.

In Aug 2016, CPs will be integrated & checked following this process (currently draft): ITI CP Integration Process

Ballots

Ballot 36

tbd...

Assigned CPs

For a list of CPs that are currently assigned see the 'Active CPs' 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. Changes to the 'traditional' schedule for CP calls is announced on the ititech email list.

Aug-18-2017

Webex link: https://himss.webex.com/himss/j.php?MTID=m0d26b9c56e594b0b040cf093162821ac

Meeting number: 921 693 534

Password: Meeting1

See current CP status spreadsheet here.

(1) Assigned CPs for discussion ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance/CPs/1_Assigned/

...tbd..

(2) Review of new Incoming CPs ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance/CPs/0_Incoming/

CP-ITI-ESL_Effects_of_Merge_on_Relationship_Associates.doc
CP-ITI-ESL_SoapActionRequired_Mandatory.doc
CP-ITI-ESL_XCDR-XDR_Cleanup.doc
CP-ITI-IsSnapshot-UML.doc
CP-ITI-KM_MU_AddMetadataParamFindDocsByRefId.doc
...more tbd...

(3) Next in CPs

ballot 36 timing
...other...

Agenda and Minutes from past CP calls

See: http://wiki.ihe.net/index.php/ITI_CPs_2016-17-Agenda_and_Minutes_from_past_CP_calls

ITI Change Proposals 2017

Contents