ITI Change Proposals 2017

Introduction

This page contains the details of Change Proposal (CP) processing in the ITI domain for the 2016-17 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 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 for 4 weeks
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.
10. CP status and ballots are tracked here

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. Its contents are approved by the Technical Committee and the CP 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 but rejected by the committee

Canceled

contains CPs that were once assigned bu have been canceled, i.e. Canceled status

Ballots

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

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 2016
• ITI Change Proposals 2015
• 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

Location of CPs, and CP status

All Change Proposal management is done on the IHE ftp site here.

ITI tracks status of its Change Proposals on the "CPs tracking" tab in this google doc: https://docs.google.com/spreadsheets/d/1gdr_Y8xZBvbb326J4z67cqprxOexFgtkPj_VlD3rB9E/edit?usp=sharing

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 the "Ballot Log" tab of the tracking spreadsheet.

CPs that have already been integrated into the Technical Framework are stored here: ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance/CPs/4_Integrated/

In Aug 2017, CPs will be integrated & checked following this process : ITI CP Integration Process

Ballots

Ballot 36

Out for ballot: Aug 23 - Sep 23, 2016. Comments/votes were reviewed/resolved on the October 7 CP call.

Ballot 36 CPs are archived here: ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance/CPs/Ballots/2017/Ballot_36/

Consolidated comments/votes are gathered here

CPs approved in this ballot are Final Text and are stored here until they are incorporated in 2017: ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance/CPs/3_FinalText/

CP-ITI	Title	Ballot Result
738-03	Replace should deprecate other associations	NOT approved
787-07	HL7 Encoding in SourcePatientinfo / Patient Id Use of Caret Symbol Clarification	Approved w/ updates
864-05	Clarification on Association Classifications (TF-3 4.2.2.2)	Approved w/ updates
955-01	Add DocumentEntry type to FindDocumentsByReferenceId	Approved w/ updates
957-01	Further Submission Set Immutability Cleanup	Approved w/ updates
958-01	Effects of Merge on Relationship Associations	Approved w/ updates
960-00	SoapActionRequired Mandatory	Approved
963-01	Add Pull Point rqmt to new DSUB Extensions TI Supplement	Approved w/ updates

Ballot 37

Out for ballot: Sep 29 - Oct 31, 2016

Ballot 37 CPs are archived here: ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance/CPs/Ballots/2017/Ballot_37/

Consolidated comments/votes are gathered here:

CPs approved in this ballot will be stored here: ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance/CPs/3_FinalText/

Comments/votes will be reviewed/resolved at the Nov 4 CP call.

CP-ITI	Title	Ballot Result
559-05	MPQ profile queries vs Metadata Update option	Approved w/ updates
765-07	Metadata Update Queries with MU level not set/set to 1	Failed ballot; updated version agreed to during comment resolution and will be re-balloted
810-06	Update ITI Security Considerations in MU Supplement	Approved w/ updates
939-06	Update MU Supplement to adjust for redoc of ITI-41 and 42	Approved w/ updates
962-01	MU - Add parameters for SQ-FindDocumentsByReferenceId	Approved w/ updates
965-01	MU - Actor Requirements	Approved w/ updates
966-00	MU – Correct ATNA Message-No Async	Approved
967-01	Update XDS-MU for newer XDR content in ITI TF Vol 1	Approved w/ updates

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: ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance/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. Changes to the 'traditional' schedule for CP calls is announced on the ititech email list.

Nov-4 and Nov-9 2016

Nov 4 Attendees: Bill M (NIST), Elliott L (Harris/QuadraMed), Karen W (Ready Computing), Tarik I (ICW), John M (By Light), Elliot S (McKesson), Joe Lamy, Lynn F

Nov 9 Attendees: Ken M (Merge/IBM), Karen W (Ready Computing), Bill M (NIST), Elliott L (Harris/QuadraMed), Gregorio Canal (Arsenal-IT), John Moehrke , Lynn F

(1) Resolve CP Ballot 37 comments/votes

