Proposed Work Item Title: Maintenance of ITI Profiles Published in 2015 and earlier Proposal Editor: Lynn Felhofer Work item “workers”: members of the ITI Technical Committee Date: September 17, 2015 Domain: ITI

The Problem A dedicated but finite number of ITI Technical Committee members is responsible for both creating new work items and maintaining the growing list of existing documents: PUBLISHED DOCUMENTS: In Fall 2015, the IT Infrastructure Domain has: 23 Final Text Profiles 15 Trial Implementation Profiles 5 additional Trial Implementation Supplements that modify existing profiles white papers are not accounted for in this proposal

The Problem (cont.) CHANGE PROPOSALS: The IT Infrastructure Domain applies significant Technical Committee resources to processing Change Proposals, but we are not making progress in reducing the backlog. We are publishing more new TI supplements every year than we move to Final Text. Two regular 2-hour Change Proposal t-conns per month stats: 78 new CPs submitted 5 CP ballots process resulting in 76 approved CPs integrated into TF documents 2 TI supplements moved from TI to Final Text: XCPD, On Demand Docs For the Aug/Sep 2014 cycle, the committee produced and Mary Jungers processed 14 Final Text volumes & TI Supplements that were modified by CPs stats: 89 new CPs submitted 5 CP ballots resulting in 59 approved CPs integrated into TF documents 1 TI supplement moved from TI to Final Text: XDW For Aug/Sep 2015 cycle, the committee produced and Mary Jungers processed 21 (21!) Final Text volumes & TI Supplements that were modified by CPs

95 assigned CPs (vs 84 on Sep 18) CP Backlog (as of Oct 19) Currently 95 assigned CPs (vs 84 on Sep 17). General breakdown: Includes one CP per profile for the DSTU2 update

Impact on Shared Resources TOOL DEVELOPERS: proliferation of Profiles across domains means that our tool developers cannot keep up. They are asked to: develop tools for new profiles enhance existing tools to support Conformity Assessment perform regular maintenance on existing tools See: TF PUBLICATION (ie Mary Jungers) DOMAIN Co-CHAIRS

Discussion Goal: Identify Maintenance as a Work Item Assign a % of Technical Committee resources to the effort CPs *and* review of updated TF & TI Supplements When other work items are selected and an editor is assigned, consider the impact on editor’s maintenance items (ie what CPs will be sacrificed in order to get the new work done) “An ounce of prevention…” Identify & implement actions to prevent future CPs More t-conns prior to PC & TI F2F to bring a more mature doc to the table? Identify dedicated reviewers for each work item? Ask IHE for expanded TPM support? Others? Make a push to get TI Supplements to Final Text Challenge: Even if this work item is accepted, TC members with the needed expertise may not be available to do the work

Questions? Concerns?