ITI Change Proposals 2016

Introduction

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

Since March 2015, the 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 to be integrated in 2016

CPs that have passed ballot in this cycle, and that will be integrated into Version 12.0 of the Technical Framework and the 2016 version of Supplements in September 2016 are listed on the "Ballot Log" tab of the tracking spreadsheet.

In Aug 2016, CPs will be integrated & checked following this process (currently draft): ITI CP Integration Process

Ballots

Ballot 29

Out for ballot: Aug 13 - Sep 16 2015

Ballot 29 CPs, comments, and votes are archived here: ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2016/CPs/Ballots/ballot_29/

CPs approved in this ballot are here: ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2016/CPs/3_FinalText/from_Ballot_29/

Comments/votes were reviewed on the Sep 24 & 25 CP calls. Resolution is in the table below.

CP-ITI	Title	Ballot Result
559-02	MPQ profiles queries vs. Metadata Update option	Approved
801-04	Update Vol 1 references to RFC 3881	Approved w/ updates
872-05	Add ATNA Repository Forwarding and re-doc ITI-20 transaction	Approved w/ updates

Ballot 30

Out for ballot: Nov 23 - Dec 1, 2015

Ballot 30 CPs, comments, and votes are archived here: ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2016/CPs/Ballots/ballot_30/

CPs approved in this ballot will be posted here: ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2016/CPs/3_FinalText/from_Ballot_30/

Comments/votes will be reviewed on the CP call on December 4, 2015

CP-ITI-	Title	Ballot Result
771-04	Clarify hash validation rules in Volume 3	Approved w/ updates
797-07	Definition of Document	Approved
814-06	Remove ambiguity about “Registry Enforcement” of display name in coded attributes	Failed; back to assigned
857-03	Clarify/update the use of homeCommunityID in XCA	Failed; back to assigned
870-02	Repository behavior on ITI-42 failure	Approved w/ updates
879-01	mACM - Fix inaccurate Field and Section references plus typos	Approved
890-02	mACM – Clarify resources included in ITI-84 and ITI-85 response	Approved w/ updates

Ballot 31

Out for ballot: Dec 4, 2015 - Jan 6, 2016

Ballot 31 CPs, comments, and votes are archived here: ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2016/CPs/Ballots/ballot_31/

CPs approved in this ballot are posted here: ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2016/CPs/3_FinalText/from_Ballot_31/

Comments/votes were reviewed on the CP call on January 8, 2016

CP-ITI-	Title	Ballot Result
814-08	Remove ambiguity about “Registry Enforcement” of display name in coded attributes	Approved w/ updates
858-03	Fix ITI-39 error reporting requirements	Approved w/ updates
889-03	Clarify Error Code used for ‘RPLC’ or ‘XFRM_RPLC’ Association Validation	Failed; updates made require reballoting
893-00	mACM – clarify actor requirements for create & read	Approved
896-00	referenceIdList Clarification	Failed; back to assigned
898-01	Update to MetadataLevel Parameter	Approved w/ updates
899-00	Typo in XCPD Query transaction	Approved
900-00	mACM – fix PCD-06 mapping for alert text	Approved
903-01	Add encounterID to referenceIdList	Approved w/ updates
904-00	Fix ASTM signature purpose vocabulary	Approved

Ballot 32

Out for ballot: Feb 24 - Mar 15, 2016.

The ballot announcement is here.

The ITI Technical Committee will review comments/votes on these dates:

• Thu March 17, 2016, 9-11am CDT - MHD and Appendix Z comments
• Fri March 18, 9-11am CDT' - PIXm and PDQm comments
• Thu March 24, 8-11am CDT - MHD, Appx Z and PIXm comments
• Wed Apr 6, 8-10am - finish open review items

Ballot 32 CPs are archived here: ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2016/CPs/Ballots/ballot_32/

Ballot 32 consolidated comments & votes are here.

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

