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.

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 Erik Pupo and 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
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 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

Assigned CPs

CP assignment

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

9-11am Central US

https://himss.webex.com/himss/j.php?J=921161852&PW=NZDYyMzlkNTk1

Call-in toll-free number (US/Canada): 1-866-469-3239

Call-in toll number (US/Canada): 1-650-429-3300

Access code: 921 161 852

Meeting password: meeting

Agenda

(1) Upcoming schedule: There will be no CP call on Jan 2. Our next call is Jan 16. What about Jan 30 (connectathon week)?

(2) Assigned CPs ready for review: ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2014/CPs/1_Assigned/

• CP-ITI-731-00 (Elliott L) DICOM Audit Differences
• CP-ITI-732-01 (Elliott L) Update to Doc Relationship example
• CP-ITI-586-01 (Elliott L) MU typo
• CP-ITI-720-01 and pptx (Bill) Clarify Replacement for addendum and transformation docs
  • proposal to reassign from John to Bill: I (John) was involved in the email discussion, but in my case I added confusion to the email discussion bringing up the Appendix in Volume 1 that makes this even more confused. I would tend to agree with Gil that a replace on the addendum or transform should only affect those and not the parent. I just don’t have a clue if this is what Bill would agree is current fact. This item really needs to be owned by Bill.
• CP-ITI-721 - Clarify associations in different submission sets -
  • request to reassign from John M: I am not the expert here. I think the example is intended to provide an example of a submissionSet where just an association is included. The note on document-signature it isn’t a perfect example of a submissionSet that contains only an association. It is an example of a submissionSet holding a document (signature document) with an association to a document (signed document) from a different submissionSet. I can’t think of a ‘good’ example of a submissionSet with just an association. Most of the time one is submitting a new document with an association. If the point of the CP is that because the note is not a perfect example that it should be removed as an imperfect example, then I guess I don’t see the harm in removing it.
• CP-ITI-722 - Update explanation of relating a documentEntry to a Folder -
  • request to reassign from John M to Bill, Karen, Vassil or other
• CP-ITI-638-01 (Karen) Async Supplement update to Appendix V -
  • this CP is actually 'final text' but was never balloted or integrated. Need to determine whether ballot is needed, or can this just be integrated in 2014.
• CP-ITI-711 - (Karen) Add limitedMetadata attribute to optionality table -
  • from Karen: while I like the addition you made, I’m concerned that there is another category. For homeCommunityId the Registry is not REQUIRED to ignore the value, and is free to do something with it if it would like, but none is specified in the transaction. Not sure if we should add another category for “may ignore” or weaken the “I” or what.
• CP-ITI-712 - (Karen) Clarify “optional” metadata on “submission” -
  • from Karen: the limitedMetadata tag is an on/off tag, not a contents tag. If it is specified this means there is limited Metadata in the transaction. This makes it required as you have specified but NOT ALLOWED on all other transactions, since they are not allowed to carry limited metadata. Exception is XDM where it truly would be optional. We don’t have a NOT ALLOWED category so this also should be discussed.
• CP-ITI-655-04 - (Marek / Mark S) Modify field predicate logic for conditional fields PID-29, 30 Patient Death of IHE PAM

(3) Discuss email comments on 2 completed CPs: ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2014/CPs/2_Completed/

• CP-ITI-708 (Vassil's) Update Appendix V with current versions of WS-I profiles
• CP-ITI-709 (John M's) Accounting of Disclosures audit message

(4) CP Ballot 20 planning:

• Currently completed CPs are here: ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2014/CPs/2_Completed/
• Timeline PROPOSAL:
  • mm/dd/yyyy -- ballot content & spreadsheet sent to IHE USA staff (Lynn)
  • mm/dd/yyyy -- ballot sent to ITI Tech email list (Nancy)
  • mm/dd/yyyy -- ballot comments due (ITI Tech)
  • mm/dd/yyyy -- ballot comments consolidated (Lynn)
  • mm/dd/yyyy -- CP call for ballot 20 review (ITI Tech)

(5) Incoming CP review: ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2014/CPs/0_Incoming/

• bill-vol1-doc-src.doc
• bill-vol1-folders.doc
• CP-ITI-BPPCtypecode.doc
• CP-ITI-CSD-CL_default_namespaces.doc
• CP-ITI-CSD_CL-inconsistent_soap.doc
• CP-ITI-HV_otherID_parameter_description.doc
• CP-ITI-ES-Add referenceId attribute optionality.doc
• CP-ITI-ES-Clarify query attribute optionality-RESUBMITTED.doc
• CP-ITI-formatCode.doc
• CP-ITI-typeCodeVSclassCode.doc

(6) Old CPs - Motion to cancel these assigned CPs

• 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.

Minutes

(1) Upcoming schedule: There will be no CP call on Jan 2. Our next call is Jan 16.

(2) These Assigned CPs were discussed ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2014/CPs/1_Assigned/

• CP-ITI-731-00 (Elliott L) DICOM Audit Differences
• CP-ITI-732-01 (Elliott L) Update to Doc Relationship example
• CP-ITI-586-01 (Elliott L) MU typo
• CP-ITI-720-01 (Bill) Clarify Replacement for addendum and transformation docs
• CP-ITI-721 - Clarify associations in different submission sets -
• CP-ITI-722 - Update explanation of relating a documentEntry to a Folder -
• CP-ITI-638-01 (Karen) Async Supplement update to Appendix V -
• CP-ITI-711 - (Karen) Add limitedMetadata attribute to optionality table -
• CP-ITI-712 - (Karen) Clarify “optional” metadata on “submission” -

(3) Discuss email comments on 2 completed CPs: ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2014/CPs/2_Completed/

• CP-ITI-708 (Vassil's) Update Appendix V with current versions of WS-I profiles
• CP-ITI-709 (John M's) Accounting of Disclosures audit message

(4) CP Ballot 20 planning:

• Currently completed CPs are here: ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2014/CPs/2_Completed/
• This is the timeline:
  • mm/dd/yyyy -- ballot content & spreadsheet sent to IHE USA staff (Lynn)
  • mm/dd/yyyy -- ballot sent to ITI Tech email list (Nancy)
  • mm/dd/yyyy -- ballot comments due (ITI Tech)
  • mm/dd/yyyy -- ballot comments consolidated (Lynn)
  • mm/dd/yyyy -- CP call for ballot 20 review (ITI Tech)

(5) These incoming CPs were reviewed:

• bill-vol1-doc-src.doc
• bill-vol1-folders.doc
• CP-ITI-BPPCtypecode.doc
• CP-ITI-CSD-CL_default_namespaces.doc
• CP-ITI-CSD_CL-inconsistent_soap.doc
• CP-ITI-ES-Add referenceId attribute optionality.doc
• CP-ITI-ES-Clarify query attribute optionality-RESUBMITTED.doc
• CP-ITI-formatCode.doc
• CP-ITI-typeCodeVSclassCode.doc

(6) Old CPs - Motion to cancel these assigned CPs

• CP-ITI-496 (John M) - ATNA secure communications option
• CP-ITI-514 (John M) - Correct conflict in node authentication requirements

Jan-16-2014

9-11am Central US