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 and details on how to submit comments are 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, 2016, 9-11am CDT' - PIXm and PDQm comments

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

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

Ballot 33

Will be Out for ballot: March 21 - April 22, 2016

Ballot 33 CPs, comments, and votes will archived here:

CPs approved in this ballot will be stored here:

Comments/votes will be reviewed at the CP call on: TBD

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

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.

March-4-2016

Fri, 9-11am CST

• Webex link: https://himss.webex.com/himss/j.php?MTID=m6a38776c9b99e3481f4d256e5949dc54
• Phone number: 1-866-469-3239
• Meeting number: 926 562 253
• Password: Meeting1

Agenda

The current ITI CP status spreadsheet is here

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

• CP-ITI-907 - IUA Maintenance and alignment with FHIR initiatives (Massi)
• CP-ITI-307 - PDQ Continuation Protocol in One Socket or Multiple Sockets (Rob H)

(2) Incoming CPs for review: ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2016/CPs/0_Incoming

• CP-ITI-CS-HPDvsISOrqmts.doc
• CP-ITI-JKV-FIX.PIX.BECAUSE.IT.IS.INCONSISTENT.doc
• CP-ITI-FixSectionRefInITI-20.docx

(3) approx 10:00 CST -- review of the ITI-41 and 42 Redoc integration of CPs (Elliott L & Karen W)

• ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr14-2016-2017/Technical%20Cmte/Workitems/DocShareRedoc/IHE_ITI_Suppl_ReDoc_DocSharingProfiles_Rev1.0_PC_2016-03-03.docx

(4) 10:30 CST -- Discuss audit logging in RFD-based profiles

• Interested members of the QRPH Technical Committee will join for this discussion
• CP-ITI_916 - Add ATNA audit message details to RFD transactions (Rob Horn, John Stamm)

(5) Next in CPs

• Seeking committee feedback on CPs in FTP site --> perhaps moving from yearly hierarchy to functional
• Ballot 32 timeline:
  • March 15 - comments & votes due
  • March 17 - review comments PDQm, PIXm, Appx Z
  • March 18 -- review comments MHD

Minutes

Attendees: Elliott L, Rob H, Steve M, Massi M, Steve M, Mauro Z, Lynn F, Duarte Ferreira, Raphael Oliveira, John M, Lisa Nelson (QRPH TC), Robert Barr (QRPH TC),

(1) Assigned for discussion

• CP-ITI-907 - IUA Maintenance and alignment with FHIR initiatives (Massi) - The group discussed post-connectathon comments received from Johannes (icoServe) as well as benefits/pitfalls for including examples. Next, John will consider this discussion & the comments the CP and determine how they might affect the documentation of the IUA transaction. The CP remains in 'Assigned' state and will be discussed again in the future after John finishes the analysis.
• CP-ITI-307 - PDQ Continuation Protocol in One Socket or Multiple Sockets (Rob H) - The group discussed issues around behavior of the server when continuation happens. The group agreed that clarification is needed that affects interoperability (ie not just application behavior). Rob is going to write a paragraph and then Lynn will use this to get feedback from a few connectathon implementers of PDQ Suppliers. CP remains 'Assigned'.
• CP-ITI-914 - Value of Content-Type HTTP header action parameter - Elliott L lead the discussion on determining approach for cleaning up specification of soapAction across multiple transactions. This was started in CP 510 (in 2011) with a change to Appendix V. Elliott agreed to modify one transaction as a way to illustrate what the changes would look like across SOAP-based transactions. When this is done, we can distribute to implementers for feedback before making changes in multiple transactions.

(2) Incoming CPs for review: ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2016/CPs/0_Incoming

