ITI Change Proposals 2022-2023

From IHE Wiki
Jump to navigation Jump to search

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

  1. Write a change proposal. Here is IHE's Change Proposal Template.
  2. Submit into the Incoming folder on the IHE Google Drive. This is typically done by directly uploading the CP into the folder (if you have access); otherwise, send it an email to the ITI Technical Committee members in charge of CPs (currently Sarah Bell or to an ITI Technical Committee co-chair).
  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 the Assigned folder. If CP is rejected it is moved to the Rejected folder and the 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 the Completed folder and old versions are moved to old_versions.
  6. ITI Tech co-chair or CP manager collects Completed CPs into a ballot. The Ballots folder will be used for this.
  7. Ballot is released to the general community for voting for 4 weeks
  8. Votes and comments are collected. All yes votes means the CP passed ballot and moved to Final Text. 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 Final Text status and scheduled to be integrated into the Technical Framework or Supplement.
  1. CP status and ballots are tracked here

Change Proposal pages from previous years

Prior years work can be accessed at:

ITI CP Tracking

Location of CPs

All Change Proposal management is done on the IHE Documents on Google Drive here.

As CPs are processed through various statuses they move from one folder to another. The directories involved are:

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.
contains CPs that have been assigned an editor and are being actively worked on by the committee, i.e. Assigned status
contains the last version of a CP that is in Completed status. Its contents are approved by the Technical Committee and the CP is waiting to be put in a ballot.
Final Text
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 in the upcoming publication cycle.
contains the version of the CP that was integrated into the TF, organized by year.
CPs that have been submitted but rejected by the committee
contains CPs that were once assigned but have been cancelled, i.e. Cancelled status
contains Ballots that have been released for voting by the general community, organized by year.

CP status

ITI tracks status of its Change Proposals in this google doc: The Active CPs tab contains those that are Assigned, Completed, or Final Text in this cycle. There are also archive tabs for prior years.

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 ITI Technical Framework are listed on this Log of Approved CPs.

CPs that have already been integrated into the Technical Framework are stored here.

The ITI Technical Committee integrates CPs into Technical Framework documents following this process : ITI CP Integration Process


Ballot 62

Out for ballot: April 27, 2023. Comments due: May 31, 2023. Comments/votes resolution: June 13, 2023

Ballot 62 CPs are on Google Drive under IHE Documents here.

CP-ITI Title Ballot Result
793-05 Allow a FindDocumentsByReferenceId Query Without XDSDocumentEntry.patientID Approved with updates
959-01 PDQ PatientId Audit Approved
1150-02 Clarify specification Clarify handling of partial dates in queries Approved
1219-03 XCDR: Clarify error handling Approved with updates
1226-04 XDR/XCDR: Clarify “without any context” Approved
1227-03 XCDR: Clarify homeCommunityId formatting and forwarding requirements Approved
1254-02 Date handling inconsistencies in lookup transactions Approved with updates
1271-02 XCA: Add Delayed Document Assembly Option; clarify “on-demand” Approved
1272-04 XDS: Clarify creationTime for Delayed Document Assembly Approved
1277-02 XDS service time definitions are too restrictive for CDA Approved with Updates
1283-00 FHIR Profile Canonical URI as a FormatCode Approved
1289-00 XDR Remove Text Forbidding Validation Approved

Ballot 61

Out for ballot: August 16, 2022. Comments due: Friday, September 16, 2022. Comments/votes resolution: Tuesday, October 4th @ 10amCT during October vF2F.

Ballot 61 CPs are on Google Drive under IHE Documents here.

CP-ITI Title Ballot Result
1014-03 Fix XCDR Auditing Specifiation Approved with Updates
1226-02 XDR/XCDR: Clarify “without any context” Failed ballot
1252-03 Clarify use of LID Attribute in ITI-41 Transaction Approved
1260-03 ITI-18 – clarify that datetime parameter values can have single quotes Approved
1269-03 XDS: Clarify DocumentEntry.uniqueId encoding for URIs Approved
1273-03 Move guidance on service dates for On demand Approved
1274-00 RMD: Clarify conditions for metadata removal for Doc Registry in ITI-62 Approved
1275-01 Align Metadata Update with Restricted Metadata Update in context of CP-ITI-1190 Approved
1278-01 Delayed Document Assembly – hash and size inconsistency Approved with Updates
1279-00 ITI-19 updates to remove mention of User Authentication and add generic roles Approved pending Updates
1280-00 Clarify implication of grouping with ATNA Secure Node/Application Approved pending Updates
1282-00 XDS-MU - Fix Section Reference Approved

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.

Strategies for smarter CP processing (from Jul-17 F2F)

We often have CPs that need a lot of rework after ballot:

  • There is not enough review prior to ballot
  • Perhaps too much effort on specificity vs remaining silent
  • Look for opportunities to suggest that a small subset take a time-consuming or editorial problem offline and come back to the group with an updated change.

Gateway questions prior to accepting a CP (or finishing work on an existing CP):

  • Is solving the problem necessary for interoperability?
  • Has an implementer reported this problem, or should they, or... is this theoretical?
  • Is the text inconsistent? If so, are we over-specifying, i.e. can we delete the inconsistency?
  • Strongly suggest that a submitter propose a solution.
  • Is this a problem that needs to be fixed?

Upcoming CP discussions

ITI CP review calls are typically held the second Tuesday of each month from 9-10am Central US. Changes to the 'traditional' schedule for CP calls are announced on the ititech email list.

December 12, 2023

Date/Time: Tuesday, December 12 @ 9:00am CT

Teams Info: Join here

Meeting ID: 225 786 389 138

Passcode: xeDyHt


The ITI CP tracking spreadsheet is here.

(1) Process Incoming CPs

(2) Assigned CPs ready for discussion

  • CP-ITI-1288-02 (Martin S.)

(3) Next in CPs

  • Next CP Call - Tuesday, January 9th @ 9:00 am CT

Minutes from past CP calls

See ITI CPs Agenda and Minutes from past CP calls