ITI Change Proposals 2018-19
This page contains the details of Change Proposal (CP) processing in the ITI domain for the 2018-19 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.
- Write a change proposal. Here is IHE's Change Proposal Template
- 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).
- 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.
- Committee works with editor to draft the CP. Versions are kept in Assigned directory and numbered -00, -01, -02, etc.
- Committee decides CP is ready for ballot. Latest version of CP is moved to Completed diretory and old versions are moved to old_versions.
- Co-chair collects Completed CPs into a ballot. The Ballot directory will be used for this.
- Ballot is released to the general community for voting for 4 weeks
- 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.
- CP approved in ballot are put in FinalText and scheduled to be integrated into the Technical Framework or Supplement.
- CP status and ballots are tracked here
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 2018
- ITI Change Proposals 2017
- 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
All Change Proposal management is done on the IHE ftp site here.
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 in the upcoming publication cycle.
- Integrated
- contains the version of the CP that was integrated into the TF, organized by year.
- Rejected
- CPs that have been submitted but rejected by the committee
- Cancelled
- contains CPs that were once assigned but have been cancelled, i.e. Cancelled status
- Ballots
- 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: https://docs.google.com/spreadsheets/d/1gdr_Y8xZBvbb326J4z67cqprxOexFgtkPj_VlD3rB9E/edit?usp=sharing 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 the "Approved CPs" 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 2018, CPs will be integrated & checked following this process : ITI CP Integration Process
Ballots
Ballot 48
Out for ballot: June 8 - July 9, 2018. Comments/votes resolved on the July 12, 2018 CP review call.
Ballot 48 CPs are here: ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance/CPs/Ballots/2019/Ballot_48/
Comments, votes & resolution are here
CP-ITI | Title | Ballot Result |
---|---|---|
1094-08 | ATNA - Add Option: Require server certificate domain name validation for all traffic over the public internet | Failed ballot; will be reballoted in Ballot 49 |
1124-09 | ATNA – Add two options related to BCP195 TLS Secure Transport Connection | Failed ballot; will be reballoted in Ballot 49 |
Ballot 49
Out for ballot: Aug 10 - Sep 10, 2018. Comments/votes were resolved on the Sep 13, 2018 CP review call.
Ballot 49 CPs are here: ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance/CPs/Ballots/2019/Ballot_49/
Comments, votes & resolution are here.
CPs approved in this ballot are Final Text and are stored here until they are incorporated in 2019: ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance/CPs/3_FinalText/
CP-ITI | Title | Ballot Result |
---|---|---|
697-02 | PIXv3 Query Result | Approved w/ updates; pending confirmation of update by Change HC |
1094-10 | ATNA - Add Option: Require server certificate domain name validation for all traffic over the public internet | Approved w/ updates. This CP is cancelled, but approved text is now in CP-ITI-1145; see below. |
1124-12 | ATNA – Add two options related to BCP195 TLS Secure Transport Connection | Approved w/ updates. This CP is cancelled, but approved text is now in CP-ITI-1145; see below. |
1122-08 | Redocumentation of Appendix V on SOAP Web Services | Approved w/ updates; Vol 2x Rev 15.1 republished in Oct 2018 with this CP |
1123-04 | Redocumentation of Appendix V – HL7 V3 Sections | Approved w/ updates; Vol 2x Rev 15.1 republished in Oct 2018 with this CP |
1145-01 | ATNA – Add three options affecting ITI-19 | Approved. Includes text with resolved comments from CP 1094 and 1124 above |
Ballot 50
Out for ballot: Sep 25 - Oct 24, 2018. Comments/votes resolved on the Oct 25, 2018 CP review call.
Ballot 50 CPs are here: ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance/CPs/Ballots/2019/Ballot_50/
Comments, votes & resolution are here.
CPs approved in this ballot are Final Text and are stored here until they are incorporated in 2019: ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance/CPs/3_FinalText/
CP-ITI | Title | Ballot Result |
---|---|---|
1051-01 | Align BPPC Vol 1 with convention for Content Profiles & Grouping | Failed ballot; needs to be addressed more broadly; back to Assigned |
1134-00 | Author Person Required | Approved |
1135-01 | SAML – multiple levels of nesting must be supported | Approved w/ updates. |
1137-00 | healthCareFacilityTypeCode example fix in ITI-18 | Approved |
1138-01 | Update Form Receiver and Form Processor Role Definition in ITI-35 | Approved |
1139-00 | NPFSm – wrong actor in message semantics | Approved |
1140-00 | ITI TF-1 reference to background material is out of date | Cancelled. Updated links in the TF to ihe.net now have redirects. This change is not needed. |
1141-00 | XCF – example is inconsistent with list of attributes | |
1142-00 | Remove extra spaces in attribute values in ITI-43 | Approved |
1143-01 | DEN: update to formatCode was done on pre-redoc Vol 3 content | Approved w/ update. |
1144-01 | Reference in Vol 3 is circular rather than helpful | Approved w/ updates. |
1146-00 | DSUB - Correct SubmissionSet Suscription Filter Text | |
1147-00 | Out-of-date DICOM reference in ITI-19 | Approved |
Ballot 51
Out for ballot: Jan 22 - Feb 19, 2019. Comments/votes resolved on the March 7, 2019 CP review call.
Ballot 51 CPs are here: ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance/CPs/Ballots/2019/Ballot_51/
Comments, votes & resolution are here.
CPs approved in this ballot are Final Text and will be stored here until they are incorporated in 2019: ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance/CPs/3_FinalText/
CP-ITI | Title | Ballot Result |
---|---|---|
693-03 | Allow “addAttachment” as an Event Type in XDW | Approved w/ updates |
978-03 | MHD Documents encoding in XDW task output/input | Failed ballot. This CP is now Cancelled |
1054-02 | XDW : Datatype fix and update diagram | Approved; rationale updated. |
1086-04 | Clarify Max Length for CX Datatype | Approved w/ updates |
1125-01 | Fix documentEntry.referenceIdList | Approved |
1148-00 | IUA - define JWT token structure | Approved |
1154-00 | Editorial: Fix section numbers in AS4 TI Supplement | Approved |
1157-02 | Add Link to RAD TF - Best Practice for the Grouping of PDI with XDM | Approved |
1158-00 | BPPC editorial fixes | 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: ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance/CPs/1_Assigned/
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 every Thursday from 10-11am Central US. Additional sessions may be scheduled during ITI Tech F2F meetings. Changes to the 'traditional' schedule for CP calls are announced on the ititech email list.
The Google Doc used to gather availability of ITI Tech Members and the focus of future CP calls is here.
March 14, 2018
Time: 10:00 - 11:00 CDT
Webex link: https://himss.webex.com/himss/j.php?MTID=m0c4797d303b0ef85bc37ae2f1e30ee61
Meeting: 926 847 156
Password: Meeting1
Attendees:
The ITI CP tracking spreadsheet is here. (1) Incoming CPs ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance/CPs/0_Incoming/
- CP-ITI-Fix ITI 53 audit...docx - reviewed and approved as Completed CP-ITI-1164 for future ballot 52 (April)
- CP-ITI-LF-PLTupdates.doc - accepted as CP-ITI-1165, but not assigned to anyone at this time. There is no 'owner' of the Patient Location Tracking profile, which has companies registered to test it, for the first time, at the Rennes Connectathon. Lynn will talk to the implementors of PLT at the Connectathon to find out if they find it useful, and perhaps we can find an owner for this CP.
(2) Tarik's topics
- The following was discussed and will become CP-ITI-1166, assigned to Tarik: IUA references RFC 6750. This never made much sense to me. What would the alternative to the Bearer transport of the OAuth2 Token be? I now have a hunch that this was supposed to be RFC 7522 (https://tools.ietf.org/html/rfc7522) instead. The option makes more sense if it allows interoperability between XUA and IUA by allowing clients to get a OAuth Access Code using a SAML Bearer Token.
- The following was discussed and will become CP-ITI-1167, assigned to Tarik: The topic came up in german national specifications using IHE XDS whether MTOM/XOP has to be used for all ITI-41 and ITI-43 transactions or whether the client decides. Vol2b states in 3.41.4.1.2 that "The Provide and Register Document Set-b Response message shall use SOAP 1.2 and MTOM with XOP encoding (labeled MTOM/XOP in this specification). Implementors of this transaction shall comply with all requirements described in: ITI TF-2x: Appendix V: Web Services for IHE Transactions." Vol2x Appendix V.3.6 states "Actors that create messages with xsi:base64Binary content may use XOP Optimization to reduce the size of the message. If there are multiple xsi:base64Binary content elements, the actor may optimize none, any or all of them at its discretion. Typically, small content will be left in the XML Infoset while larger content will be "optimized".
ITI-43 also requires use of MTOM and XOP, but then includes an example without it, using the following explanation: "A second form of the response is possible, an un-optimized MTOM/XOP message. In this form the message is still formatted as a multipart but the document contents is not split out into a separate part of the multipart. Some popular Web Service toolkits generate this form for very small documents. The same response in this form looks like..." (3.43.5.1.2.1) There should be clear guidance whether the MTOM and XOP must be used in ITI-41 and -43.
(3) Next in CPs
- Reminder: If you want a CP to be integrated into TF docs in June, then the CP should be reviewed and completed in March so it can be balloted in April. There are openings on the Mar 21 and 28 agenda for Assigned CPs ready for review.
March 21, 2018
Time: 10:00 - 11:00 CDT
Webex link: https://himss.webex.com/himss/j.php?MTID=m0c4797d303b0ef85bc37ae2f1e30ee61
Meeting: 926 847 156
Password: Meeting1
Attendees:
The ITI CP tracking spreadsheet is here.
(1) Assigned CPs for Review ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance/CPs/1_Assigned/
- CP-ITI-1130 - Updates to Async option in existing TF to align with AS4 TI Supplement (Charles)
- more tbd
(2) Incoming CPs ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance/CPs/0_Incoming/
- tbd
(3) Next in CPs
- x