ITI Change Proposals 2014
Introduction
The ITI Change Proposal (CP) process follows the general IHE CP process described on the Change Proposal process page. The following sections give more detail on the general process for ITI participants involved in the CP process.
The ITI-specific CP Process
The following text explains what the process used by the ITI commitee in processing submitted CPs. It is consistent with the general IHE CP process and is informative only.
- Submission into the Incoming directory. This is typically done by directly updating the directory if you have access, otherwise an email to the ITI Technical Committee members in charge of CPs (currently Erik Pupo and Lynn Felhofer).
- First consideration by the committee. 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
- 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 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
All Change Proposal management is in ITI CP ftp site. The tracking spreadsheet can be accessed at Status directory. It is the file with the most recent date in that directory.
Integrated CPs 2014
This section will document all CPs integrated into the Version 11.0 of the Technical Framework and the 2014 version of Supplements in August 2014
Ballots
Ballot 19 (balloted in Aug 2013, comments reviewed)
Ballot 19, including ballot comments, is archived here: ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2014/CPs/Ballots/ballot-19/
CP | Title | Profile or Volumes Affected | Ballot Result |
---|---|---|---|
581-02 | DSUB correction for event ID in audit message | DSUB | Failed, see comments in archive link above |
655-02 | Modify field predicate logic for conditional fields PID-29, PID-30 (Patient Death) of IHE PAM | 2a,2b | Failed, see comments in archive link above |
657-04 | Consistency of HD and CX datatype definitions in the appendix. | 2b | Approved Final Text |
673-02 | Corrections of the usage code of some fields in segments PID, PV1, OBX, for PAM | 2b | Approved Final Text |
674-03 (updated version needed) | New option “Diagnostic Imaging Aware” for PAM to facilitate adoption by other domains (RAD, CARD, …) | 2b | Accepted for Final Text with updates from ballot comments |
681-02 | XDW Actor Definition | 1 | Accepted ballot comments; -02 was integrated into XDW in 2013 |
Assigned CPs
CP assignment
For a list of CPs as they are currently assigned see the latest CP-ITI-Tracking-201x-nn-nn.xls file in the Status directory.
Agenda and Minutes from CP discussions
All CPs call are held 9-11am Central US
Nov-21-2013
https://himss.webex.com/himss/j.php?J=922907447&PW=NMzhiZmNlYTEy
Call-in toll-free number (US/Canada): 1-866-469-3239
Call-in toll number (US/Canada): 1-650-429-3300
Access code:922 907 447
Meeting password: meeting
Agenda
(1) Incoming CPs
The following are in the Incoming directory:
- CP_ITI_RFD_documentRetrieveFormResponse.doc
- CP-ITI-App_V-WSI_Versions.doc
- CP-ITI-ATNA-Disclosure.doc
- CP-ITI-DSUB_SUPPL_Building Filter Expressions.doc
- CP-ITI-ES-Add limitedMetadata attribute optionality.doc
- CP-ITI-ES-Clarify query attribute optionality.doc
- CP-ITI-ES-Clarify submit attribute optionality.doc
- CP-ITI-ES-Correct query IG label.doc
- CP-ITI-ES-Correct XDS attribute capitalization.doc
- CP-ITI-ESL_ATNA_Typo.doc
- CP-ITI-ES-Remove XDS parentDocumentId.doc
- CP-ITI-Forcare-DEN-MimeWrappingConfusion.doc
- CP-ITI-Forcare-PDQ-NamespaceID.doc
- CP-ITI-Forcare-XDS-MU-AuditRecordTypo.doc
- CP-ITI-GL-AppndAddendumReplacment.doc
- CP-ITI-GL-DocumentRelationshipSubmissionset.doc
- CP-ITI-GL-FolderDocumentSubmissionSet.doc
- CP-ITI-rjh-fix-3881-references.doc
- CP-ITI-rjh-fix-URN.doc
- CP-ITI-SCO_TF_CSD_SUPPL_FreeBusyDescription.doc
- CP-ITI-XDS_XDSDocumentEntry.uniqueId Format is not OID (ICW).doc
- other topics tbd