ITI Change Proposals 2015

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.

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

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.

Integrated CPs 2015

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

Appoved CPs to be integrated into Version 12.0 of the Technical Framework and the 2015 version of Supplements in September 2015 are listed <tbd>

ITI docs affected by 2015 CPs

tbd

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/

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

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.

Sep 5, 2014

Fri Sep 5, 9-11am CDT

Webex link: https://himss.webex.com/himss/j.php?J=927690136&PW=NNzYzYzhlY2I0

Agenda

Current status spreadsheet is here: ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2015/CPs/Status/

(1) Ballot 24 comment review & resolution"'

• Ballot contents are here: ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2015/CPs/Ballots/ballot_24/
• Consolidated comments are in this directory. Note that it contains several change-tracked review submission for the DSG and HPD CPs: ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2015/CPs/Ballots/ballot_24/BallotCommentsReceived/

(2) Next in CPs

Sep 18, 2014

Thu Sep 18, 9-11am CDT

Webex link: tbd

Agenda

Note: agenda is draft until Sep 17 -- send your additions to Lynn

(1) Process new Incoming CPs ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2015/CPs/0_Incoming/

• CP-ITI-XDS_Changes-for-XPID.doc
• CP-ITI-XDS_FindDocumentsByReferenceID-without-patientID.doc
• CP-ITI-XDS-PatientIdentityFeedMergeType.doc
• CP-ITI-ESL_Definition_Of_Document.doc
• CP-ITI-LW-XDW-content-Vol3.doc
• CP-ITI-LF-PDOinconsistencies.doc
• others tbd...

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

• CP-ITI-790 - Explicitly Indicate Local Patient Identifier (sourcePatientID) Merges in the XDS Registry
• others tbd...

Agenda and Minutes from past CP calls

Aug-1-2014

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