Difference between revisions of "ITI Change Proposals 2018-19"
Line 210: | Line 210: | ||
'''(2) Review Incoming CPs''' ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance/CPs/0_Incoming/ | '''(2) Review Incoming CPs''' ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance/CPs/0_Incoming/ | ||
− | * tbd... | + | * CP-ITI-Vol3_MetadataReference.docx |
+ | * more tbd... | ||
'''(3) Next in CPs''' | '''(3) Next in CPs''' |
Revision as of 12:56, 30 August 2018
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
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 |
---|---|---|
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 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-01 | PIXv3 Query Result | |
1094-10 | ATNA - Add Option: Require server certificate domain name validation for all traffic over the public internet | |
1124-12 | ATNA – Add two options related to BCP195 TLS Secure Transport Connection | |
1122-07 | Redocumentation of Appendix V on SOAP Web Services | |
1123-03 | Redocumentation of Appendix V – HL7 V3 Sections |
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.
Aug 30, 2018
Time: 10:00 - 11:00 CDT
Webex link: https://himss.webex.com/himss/j.php?MTID=m5bee5cd2fc5bf1bd681df5df78c1d6ca
Meeting: 929 898 116
Password: Meeting1
Attendees: Tarik Idris (ICW), Elliott Lavy (N Harris Computer), Ben Levy (Corepoint Health), Spencer LaGesse (Epic) -- welcome!!!, Vassil Peytchev (Epic), John Moehrke (By Light), Lynn Felhofer, (Elliot S attempted to join)
The ITI CP tracking spreadsheet is here.
(0) New CP Motto recommendation:
- We will ballot no CP before its time.
(1) Review Incoming CPs ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance/CPs/0_Incoming/
- CP-ITI-XDS-Query_HealthcareFacilityTypeCodeExample.doc - assigned to John and accepted as Completed CP 1137 for future ballot 50
- CP-ITI-TP-RFDGlossaryUpdates_AG2.doc - assigned to Lynn; recommended wording slightly modified. Lynn will check to see if other transactions are affected and will confirm with Alex that new wording is ok. If no issues, this CP is accepted as Completed CP 1138 for future ballot 50
- CP-ITI-NPFSm_Wrong_actor in message semantics.docx - assigned to Gregorio and accepted as Completed CP 1139 for future ballot 50
- CP-ITI-TF_App_C.doc - assigned to John and accepted as Completed CP 1140 for future ballot 50
- CP-ITI-TP-fixXCFinconsistency.doc - assigned to Thomas Papke and change to example is accepted as Completed CP 1141 for future ballot 50
- CP-ITI-LF-removeExtraSpaces.doc - assigned to Lynn and accepted as Completed CP 1142 for future ballot 50
- CP-ITI-DENupdatesToOldVol3.docx - this editorial CP is assigned to John as CP 1143
(2) Assigned CPs for Discussion ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance/CPs/1_Assigned/
- CP-ITI-1131-01 - ATNA – Clarify ITI-19 rqmts for All Connections carrying Protected Information (Elliot S)
(3) Next in CPs
- Reminder: Ballot 49 votes/comments due Sep 10
in the queue for discussion:
- 1130-04 - Editorial: Updates to Async option in existing TF to align with AS4 TI Supplement (Charles, Massi)
- 1051-01 - Align BPPC Vol 1 with convention for Content Profiles & Grouping (Lynn)
Sep 6, 2018
Time: 10:00 - 11:00 CDT
Webex link: https://himss.webex.com/himss/j.php?MTID=m5bee5cd2fc5bf1bd681df5df78c1d6ca
Meeting: 929 898 116
Password: Meeting1
Attendees:
The ITI CP tracking spreadsheet is here.
(1) Assigned CPs for Discussion ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance/CPs/1_Assigned/
- CP-ITI-1131-01 - ATNA – Clarify ITI-19 rqmts for All Connections carrying Protected Information (John)
(2) Review Incoming CPs ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance/CPs/0_Incoming/
- CP-ITI-Vol3_MetadataReference.docx
- more tbd...
(3) Next in CPs
- Reminder: Ballot 49 votes/comments due Sep 10
in the queue for discussion:
- 1130-04 - Editorial: Updates to Async option in existing TF to align with AS4 TI Supplement (Charles, Massi)
- 1051-01 - Align BPPC Vol 1 with convention for Content Profiles & Grouping (Lynn)
Sep 13, 2018 - Ballot 49 resolution
Time: 10:00 - noon CDT
Webex link:
Meeting:
Password:
Attendees:
(1) Resolve Ballot 49 CPs
- Ballot contents are here: ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance/CPs/Ballots/2019/Ballot_49/
- Votes/comments are here: https://docs.google.com/spreadsheets/d/1qOJsHB0Ny2cJyfN8NbyTACdA_VjvgCg6ZvZEUjYGGLw/edit#gid=0
(2) Next in CPs
- tbd...