Difference between revisions of "ITI Change Proposals 2016"

From IHE Wiki
Jump to navigation Jump to search
Line 149: Line 149:
 
   reviewed 857-02. Adjusted wording in new section.
 
   reviewed 857-02. Adjusted wording in new section.
 
   Split CP to separate first section, where no agreement reached on clear wording.  Remainder is ready to go.  The subject matter is fully separate.
 
   Split CP to separate first section, where no agreement reached on clear wording.  Remainder is ready to go.  The subject matter is fully separate.
   New CP to continue effort will be CP-ITI-895
+
   New CP to continue effort will be CP-ITI-895 - Clarify/update use of homeCommunityID in XCPD.  857 becomes Clarify/update use of homeCommunityID in XCA
  
 
* CP-ITI-879-01 -  
 
* CP-ITI-879-01 -  

Revision as of 11:08, 15 October 2015

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 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


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.

Oct-15-2015

9-11am CDT

Agenda

The current ITI CP status spreadsheet is here.

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

  • CP-ITI-CS-ProducerReferenceITI53ProducerReferenceBrokerID.doc (Clay S)
  • CP-ITI-MZ-ProducerReferenceITI54UnclearUsage.doc (Mauro Z)
  • CP-ITI-KM_XDSReplaceFailed.doc (Ken Meyer)
  • CP-ITI-LF-mACM-clarify-ITI-84-response.doc (Lynn...Carl reviewed;hopefully ready for ballot)
  • CP-ITI-LF-mACM-clarifyOperations.doc (Lynn)
  • CP-ITI-LF-mACM-clarify-ITI-85-resource-constraints.doc (Lynn)
  • CP-ITI-ESL-PIXm_Audit.doc
  • CP-ITI-ELS-XDS-objects-represent.doc
  • ...

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

  • CP-ITI-857-01 - Clarify/update the use of homeCommunityID in XCA and XCPD (Karen W)
  • CP-ITI-879-01 - mACM Fix inaccurate field and section references (Lynn...should be ready for ballot)
  • CP-ITI-814 - Remove ambiguity about “Registry Enforcement” of display name in coded attributes (Elliott L)
  • more tbd

(3) Next in CPs

  • Lynn will compile Ballot 30 with Completed CPs as of the end of this call
  • The next CP call is on Friday Nov 6, 9-11am

Minutes

Attendees:

(1) Review of Incoming CPs

  • CP-ITI-CS-ProducerReferenceITI53ProducerReferenceBrokerID.doc - assigned 888
  • CP-ITI-MZ-ProducerReferenceITI54UnclearUsage.doc - merged with 888
  • CP-ITI-KM_XDSReplaceFailed.doc - assigned 889
  • CP-ITI-LF-mACM-clarify-ITI-84-response.doc - assigned 890
  • CP-ITI-LF-mACM-clarifyOperations.doc - 892
  • CP-ITI-LF-mACM-clarify-ITI-85-resource-constraints.doc - 893
  • CP-ITI-ESL-PIXm_Audit.doc - 891, extend to other transactions and make consistent with the DSTU2 update effort.
  • CP-ITI-ELS-XDS-objects-represent.doc - 894

(2) Assigned CPs for review

  • CP-ITI-857-01 -
 reviewed 857-02. Adjusted wording in new section.
 Split CP to separate first section, where no agreement reached on clear wording.  Remainder is ready to go.  The subject matter is fully separate.
 New CP to continue effort will be CP-ITI-895 - Clarify/update use of homeCommunityID in XCPD.  857 becomes Clarify/update use of homeCommunityID in XCA
  • CP-ITI-879-01 -
  • CP-ITI-814 -
  • more tbd

(3) Next in CPs

  • Lynn will compile Ballot 30 with Completed CPs as of the end of this call
  • The next CP call is on Friday Nov 6, 9-11am

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