• Find Ballot 37 CPs here: ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance/CPs/Ballots/2017/Ballot_37/
• Consolidated comments/votes are gathered: https://docs.google.com/spreadsheets/d/1ReN0t3cQ9AwfI8m0xkFtu1S3IWjuaVcksgSWvCokOAw/edit
  • Discussed on Nov 4:
    • 559 - text was updated based on submitted comments. After the meeting, Elliot Silver's confirmed that the new wording addresses his comments adequately and he withdrew his no vote.. version -05 is approved for Final Text.
    • 765 - discussion resulted in significant updates to Sec 3.18.4.1.2.3.5.1.1 "MetadataLevel parameter"; before Nov 9 Lynn will be making editorial updates to address footnote numbering under Stored Query tables, and Elliott L will investigate the proper home for a note currently in Sec 3.18.4.1.2.3.5.1.1
    • 810 - CP was updated based on Elliot's comments, with approval from John. version -06 is approved for Final Text
  • Discussed on Nov 9:
    • 939 - updated per ballot comments; discussed some opportunities to improve text that this CP moves from Vol 3 to Vol 2, but decided against doing so. There are many opportunities for this kind of redocumentation throughout the MU Supplement, and that is outside of the scope of this CP. Version -06 approved for Final Text.
    • 962 - updated per ballot comments; version 01 approved for Final Text
    • 965 - minor update, but some comments of an editorial nature were rejected. Clean-up type issues are not being done in the context of this CP. They are deferred to a yet-to-be planned (or decided on) redoc effort for XDS-MU content
    • 966 - No discussion needed. version -00 is approved for Final Text
    • 967 - diagram fixed per comment; version -01 is approved for Final Text
    • 765 - content was updated per ballot comments. The updates included one change that the group agreed needs to be re-ballot. In addition, there are many editorially fussy/complex changes associated with updates to tables and footnotes in the ITI-18 transaction. The group agreed to re-ballot an updated version of this CP.

(3) Next step for MU CPs

• All CPs in this ballot except for 765 are approved for Final Text. See summary here: http://wiki.ihe.net/index.php/ITI_Change_Proposals_2017#Ballot_37
• Elliott Lavy (hero volunteer and editor extraordinaire) agreed to produce a change-tracked version of the XDS MU TI supplement that starts with XDS MU Rev 1.8 published in Sep-2016. He will apply all CPs in ballot 37 ***including the changes agreed to in 765 (the CP to be re-balloted). This has three immediate benefits:
  • This produces a Word version with CP updates applied for the benefit of implementers for the Jan connectathon. Absent this, it is extremely difficult for implementers (or anyone) to start with the Final Text TF, apply the changes described in the MU Supplement v1.8, and then account for the deltas in the Final Text CPs from Ballot 37.
  • It get multiple implementers eyes on an interim version of the MU Supplement with changes inline to see if it is implementable and to determine whether we missed anything that can be CP'ed before we officially republish this later in 2017.
  • This version with changes integrated will be supplemental material to ITI-CP-765 when it is re-balloted.

* Lynn will create new CP-ITI-979 to account for the need to update Vol 3 Sec 4.1.4 to 4.1.5 within the MU Supplement, and update references as necessary.  This needed change was identified as a ballot 37 comment.  It will be an 'instant final text' CP because it is editorial, and this change will be part of Elliott's updates (previous bullet)

(4) Next in CPs

• The approach for CP work in the coming year will be determined at the Nov 16-17 F2F. There is work in the queue. See http://wiki.ihe.net/index.php/ITI_Change_Proposals_2017#Nov-TBD-2016.

Nov-TBD-2016

Time: To be determined during the Nov 16-17 ITI TC F2F

Webex link:

Meeting number:

Password: Meeting1

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

• 969-01 - Allow Documentation on all Relationship Associations (Elliott L)
• 972-01 - Clarification of Chained Associations (Elliott L)
• 973-01 - Association names (Elliott L)
• 971-01 - Clarify XDSResultsNotSinglePatient Error application (Ken) - contents went through email review
• 938-01 - Audit message for ITI-30 and ITI-31 (Lynn) - created audit msgs for PAM transaction based on existing ITI-8 audit msgs
• 978-00 - MHD Documents encoding in XDW task output/input (Mauro)
• 949-01 - Clarify Folder.lastUpdateTime (Tarik)
• 975-00 - Add reference to HL7v3 feed in description merge for Registry (Lynn)

(2) Process Incoming CPs ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance/CPs/0_Incoming/

• tbd...

(3) Next in CPs

• Summary of plan for CP processing in 2016-17 based on ITI F2F outcomes

Agenda and Minutes from past CP calls

See: ITI CPs 2016-17-Agenda and Minutes from past CP calls