Introduction

The ITI Change Proposal (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.

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

All Change Proposal management is done 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.

Approved CPs to be integrated in 2015

Approved CPs to be integrated into Version 12.0 of the Technical Framework and the 2015 version of Supplements in September 2015 are listed in this spreadsheet: ITI-CPs_FinalText_2014-15.xlsx

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

Ballots

Ballot 24

Out for ballot: Aug 5 - Sep 3 2014

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

Ballot 24 is archived here: ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2015/CPs/Ballots/ballot_24/

CPs approved in this ballot are here: ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2015/CPs/3_FinalText/from_Ballot_24/

Comments/votes were reviewed on the Sep 5 CP call. Resolution is in the table below. Approved CPs are in effect for 2015 connectathons.

CP-ITI	Title	Profile / Volumes Affected	Ballot Result
352-09	Cleanup of Definition of Submission Sets	XD* / Vol 3	Approved w/ changes
412-01	DSG needs to be a Doc Content Profile	DSG / Vol 1, 3	Failed; back to Assigned
443-03	PDQv3 needs more error codes	PDQv3 / Vol 2b	Failed, reassign to Karen
529-05	Missing date comparison	XDS / Vol 2a	Approved w/ changes
562-01	XUA++ Purpose of Use example child element uses HL7v3 namespace	XUA / Vol 2b	Failed, reassign to Walco
579-02	Remove duplicate table	editorial / Vol 2a	Failed, reassign to Lynn
580-04	Clarify BOM requirements	ATNA / Vol 2a	Approved w/ changes
582-01	Dangling associations from GetAllQuery	XDS-MU / Vol 2a	Failed; back to Assigned
650-02	OASIS/ebXML Registry Ino Model Constraint or ITI TF example change	XDS, XCA, XDR, MPQ, XCF / Vol 2a, 2b	Failed; back to Assigned
666-03	Clarify rqmts for QPD segment	PDQ / Vol 2a	Approved w/ changes
716-02	Clarify MIME wrapping in DEN	DEN / Vol 2b	Approved w/ changes
738-01	Replace should deprecate other associations	XDS / Vol 3	Failed; back to Assigned
739-02	Clarification of formatCode purpose & encoding	XDS / Vol 3	Approved w/ changes
741-02	Doc Source Responsibility	XDS / Vol 1	Approved w/ changes
756-01	MPQ fixes to ensure Metadata Update compatibility	MU / Vol 2a	Failed; back to Assigned
757-03	MPQ fixes to ensure On-Demand Docs compatibility	XDS-ODD / Vol 2b	Approved w/ changes
770-02	Fix inconsistencies in references to XSPA/XACML in ITI-40	XUA / Vol 2b	Approved w/ changes
786-00	Fix typo in message type in ITI-8	XDS, PIX / Vol 2a	Approved
788-02	Clarify ability to replace stable doc w/ ODD & vice versa	XDS / Vol 2b	Approved w/ changes
789-02	Move Basic Subset rqmt out of option section in PAM Vol 1	PAM / Vol 1	Approved w/ changes
792-05	Add Federation Option to HPD	HPD / Vol 1,2b	Approved w/ changes

Ballot 25

Out for ballot: Nov 13 - Dec 12, 2014

Ballot 25 and votes are archived here: ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2015/CPs/Ballots/ballot_25/

CPs approved in this ballot are here: ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2015/CPs/3_FinalText/from_Ballot_25/

Comments/votes were reviewed on the Dec 18 CP call. Resolution is in the table below.

CP-ITI	Title	Profile / Volumes Affected	Ballot Result
443-04	PDQv3 needs more Error Codes		failed; back to Assigned
579-04	Remove duplicate table and move to message semantics	PDQ, XDS / Vol 2a	Approved w/ updates
630-05	XTN data type should be more specific	XD* / Vol 3	Approved
650-05	OASIS/ebXML Registry Information Model constraint or IHE ITI TF Example change		Approved w/ update
672-06	replyTo and mustUnderstand		Approved
796-00	Conformance typo	editorial / Vol 3	Approved
797-03	Definition of Document		Failed; back to Assigned; one portion split into 830; see below
798-00	Move XDW content out of Vol3 until XDW becomes FT	Vol 3, XDW-TI	Approved
800-04	Resource Naming	CSD-TI	Approved w/ updates
802-03	Fix mislabeled transactions in Vol 1 diagram		Approved w/ updates
805-03	Document Uniqueness Validation		Approved w/ updates
807-01	Audit for synchronous webservices	many / Vol 2a & 2b, TI: XCPD, DSUB, MU, SeR	Approved
813-00	Fix missing editorial change in XDW supplement	XDW / XDW-TI	Approved
830-00	Clarify rqmts for DocumentEntry.uniqueId attribute	XD* / Vol 3	Approved (from 797 above)

Assigned CPs

For a list of CPs that are currently assigned see the latest CP-ITI-Tracking-201x-nn-nn.xls file in the Status directory. Assigned CPs are here: ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2015/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.

ITI F2F Feb-23-27-2015

This section covers CP discussions during the Feb ITI F2F meeting in Paris. Agenda & call-in details for that meeting are here: http://wiki.ihe.net/index.php?title=ITI_Agenda_2014-2015#Agenda_February_2015.2C_Face_to_Face

The current status spreadsheet dated 2015-01-15 is here: ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2015/CPs/Status/

Agenda

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

DSUB CPs:
- CP-ITI-613 - Make Patient ID an optional parameter in Subscription Filter (Mauro)
Other CPs ready for discussion
- CP-ITI-TBD

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

CP-ITI_XCPD_Health_Data_Locator_Diagram_Correction.doc
CP-ITI-PIXV3_removed_unexpected_lines.docx
CP-ITI-RAM_DSUB_audit_chgs.doc
CP-ITI-RAM-XCF_audit_chgs.doc
CP-ITI-RAM-ClarificationRequest_XPID.docx
CP-ITI-RAM-SVSauditMsg.doc

(3) Next in CPs

Ballot 26 planning
- mmm-dd-2015 - All CPs due to Lynn
- mmm-dd-2015 - Lynn gives CP Ballot and announcement to Nancy
- mmm-dd-2015 - Nancy distributes Ballot 26
- mmm-dd-2015 - Ballot 26 announcement
- mmm-dd-2015 - Ballot 26 comments due
- Discussion of CP Ballot 26

Next CP call is...

Minutes Feb 24, 2015

(1) Assigned CPs discussion outcomes
- CP-ITI-613-02 that affects DSUB supplement has been revised by the ITI Tech committee. That CP is considered relevant because introduces new functionalities (subscription for multiple patients) that could bring up Privacy issues. The CP does not break on-field implementations because is structured identifying a new Option. Primary use-cases are related to XDW, but the changes introduced are not focused just on XDW, so it was suggested to identify other use-cases of interest. From the privacy point of view the CP does not introduce new challenges, however privacy issues already identified in Security Considerations section are amplified using the new subscription approach. It was suggested to add an analysis related to the new functionality in the Security Considerations section.

Minutes Feb 27, 2015

TBD

March-6-2015

Fri March 6, 9-11 CST

Agenda

(1) Assigned CPs ready for review ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2015/CPs/1_Assigned/

CP-ITI-790-02 - XPID Local Merge (Karen)
- Needs review by XPID implementors (is Vol 1 material clear? is transaction implementable?), HL7 messaging experts (is specification of HL7v2.5 messaging content correct?), XDS MU experts (to verify correct specification of the use of metadata versioning in reflecting the changes to metadata resulting from this new transaction)
others TBD...