ITI Change Proposals 2010
Introduction
The ITI 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 via an email to the ITI Technical Committee co-chair in charge of CPs (currently Karen Witting) or by directly updating the directory if you have access to the ftp write password.
- 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 invoved are:
- Assigned
- contains CPs that have been assigned an editor and are being actively worked on by the committee, i.e. Assigned status
- Ballots
- contains Ballots that have been released for voting by the general community
- Canceled
- contains CPs that have been canceled, i.e. Canceled 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.
- FinalText/Integrated
- contains the version of the CP that was integrated into the TF.
- 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.
- old_versions
- Contains old versions of Completed and FinalText CPs
- Rejected
- CPs that have been submitted by rejected by the committee
- Status
- contains spreadsheets describing the status of CPs.
Archived Change Proposal pages
Ongoing work on CPs is placed on the current year CP page. Prior years work can be accessed at:
ITI CP Tracking
All Change Propoposal 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
These CPs have been integrated into the Version 6.0 of the Technical Framework and the 2009 version of Supplements.
CP | Title | Profiles Affected | Date |
---|---|---|---|
TBD | TBD | TBD | TBD |
Final Text CPs
These CPs are ready for integration into the Technical Framework and Supplements.
CP | Title | Profiles Affected |
---|---|---|
188 | XDSFolder.codelist inconsistent | XDS |
308 | PDQv3 specify what fuzzy search means | PDQV3 |
310 | Assign profile #s to PIXV3 and PDQV3 | PIXV3 / PDQV3 |
364 | Make query continuations optional | PDQV3 |
377 | XDR Doc Recipient not documented in ITI-41 | XDR |
398 | BPPC clarification of terms | BPPC |
403 | ATNA Encoding of Query Content | PIX, PDQ, XDS |
405 | BPPC clarification of consent template | BPPC |
406 | BPPC codes | BPPC |
413 | XDS Metadata SHA1 encoding | XDS |
415 | XDS Stored Queries of non-patient returning different patients | XDS |
417 | ATNA SYSLOG-Protocol | ATNA |
418 | XDS Remove Query Column From XDS(.b) Metadata tables | XDS |
419 | Clarify repositoryUniqueId and URI may be rejected by Repository | XDS |
420 | XCA Remove WS-Adressing action for Asynchronous Web Services Exchange | Async, XCA, XCPD |
424 | More lost XDS Off-line mode text | XDS |
427 | ATNA: ITI 14: Source UserID of ATNA message is not specialized, but required | XDS.b |
429 | ATNA: ITI-18 Consumer: HomeCommunityID cannot be set in the defined way | XDS.b |
431 | Clean up references to ATNA Encryption option | ATNA |
432 | Clean up NAV dependencies table | NAV |
434 | Volume 2 Appendix Cleanup | XDS |
439 | Missing formatCodeDisplayName in document metadata table | XDS |
441 | ATNA ParticipantObjectDetail use not well-defined | BPPC, XDS-SD |
444 | Update XCA to reflect udpates to referenced text/profiles | XCA |
445 | Description of SOAP faults in RFD is based on wrong SOAP version | RFD |
446 | Missing transaction for ATNA Secure Node | ATNA |
447 | Patient ID param formatting | MPQ |
448 | Clarify Options for BPPC | BPPC |
449 | Delete out-of-date note in ITI-41 | XDS.b |
Completed CPs
Ballot 5 CPs
Note: Ballot 5 is expected to be released January 2010.
CP | Title | Profiles Affected |
---|---|---|
TBD | TBD | TBD |
Assigned CPs
CP assignment
For a list of CPs as they are currently assigned see the latest CP-ITI-Tracking-2010-nn-nn.xls file in the Status directory.
Agenda and Minutes from CP discussions
January 8, 2010
Agenda
- 442-01 Ready to Review - Yongjian
- 433-02 Ready to Review - Yongjian
- 477-01 Ready for Review - Rob
- 440-01 High Accuracy SNTP - Rob
- 435-02 Ready for Ballot - Karen
- 468-01 Ready for Ballot - Karen
- 469-01 Ready for Ballot - Karen
- 450-02 Ready to Review - Karen
- 461-01 Ready for Review - Karen
- 472-01 Ready for Review - Karen
- Incoming
Minutes
TBD