ITI Change Proposals 2017

From IHE Wiki
Revision as of 17:02, 25 October 2016 by ELavy (talk | contribs) (→‎Oct-26-2016: Fix incoming document name)
Jump to navigation Jump to search

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.

  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 for 4 weeks
  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.
  10. CP status and ballots are tracked here

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. 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.
Integrated
contains the version of the CP that was integrated into the TF.
Rejected
CPs that have been submitted but rejected by the committee
Canceled
contains CPs that were once assigned bu have been canceled, i.e. Canceled status
Ballots
contains Ballots that have been released for voting by the general community

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 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. Comments/votes were reviewed/resolved on the October 7 CP call.

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 are Final Text and are stored here until they are incorporated in 2017: ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance/CPs/3_FinalText/

CP-ITI Title Ballot Result
738-03 Replace should deprecate other associations NOT approved
787-07 HL7 Encoding in SourcePatientinfo / Patient Id Use of Caret Symbol Clarification Approved w/ updates
864-05 Clarification on Association Classifications (TF-3 4.2.2.2) Approved w/ updates
955-01 Add DocumentEntry type to FindDocumentsByReferenceId Approved w/ updates
957-01 Further Submission Set Immutability Cleanup Approved w/ updates
958-01 Effects of Merge on Relationship Associations Approved w/ updates
960-00 SoapActionRequired Mandatory Approved
963-01 Add Pull Point rqmt to new DSUB Extensions TI Supplement Approved w/ updates


Ballot 37

Out for ballot: Sep 29 - Oct 31, 2016

Ballot 37 CPs are archived here: ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance/CPs/Ballots/2017/Ballot_37/

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 at the Nov 4 CP call.

CP-ITI Title Ballot Result
559-04 MPQ profile queries vs Metadata Update option
765-07 Metadata Update Queries with MU level not set/set to 1
810-05 Update ITI Security Considerations in MU Supplement
939-05 Update MU Supplement to adjust for redoc of ITI-41 and 42
962-01 MU - Add parameters for SQ-FindDocumentsByReferenceId
965-00 MU - Actor Requirements
966-00 MU – Correct ATNA Message-No Async
967-00 Update XDS-MU for newer XDR content in ITI TF Vol 1


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.

Oct-26-2016

Time: 9-11am CDT

Webex link: https://himss.webex.com/himss/j.php?MTID=ma81b8115ffa958ad954456144e7a156a

Meeting number: 928 606 507

Password: Meeting1

See current CP status spreadsheet here.

(1) Review of new Incoming CPs ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance/CPs/0_Incoming

  • CP-ITI-AGB-FixOptionalitySeRAuditMsg.doc
  • CP-ITI-ELS-Clarify purpose of hash.doc
  • CP-ITI-ELS-Clarify-XDSResultNotSinglePatient.doc
  • These two should be merged on acceptance
    • CP-ITI-ELS-addSignsToListOfAssociations.doc
    • CP-ITI-ESL_Documentation_On_Associations.doc
  • CP-ITI-ESL-clarificationOfChainedAssociations.doc
  • CP-ITI-ESL_Association_Names.doc
  • CP-ITI-GEC_tls_version_update.doc
  • CP-ITI-LFaddReferenceToLH7v3Feed.doc
  • CP-ITI-TPA-XTN-phone-numbers.doc
  • ...more tbd...

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

  • 956-01 - IsSnapshotOf association documentation clean up (Elliott L)
  • 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)
  • 738 Revisited - Replace should deprecate other associations -- initially approved in ballot 36, now back to assigned
  • 949-01 - Clarify Folder.lastUpdateTime (Tarik)
  • ...more tbd...

(3) Next in CPs

  • Oct 31 - Ballot 37 comments due
  • Nov 4, 9-11a, CDT - next CP call is to resolve CP Ballot 37 comments. Comments/CPs available here.

Nov-4-2016

Time: 9-11am CDT

Webex link: https://himss.webex.com/himss/j.php?MTID=m51c9a06ce08d1b73355ca1cc3898af84

Meeting number: 924 218 326

Password: Meeting1

(1) Resolve CP Ballot 37 comments/votes

(2) Next in CPs

  • ...

Agenda and Minutes from past CP calls

See: ITI CPs 2016-17-Agenda and Minutes from past CP calls

Retrieved from "http://wiki.ihe.net/index.php?title=ITI_Change_Proposals_2017&oldid=98350"