• CP-ITI-CS-HPDvsISOrqmts.doc - accepted and assigned to Eric H as CP-ITI-921. Lynn will follow up with Eric.
• CP-ITI-JKV-FIX.PIX.BECAUSE.IT.IS.INCONSISTENT.doc - accepted and assigned to Jens V as CP-ITI-922. The committee provided guidance that PIXm should be modified to be in line with PIXv2 & v3, rather than the other way around. This is to ensure that existing implementations of PIX Managers supporting v2 and v3 are able to keep existing behavior. Lynn will follow up with Jens.
• CP-ITI-FixSectionRefInITI-20.docx - accepted and assigned to Rob H as CP-ITI-920.

(3) Review of the ITI-41 and 42 Redoc integration of CPs (Elliott L & Karen W)

• Elliott walked us through 3 updates to the redoc work that were driven by CPs
  • CP-870 - Final Text - The change for this CP is completely integrated into the updates that will be published for re-doc
  • CP-814 - Final Text - The change for this CP is partially integrated into the updates that will be published for re-doc. Additional changes for Vol 3 will be integrated in late summer
  • CP-846 - This CP is assigned to Elliott. This CP will be updated/balloted/completed after Redoc (will be based on the redoc updates)
  • Lynn will add notes to the above CPs & status spreadsheet so that we are not confused about this later in summer when approved CPs get integrated.

(4) Discuss audit logging in RFD-based profiles

• Robert Barr & Lisa Nelson from the QRPH Technical Committee joined for this discussion
• CP-ITI_916 - Add ATNA audit message details to RFD transactions (Rob Horn, John Stamm)
• Robert Barr commented that in Clinical Trial scenarios, a Form Processor is overlaid onto an EHR. It may not be possible/practical to do ATNA auditing. The Security Considerations section for RFD-profiles in clinical scenarios (and perhaps others) could specify that the internal (ie non-ATNA) auditing that the 'systems' in the scenario are able to export their (non-IHE) audits for security-relevant event (eg a transaction) to a (non-IHE) audit repository in the environment.
• The CRD profile (http://www.ihe.net/uploadedFiles/Documents/QRPH/IHE_QRPH_Suppl_CRD.pdf) in Section 5.Z3 contains the 'base' audit msg definitions for RFD-based profiles in QRPH.
• The audit msgs in that section are missing some updates that have been applied to ITI audit msg definitions in the last year or two (eg removing RFC-3881 & reference to DICOM Supp 95)
• Lisa commented that QRPH TC members do not have the expertise necessary to be able to correctly tweak/modify those messages for auditing in new QRPH profiles.
• The group agreed that we could collaborate to create a short checklist / guidance document that QRPH could use to (1) assess whether ATNA auditing was necessary for a given profile/use case, (2) if yes, guidance on how to modify an audit msg based on the DICOM schema (req'd for an ITI-20 audit msg) for a specific transaction (eg a form submission in a specific QRPH profile)
• We will not add 'vanilla' audit message specifications to ITI-34,35... in the ITI TF. The contents of the audit msg will always be profile/transaction specific.
• Lynn will facilitate scheduling joint QRPH/ITI TC time to work on the checklist, probably at 10am Central on either the first Friday in April or May, when both committees have a recurring call that overlaps.

(5) Next in CPs

• Seeking committee feedback on CPs in FTP site --> perhaps moving from yearly hierarchy to functional
  • The group thought that the benefits of removing the 'annual' folder structure from the FTP site might be worth the work. Lynn will think about this a bit more before proceeding
• Ballot 32 timeline:
  • March 15 - comments & votes due
  • March 17 - (regular 3rd Thurs CP call) - review comments on PDQm, PIXm, Appx Z
  • March 18 - (additional call) - review comments on MHD

March-17-2016

Thu, 9-11am CDT

• Webex link:
• Meeting number:
• Password:

Agenda

(1) Process Ballot 32 comments on the MHD and Appendix Z Supplements

March-18-2016

Fri, 9-11am CDT

• Webex link:
• Meeting number:
• Password:

Agenda

(1) Process Ballot 32 comments on the PIXm and PDQm Supplements

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