Difference between revisions of "ITI Change Proposals 2014"
Jump to navigation
Jump to search
| Line 242: | Line 242: | ||
== Jan-16-2014 == | == Jan-16-2014 == | ||
| − | |||
| − | + | Agenda and minutes are here: http://wiki.ihe.net/index.php?title=ITI_CPs_2014-01-16 | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
== Feb-6-2014 == | == Feb-6-2014 == | ||
Revision as of 09:51, 3 February 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.
- Write a change proposal. Here is IHE's Change_Proposal_Template
- 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 Erik Pupo and Lynn Felhofer).
- 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.
- 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 done 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 | Approved for Final Text with updates from ballot comments |
| 681-02 | XDW Actor Definition | 1 | Accepted ballot comments; -02 was integrated into XDW in 2013 |
Ballot 20 (out for review Jan 7 - Feb 7, 2014)
Ballot 20 is archived here: ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2014/CPs/Ballots/ballot-20
| CP | Title | Profile | Vol | Ballot Result |
|---|---|---|---|---|
| CP-ITI-515-02 | Correct hyperlinks to point to TF sections | XUA | 1 | |
| CP-ITI-586-01 | MU Typo | MU | 2b | |
| CP-ITI-638-01 | Async Supplement update to Appendix V | Async | 2x | |
| CP-ITI-660-03 | XCPD diagram shows single when should be multiple | XCPD | 2b | |
| CP-ITI-672-01 | mustUnderstand | many | 2x | |
| CP-ITI-678-00 | Correction of the example illustrating the URL of Find document Dossiers message | MHD | 2c | |
| CP-ITI-687-03 | Use referralIdList as specified by CP-ITI-659 instead of folders in XDW | XDW | 1,3 | |
| CP-ITI-690-05 | Document Sharing Metadata Enhancement for Security/Privacy Tags | XD* | 3 | |
| CP-ITI-707-00 | Document Retrieve Form Response | RFD | 2b | |
| CP-ITI-708-01 | Update Appendix V with current versions of WS-I profiles | many | 2x | |
| CP-ITI-713-00 | Correct labelling of XCA IG in query attribute optionality | XCA | 3 | |
| CP-ITI-714-00 | Correct capitalization of Document Sharing Attribute names | XD* | 3 | |
| CP-ITI-715-00 | Remove parentDocument references | XDS | 3 | |
| CP-ITI-717-00 | Incorrect section reference | ATNA | 2a | |
| CP-ITI-718-00 | Namespace ID required even if ISO OID set | PDQv2, PAM | 2x | |
| CP-ITI-719-00 | Typo in audit message for Document Registry/Recipient in Metadata Update supplement | MU | 2b | |
| CP-ITI-729-00 | Typo in FacilityServices | CSD | 2x | |
| CP-ITI-730-00 | Limited Metadata Audit | XDS | 2b | |
| CP-ITI-731-00 | DICOM Audit Differences | ATNA, many | 2a | |
| CP-ITI-736-00 | clarification of BPPC typeCode | BPPC | 3 | |
| CP-ITI-737-00 | clarification of classCode from typeCode | XD* | 3 |
Assigned CPs
For a list of CPs that are currently assigned see the latest CP-ITI-Tracking-201x-nn-nn.xls file in the Status directory.
Agenda and Minutes from CP discussions
ITI CP review calls are held the 1st and 3rd Thursday of each month from 9-11am Central US.
Nov-21-2013
Agenda and minutes are here: http://wiki.ihe.net/index.php?title=ITI_CPs_2013-11-21
Dec-5-2013
Agenda and minutes are here: http://wiki.ihe.net/index.php?title=ITI_CPs_2013-12-05
Dec-19-2013
Agenda and minutes are here: http://wiki.ihe.net/index.php?title=ITI_CPs_2013-12-19
Jan-16-2014
Agenda and minutes are here: http://wiki.ihe.net/index.php?title=ITI_CPs_2014-01-16
Feb-6-2014
9-11am Central US
https://himss.webex.com/himss/j.php?J=928131590&PW=NNmIwZDZhNzhh
1-866-469-3239
meeting number: 928 131 590
meeting password: meeting
Agenda
...this agenda is under revision until Feb 5
(1) Review Incoming CPs ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2014/CPs/0_Incoming/
- bill-vol1-doc-scr.doc
- bill-vol1-folders.doc
...
(2) Assigned CPs for discussion ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2014/CPs/1_Assigned/
- CP-ITI-685 - (Christian Ohr with input from HPD implementers) - HPD Error Codes
...
(3) Old CPs - Motion to cancel these assigned CPs (deferred from 12/19 & 1/14 calls)
- CP-ITI-496 (John M) - ATNA secure communications option
- I am unsure that this is still wanted. It is also a very radical change that would affect “IHE Integration Statements”, be even worse for Gazelle. Given that this is many years old. I think it might be best to cancel it and see if it comes back up again. Reality is that today this is happening through non-stated means. Not a great idea, but reality. I think a solution that would be more accepted would be to write a new profile that was just the audit logging. I would rather see that submitted as a profile proposal. It might be one as small as CT. But it would likely get to what people want (audit without mandatory secure-communications). – Motion to cancel
- CP-ITI-514 (John M) - Correct conflict in node authentication requirements
- I think we solved this a long time ago with other broad ATNA rewrites. I certainly don’t think I could track down the meaning of the comments in the CP document. – Motion to cancel
- CP-ITI-581 (John M) - Correct DSUB audit messages
- this seems to want us to take the current ITI-18 audit log messages and make them DSUB. But DSUB is not the same thing as ITI-18. I think the current DSUB audit messages are appropriate, and would not agree with the CP. Motion to cancel.
Feb-20-2014
9-11am Central US
Agenda
(1) CP Ballot 20 - review ballot comments