CP-ITI	Title	Ballot Result
884-00	PIXm changes for DSTU2
885-00	PDQm changes for DSTU2
886-00	MHD changes for DSTU2
919-00	Split FHIR-specific Appendix Z out of PDQm supplement & update for DSTU2	20160428: Appx Z approved w/ updates per ballot comments

Ballot 33

Out for ballot: March 21 - April 20, 2016

Ballot 33 CPs are archived here: ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2016/CPs/Ballots/ballot_33/

Ballot 33 consolidated comments and votes are here.

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

Comments/votes were reviewed at the Apr 21 CP call.

CP-ITI	Title	Ballot Result
582-05	Metadata Update correction for associations in GetAllQuery	resolution pending discussion @ F2F
799-01	SubmissionSets are immutable	Approved
857-05	Clarify/update the use of homeCommunityId in XCA	Approved w/ updates
880-03	Add new value for Study Instance UID in CXi.5 (Identifier Type Codes)	Approved w/ updates
888-04	ProducerReference in ITI-53 and ITI-54 – fix unclear usage	resolution pending discussion @ F2F
889-07	Clarify Error Code used for ‘RPLC’ or ‘XFRM_RPLC’ Association Validation	resolution pending discussion @ F2F
895-04	Clarify/update the use of homeCommunityID in XCPD	Approved w/ updates
896-04	referenceIdList Clarification	Approved w/ updates
901-03	On-Demand Document Source options	Approved w/ updates
905-00	ITI-8 PID field Optionality	Approved
906-00	ITI-8 MSH message structure - Revert changes introduced in CP-ITI-786	Approved
908-00	Table 4.3.1.1-3: on-demand repositoryUniqueId should be required	Approved
918-01	Fix workflowInstanceId specification in Vol 3 CXi datatype definition	Approved w/ updates

Assigned CPs

For a list of CPs that are currently assigned see the 'CP tracking' tab in the CP status google doc. Assigned CPs are stored here: ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2016/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.

April-25-29 F2F CP topics

(1) Finish Ballot 33 comment resolution

• Consolidated comments are here: https://docs.google.com/spreadsheets/d/1IQ8k8eEsuKfG8o8fldu2eQUxA1GVPJ5A8S4UfyuM1cI/edit?usp=sharing
• Three CPs need further review ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2016/CPs/Ballots/ballot_33/
  • CPs that will benefit from Bill's input:
    • CP 582 -- Metadata Update correction for associations in GetAllQuery
      • RESOLUTION: BIll agreed with changes. CP is final text (w/ agreed to edits)
    • CP 889 -- Clarify Error Code used for ‘RPLC’ or ‘XFRM_RPLC’ Association Validation
      • NOTES (to do for this CP from Key M):

1) Review the arguments for/against the error code UnresolvedReferenceException (see other email). > If so, do we need to make other changes to the Framework for conflicts? Do we need to make changes to MU > If not, then add the error code to the table. 3) Update the language contained in the CP inconsideration of the ITI-42 ReDoc. 4) Determine whether or not the CP requires re-balloting.

Summary:

CP-899 was challenged by Elliot Silver during the last week's ballot/call. There was insufficient time to resolve the issue on the call so I offered to review the comments and offer an opinion. This was sent back to Lynn last Friday morning (I'll forward the e-mail with my comments under separate cover).

