Revision as of 14:35, 29 July 2014

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.

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

**This ballot is under construction until Aug 1**

Balloted in Aug 5 - Sep 3 2014

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

CP-ITI	Title	Profile / Volumes Affected
532-08	Clean up definition of submission set	XDS / Vol 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 associates 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
770-01	Fix inconsistencies in references to XSPA/XACML in ITI-40	XUA / Vol 2b
786	Fix typo in message type in ITI-8	XDS, PIX / Vol 2a
788	Clarify ability to replace stable doc w/ ODD & vice versa	XDS / Vol 2b
789	Move Basic Subset rqmt out of option section in PAM Vol 1	PAM / Vol 1

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.

Aug 1, 2014

Fri Aug 1, 9-11am CDT

Agenda

this agenda is draft until July 31

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

(1) Ballot 24 preparation

CP-ITI-791 - Update MHD for FHIR (John M)
CP-ITI-412 - DSG needs to be a Doc Content Profile (John M)
CP-ITI-792 - Add Federation Option to HPD (Karen)
Summary of Ballot 24 content (Lynn)
Ballot 24 timeline
- Aug 4 - Lynn gives ballot content to Sponsors
- Aug 5 - Sponsors distribute CP ballot
- Sep 3 - Ballot comments due
- Sep 5 - CP Processing call to review ballot comments

(2) Process 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
more tbd...

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

CP-ITI-634 - Clarify error vs warning for all error codes (Rob)
CP-ITI-594-01 - Clarify formats Allowed for uniqueId in XD* meta-Data
more tbd...'

Agenda and Minutes from past CP calls

@@ Line 56: / Line 56: @@
 === Ballot 24 ===
-''This ballot is under construction until Aug 1''
+''**This ballot is under construction until Aug 1**''
 Balloted in Aug 5 - Sep 3 2014

Difference between revisions of "ITI Change Proposals 2015"