Difference between revisions of "ITI Change Proposals 2017"
m (→Agenda and Minutes from past CP calls: Change from http to wiki link) |
(→Sep-27-2016: Change from http to wiki link) |
||
Line 194: | Line 194: | ||
'''(3) Next in CPs''' | '''(3) Next in CPs''' | ||
− | * Oct 7, 9-11a, CDT - next CP call is to resolve CP Ballot 36 comments. Comments/CPs available [ | + | * Oct 7, 9-11a, CDT - next CP call is to resolve CP Ballot 36 comments. Comments/CPs available [[ITI Change Proposals 2017#Ballot_36 | here]]. |
== Oct-7-2016 == | == Oct-7-2016 == |
Revision as of 15:41, 12 September 2016
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.
- 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.
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 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
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 will be stored here: ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance/CPs/3_FinalText/
Comments/votes will be reviewed/resolved: October 7 CP call, 9-11am CDT
CP-ITI | Title | Ballot Result |
---|---|---|
738-02 | Replace should deprecate other associations | |
787-06 | HL7 Encoding in SourcePatientinfo / Patient Id Use of Caret Symbol Clarification | |
864-04 | Clarification on Association Classifications (TF-3 4.2.2.2) | |
955-00 | Add DocumentEntry type to FindDocumentsByReferenceId | |
957-00 | Further Submission Set Immutability Cleanup | |
958-00 | Effects of Merge on Relationship Associations | |
960-00 | SoapActionRequired Mandatory | |
963-00 | Add Pull Point rqmt to new DSUB Extensions TI Supplement |
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.
Sep-7-and-23-2016
Date/Time: Sep 23, 10am - noon CDT
Webex link for Sep 23: https://himss.webex.com/himss/j.php?MTID=m25ab8d60740e859014fe17537d66aa6f
Meeting number: 922 149 163
Password: Meeting1
Attendees Sep 7: Ben Levy, Elliot Silver, Bill Majurski, Tarik Idris, Elliott Lavy, John Moehrke, Ken Meyer, Mark Hodgson, Mark Sinke, Karen Witting, Harsha (eMedical), Lynn Felhofer
Attendees Sep 23:
(1) 2016 version of XDS Metadata Update TI Supplement and Final Text volumes
- All CPs that will be completed as part of this effort must use the 2016 MU Supplement and the 2016 FT TF as the baseline content
- The Word version of the MU Supplement, v1.8, that will be published later in September and the Final Text volumes to be republished can be found here: ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr14-2016-2017/Technical%20Cmte/Workitems/Pre-Publication%20Drafts%20of%20TIs%20and%20TFs/ReviewComplete/
(2) Assigned Metadata Update CPs ready for discussion ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance/CPs/1_Assigned/
- Sep 7 results:
- 559 - MPQ profile queries vs Metadata Update option - re-assigned to Mark who will update both the rationale and the note added by the CP based on Sep 7 discussion. This updated CP will then be balloted.
- 756 - MPQ fixes to ensure Metadata Update compatibility - this CP will be Cancelled; we will not accommodate MPQ queries in the context of MU. Since CP 559 is also MPQ-related and will be balloted, Mark will update 559 to include the rationale for not updating MPQ queries for MU.
- 785 - Patient ID Consistency in stored query responses wrt XDS metadata update - there was an extensive discussion of issues and alternatives
- In the November timeframe, Bill will be writing MU test cases to expose current Registries' behavior for these queries
- In parallel, Mark will write up use cases for an administration (not Doc Consumer) in the context of this CP
- These two efforts will provide more detail from two perspectives and will inform how this CP will eventually be resolved; no textual changes will be proposed until these efforts make the path forward clearer.
- Sep 23 CPs for discussion:
- 765 - Metadata Update Queries with MU level not set/set to 1 - assigned to Bill
- 810 - Update ITI Security Considerations in MU Supplement - assigned to Ken
- 939 - Update MU Supplement to adjust for redoc of ITI-41 and 42 - assigned to Karen
- 962 - MU - Add parameters for SQ-FindDocumentsByReferenceId - assigned to Ken
(3) Incoming MU CPs for consideration ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance/CPs/0_Incoming/
- Sep 7 results:
- CP-ITI-KM_MU_Asynchronous_Support.doc - accepted as CP 964 assigned to Ken, but scope was changed; we will not add async option to Doc Admin, but we will add a note to clarify the scope of transactions that must be supported, eg if a Registry supports async & MU, it does not have to support async on MU transactions. This CP will be moved out of the MU effort and discussed next on Sep 27
- Sep 23 CPs for discussion:
- CP-ITI-KM_MU_Actor_Requirements.doc
- CP-ITI-ELS-MU-additional-updates.doc
- CP-ITI-ELS-UpdateXDS-MUforNewerXDRinVol1.docx
(4) Next in CPs
- Next discussion of MU CPs is on Sept 23, 10-noon CDT
- It is important for CP editors to share updates to their CPs on the ititech and/or XDS implementer's email lists as progress is made so that people have an opportunity to review and provide input on proposed changes prior to the Sep 23 call.
- Determine CP Ballot 37 timing; will contain the completed MU CPs
- mmm-dd-2016 - Completed (ready-for-ballot) CPs to Lynn
- mmm-dd-2016 -Lynn packages ballot & send to Jeremiah
- mmm-dd-2016 - Ballot announced
- mmm-dd-2016 - Ballot closed
- mmm-dd-2016 - Comment resolution webex
Sep-27-2016
Time: 10am-noon CDT
Webex link: https://himss.webex.com/himss/j.php?MTID=m21d16cdc5d1be2c8f7228cfe5d474dc0
Meeting number: 922 395 129
Password: Meeting1
See current CP status spreadsheet here.
(1) Review of new Incoming CPs ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance/CPs/0_Iincoming
- CP-ITI-ELS-Clarify purpose of hash.doc
- CP-ITI-GEC_tls_version_update.doc
- CP-ITI-TPA-XTN-phone-numbers.doc
- ...tbd...
(2) Assigned CPs ready for discussion ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance/CPs/1_Assigned/
- 961-01 - XCDR Cleanup (Elliott L) - note: changes were reviewed in advance by Karen
- 964-01 - Clarify async wrt actors that support MU transactions (Ken)
(3) Next in CPs
- Oct 7, 9-11a, CDT - next CP call is to resolve CP Ballot 36 comments. Comments/CPs available here.
Oct-7-2016
Time: 9-11am CDT
Webex link: https://himss.webex.com/himss/j.php?MTID=mc32b24fc35136613c7c1fada0e3b4294
Meeting number: 924 218 326
Password: Meeting1
(1) Resolve CP Ballot comments/votes
- Find Ballot 36 CPs here: ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance/CPs/Ballots/2017/Ballot_36/
- Consolidated comments/votes are gathered here
(2) Next in CPs
- Next regular CP call is Thurs Oct 20, 9-11 CDT am
- Ballot 37 (MU CPs) votes/comments due: Oct TBD