The main challenge, and correctly so, was bringing forward the UnresolvedReferenceException into the Framework as part this CP. The wording around the exception was too broad and thus could be interpreted as being used for other existing ITI-42 use cases which could be considered as a breaking change. As such, I updated the text just simply add the error code XDSReplaceFailed and avoid the debate in order to close out this CP (the code had to be added anyway-it's what started this in the first place).

Also, what I did not know at the time was that the Redoc of ITI-41/42 was also going to be released that Friday afternoon. As such, the section of text affected by this CP has been moved and also rewritten from a grammar standpoint. Thus, additional word-smithing will be required for the language contained in the CP which should not be too painful. I'm not sure what process right now for CPs that are part of the ReDoc.

• • DSUB CPs:
    • CP 888 -- ProducerReference in ITI-53 and ITI-54 – fix unclear usage
      • RESOLUTION: Updated version agreed to via email. CP is final text.

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

• 882-01 - Fix merge references from PIX Feed(s) to XDS - (no new changes, but it can now move forward since redoc has been published) (Elliott L)
• 821-02 - Add specification for ITI-32 audit message (Elliott L)
• 846-08 - Clarify Base64 Required/XOP (Elliott L)
• 914-03 - Value of Content-Type HTTP header action parameter (Elliott L)
• 924-01 - Fix TF Reference in XCDR supplement (Karen)
• 894-02 - Object List Description Improvement (Elliot S)
• 533 - MU Delete from Repository (Bill) -- See notes Bill's notes here: https://docs.google.com/document/d/1H8Q-OPC_xV-qI3hFam5kqg2ML8fudbAMJjPISa7Z-EQ/edit
  • RESOLUTION: Bill updated the above document with notes/conclusions based on committee discussion. Bill will proceed to address the Change Proposal based on conclusions reached and it will be presented at a future CP call and balloted when ready.
• 922-01 - Make PIX Manager behavior consistent across PIX, PIXv3, and PIXm (Jens V)
  • RESOLUTION: CP is cancelled
• 767-02 - Fix errors in CXi datatype and referenceIdList attribute examples (John M/Elliot S)
  • RESOLUTION: CP is complete & ready for ballot
• 764-02 - Clarify CXi datatype (John M/ Elliot S)
  • RESOLUTION: CP is complete & ready for ballot

• 925-00 - Clarify UTC offset within DTM datatype (Nader)
  • RESOLUTION: Discussion determined that the update does not belong in the DTM data type definition. Instead, for individual time-based metadata attributes, we need guidance about handling time-zone offsets. CP remains assigned for additional work.

• 864-02 - Clarification on Association Classifications (TF-3 4.2.2.2) (Bill)
  • RESOLUTION: We discussed input provided by Ken Meyer. Bill will update the CP based on the comments. CP remains assigned for additional work.

(3) Finish Ballot 32 (FHIR-based supplement) updates

• Per supplement, identify remaining work, owners, timeline:
  • Consolidated comments are here
  • Not-quite-finished versions used for EU Connectathon are here
  • Lynn's notes from EU Connectathon discussion w/ developers are here
    • RESOLUTION:
      • 20160428: Appx Z approved for TI republication w/ changes based on ballot comments
      • 20160428: MHD
      • 20160428: PDQm
      • 20160428: PIXm

(4) Handling updates to FHIR-based profiles when DSTU2 revs

• The DSTU1-->2 updates were handled via a CP ballot because we had no other mid-cycle vehicle. It was not the right process (Lynn's opinion). Can we look at what might happen in 2016-17, consider the needs of the committee & implementers, and apply lessons learned?

(5) Identify & Re-assign CPs that need a new owner

• CPs need a new owner if they are languishing or if current owner can no longer work on them
• See Columns L-T on the Apr-Blitz tab of the ITI CP Tracking Spreadsheet

(6) Process Incoming CPs ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2016/CPs/0_Incoming/

• CP-ITI-CSD_transactions.docx (Carl) - Assigned to Carl as CP-ITI-926
• CP-ITI-ES-MU-patient-merge.doc (Elliot)
• CP-ITI-KW-Tran#inHeaders.doc (Karen)
• CP-ITI-fixSERurnEncoding.doc (Mauro)
• CP-ITI-ES-ReferenceIdList-homeCommum.... (Elliot)
• CP-ITI-TI-Security-relevant-attributes_v2.doc (Tarik)
• CP-ITI-TI-Replace-XUA-homeCommunityId.doc (Tarik)

(7) Blitz

• See Apr-Blitz tab on the ITI CP Tracking Spreadsheet

Agenda and Minutes from past CP calls

For 2015-16, they are collected here: ITI CPs 2015-16-Agenda and Minutes from past CP calls