ITI Change Proposals 2017

From IHE Wiki
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.

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.

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

tbd...

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.

Aug-18-2017

Attendees: Ken M (Merge/IBM), Bill M (NIST), John M (Moehrke Research), Karen W (Ready Computing), Elliott L (Harris Computing), Tarik I (InterComponentWare), Joe Lamy (SSA), Lynn F (ITI TPM)

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-ELS-Add-OnDemand-to-FindDocumentsByRefId.doc - accepted as CP 955; status is Completed
  • CP-ITI-ELS-IsSnapshotOf-redoc.doc - accepted and assigned to Elliott L as CP 956. Elliott agreed to finish proposed changes to the text based on today's discussion. The scope of this CP is also expanded to include the request for an informative UML diagram (other submitted CP below). Lynn will ask Sylvie if she can produce a diagram to accompany the improvements in text proposed by Elliot S and Elliott L.
  • CP-ITI-ELS-More-immutable-submission-set.doc - accepted as CP 957; status is Completed
  • CP-ITI-ESL_Effects_of_Merge_on_Relationship_Associates.doc - accepted as CP 958; status is Completed
  • CP-ITI-ESL_PDQ_PatientId_Audit.doc - accepted and assigned to John M as CP 959.
  • CP-ITI-ESL_SoapActionRequired_Mandatory.doc - accepted as CP 960; status is Completed
  • CP-ITI-ESL_XCDR-XDR_Cleanup.doc - accepted and assigned to Elliott L & Ken M as CP 961; Karen agreed to review the changes proposed by Elliott and Ken; if needed, will be discussed at a future CP call
  • CP-ITI-IsSnapshot-UML.doc - the request in this will be folded into the scope of CP 956 so that all 'Snapshot' changes can be reviewed together. See CP 955 in 2nd bullet above.
  • CP-ITI-KM_MU_AddMetadataParamFindDocsByRefId.doc- accepted and assigned to Ken CP 962; discussion of this CP is deferred to a future Sept CP calls focused on MU
  • CP-ITI-LF-AddPullPointRqmtsToITI-53inDSUBsupplement.doc - accepted as CP 963; status is Completed

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

  • 937-01 - DSUB Audit Msg - (Ken, Mauro) -- contents of the CP was discussed; Ken will share updated version with John via email to gain further input. CP remains Assigned.

(3) Next in CPs

  • The plan for MU CP resolution in Sep/Oct:
    • dedicate two CP calls in Sept to resolving 6 assigned MU CPs
      • Lynn will create a doodle poll to pick new dates. The regularly schedule Sept dates are problematic (Sept 2 - right before Labor Day weekend; Sept 15 - Lynn on vacation). Doodle poll will go out to key MU stakeholders (if you want to participate, send Lynn an email). Once the dates are set, the invitation to the calls will go out to ITI Tech to invite participation from all
    • MU CPs in scope for Sept discussion:
      • 559 - MPQ profile queries vs Metadata Update option - assigned to Bill
      • 756 - MPQ fixes to ensure Metadata Update compatibility - assigned to Walco
      • 765 - Metadata Update Queries with MU level not set/set to 1 - assigned to Bill
      • 785 - Patient ID Consistency in stored query responses wrt XDS metadata update - assigned to Mark Sinke
      • 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
    • Out of scope for Sept discussion:
      • 533 MU delete from Repository - this should be submitted as a new work item for 2016-17
    • ballot the newly-CompleteMU CPs late Sep to late Oct
    • Nov 1-ish, the balloted/approved CPs are ready for the implementer community for the January connectathon.
  • Ballot 36 - Lynn will make a CP ballot out of the 8 CPs in Completed status as of the end of this meeting. Will go out in the coming few days.

Agenda and Minutes from past CP calls

See: http://wiki.ihe.net/index.php/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=96642"