ITI Change Proposals 2011

Introduction

The ITI 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. Submission into the Incoming directory. This is typically done via an email to the ITI Technical Committee co-chair in charge of CPs (currently Rob Horn) or by directly updating the directory.
2. First consideration by the committee. 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.
3. Committee works with editor to draft the CP. Versions are kept in Assigned directory and numbered -00, -01, -02, etc.
4. Committee decides CP is ready for ballot. Latest version of CP is moved to Completed diretory and old versions are moved to old_versions.
5. Co-chair collects Completed CPs into a ballot. The Ballot directory will be used for this.
6. Ballot is released to the general community for voting
7. 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.
8. 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 invoved are:

Assigned

contains CPs that have been assigned an editor and are being actively worked on by the committee, i.e. Assigned status

Ballots

contains Ballots that have been released for voting by the general community

Canceled

contains CPs that have been canceled, i.e. Canceled 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.

FinalText/Integrated

contains the version of the CP that was integrated into the TF.

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.

old_versions

Contains old versions of Completed and FinalText CPs

Rejected

CPs that have been submitted by rejected by the committee

Status

contains spreadsheets describing the status of CPs.

Archived Change Proposal pages

Ongoing work on CPs is placed on the current year CP page. Prior years work can be accessed at:

• ITI Change Proposals 2010
• ITI Change Proposals 2009
• ITI Change Proposals 2008
• ITI Change Proposals 2007

ITI CP Tracking

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

Assigned CPs

CP assignment

For a list of CPs as they are currently assigned see the latest CP-ITI-Tracking-2010-nn-nn.xls file in the Status directory.

Agenda and Minutes from CP discussions

April 8, 2011 (Minutes)

0900h Central

Agenda

• Discussion of PIX/PDQ HL7v3 CPs
  • CP-ITI-505
  • CP-ITI-506
  • CP-ITI-454
• CPs ready for discussion
  • CP-ITI-569-01
  • CP-ITI-573-00
  • CP-ITI-547-01
• New CPs
  • CP-ITI-Forcare-XDSAssociationStatus-default-not-consistent.doc
  • CP-ITI-BM-MPQ-Update [1]
  • CP-ITI-Forecase-DSUBCorrectionForEvenIDInAuditMessage [2]
  • CP-ITI-Forcare-DSUBCorrectionForHomeCommunityIDInAuditMessage [3]
  • CP-ITI-MetadataUpdate-GetAllQueryShouldNotReturnDanglingAssocs [4]
  • CP-ITI-Forcare-XDSb-GetAllQueryIincludesXDSSubmissionSetStatusWhichIsIrrelevan [5]
  • CP-ITI-KW-XCA-section-reference-error [6]
  • CP-ITI-KW-MU-Delete-audit-msg [7]
• Other Business
  • CP-ITI-578-00
  • CP-ITI-577-00

March 11, 2011 (Minutes)

0900h Central

Agenda

• CPs ready for discussion
  • CP-ITI-545 (Bill and Sondra confirm this can be cancelled. Solution is by suitable affinity domain value set for healthcareFacilityCode)
  • CP-ITI-567-01
  • CP-ITI-376
  • CP-iti-454
  • CP-ITI-455
  • CP-ITI-505
  • CP-ITI-506
  • CP-ITI-539
• New CPs
  • CP-ITI-KW-cardinality-of-sourcePatientId [8]
  • CP-ITI-SMM-clarify-BOM-rqts [9]
  • CP-ITI-MM-wrong-number-or-wrong-content-for-table-3.8-4 [10]
  • CP-ITI-KW-Merge-Supplement [11]
  • CP-ITI-KW-XCA-patientid-translation [12]
  • CP-ITI-KW-HPD-Optionality-Organization [13]
  • CP-ITI-Forcare-MetadataUpdateShouldSpecifyAuditForDelete [14]
  • CP-ITI-BM-Merge-Supplement [15]
• Information
  • Radiology committee is working on their upgrade CP for HL7 V2.3.1 transition to V2.5. As part of that they are discussing ITI CP-211. (Same time as this tcon.)

February 4, 2011 (Minutes)

0830h Central

Agenda

• CPs ready for discussion
• New CPs
  • CP-ITI-BB-MU-applied-to-MQP [16]
  • cp-iti-bill-xfrm_submission [17]
  • CP-ITI-Forcare-XUApp-PurposeOfUse-example-corrected [18]
  • CP-ITI-HS-MSH21-ProfileID [19]
  • CP-ITI-HS-MSHfieldDelimiters [20]
  • CP-ITI-KW-HPD-AttriNameWrong [21]
  • CP-ITI-KW-HPD-typos-in-attributenames [22]
  • CP-ITI-KW-XCA-homeCommunitryID [23]
  • CP-ITI-LF-HPD-ISO-reference [24]
  • CP-ITI-LF-RFD-Archive-Form [25]
  • CP-ITI-sourcePatientId_shall_not_be_altered_through_versioning [26]
  • CP-ITI-SR-SVS-valueSetOid-attributename [27]
  • CP-ITI-TD-XDS-SD-CDATA-Req [28]
  • CP-ITI-VP-Typo-in-XCPD-example [29]
  • CP-ITI-VP_RFD_Remove_Xforms_Option [30]
  • Question on the intended recipient XON/XCN/XTN (email discussion, CP missing?)
• Next Ballot List
  • 555
  • 556-01 (use ftp, not incoming)
  • 557-00 (use ftp, not incoming)
  • 558
  • 561
  • 563
  • 564
  • 565
  • 566
  • 568
  • 571
  • 572