ITI Change Proposals 2009

From IHE Wiki
Jump to navigation Jump to search

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.

  1. 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.
  2. 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.
  3. Committee works with editor to draft the CP. Versions are kept in Assigned directory and numbered -00, -01, -02, etc.
  4. Committee decides CP is ready for ballot. Latest version of CP is moved to Completed diretory and old versions are moved to old_versions.
  5. Co-chair collects Completed CPs into a ballot. The Ballot directory will be used for this.
  6. Ballot is released to the general community for voting
  7. 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.
  8. 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 5.0 of the Technical Framework and the 2008 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
TBD TBD TBD

Completed CPs

Ballot 1 CPs

CP Title Profiles Affected
296 Improve Submission Set Description XDS
318 Query Example Typo XDS.a
359 XDS document relations in a single submission set XDS
379 Profile dependencies (grouping) inconsistencies Many
380 BPPC Patient Patient Privacy Enforcement option is missing for the Integ. Doc Source / Rep actor BPPC, XDS.a, XDS.b
381 homeCommunityId needs definitition in metadata tables XCA, XDS.b
382 Clarify HL7 v2 Z-Segment Usage Statement Appendix
384 Adding homeCommunityId information into NAV message XCA, NAV
387 Remove central from definition of PDQ PDQ, PDQV3
388 Unclear what error should result when Retrieve Document Set specifies an unknown uniqueID XDS.b
390 Document Registry is mentioned in PDO, but no rqmts in Vol 1 material PDO
392 SNTP reference CT
394 XCA and XDS.b ATNA Logging Enhancements XDS.b, XCA
396 XDS-SD Duplicate Option XDS-SD

Assigned CPs

CPs to be addressed in whitepaper or supplement

Organized by technical area

  • XDS Metadata
    • CP-ITI-188-01.doc Bill: XDSFolder.codelist inconsistent
      • 1/29 discussion planned for March 4
    • CP-ITI-259-00.doc Bill: parentDocumentRelationship (parentDocumentId) is unclear
      • 1/29 editing work needed and confirmation from submittor on suggested resolution
    • CP-ITI-314-00.doc Bill: XDS Folder Entry Identifiers
      • 1/29 Bill to query Keith if this is still needed
    • CP-ITI-316-05.doc Bill: Add Unique Identifier Slot for (planned discussion for 10/3)
      • 1/29 Email discussion among sarah, bill, mark, discuss march 18
    • CP-ITI-351-02.doc Bill: Nested Folders
      • 1/29 discussion planned March 4
    • CP-ITI-352-04.doc Bill: Adding folders by reference to Submission Set
      • TBD
    • CP-ITI-385-00.doc Bill: Create XDS Metadata Model
      • TBD
    • Registry Stored Query
    • CP-ITI-361-02.doc Bill: New Stored Query
      • 1/29 direction identified, editing needed
  • XDM
    • CP-ITI-356-00.doc Rob: XDM – Metadata file digitally signed
      • 1/29 plan to discuss March 4
    • CP-ITI-368-00.doc Rob: SMTP clarifications for XDS.a and XDM
      • 1/29 plan to discuss March 4
  • XDR
    • CP-ITI-377-00.doc Charles: XDR Doc Recipient not documented in ITI-41
      • 1/29 waiting for Charles to write up
  • XCA
    • CP-ITI-383-00.doc Karen: XCA return home in error messages
      • 1/29 plan to discuss March 18
    • CP-ITI-389-00.doc Karen: Responding Gateway requires two WSDL endpoints
      • 1/29 plan to discuss March 18
  • Web Services
    • CP-ITI-363-02.doc Sarah: Web Services Parameter Nomenclature
      • 1/29 plan to discuss April 29
  • BPPC
  • DSG
  • NAV
    • CP-ITI-395-00.doc Rob: Adding FolderId information into NAV message
      • 1/29 waiting for text to be written
    • CP-ITI-397-00.doc Lynn: Clarification on NAV sendAcknowledgementTo
      • TBD
  • PIX/PDQ V2
    • CP-ITI-211-03.doc Yongjian: PIX/PAM Integration
      • Being addressed through the HL7 task force re-write of Appendix C
    • CP-ITI-307-00.doc Vassil: PDQ Continuation Protocol in One Socket or Multiple Sockets
      • 1/29 Will be integrated into the Appendix C re-write
  • PIX/PDQ V3
    • CP-ITI-308-00.doc Vassil: PDQv3 specify what fuzzy search means
      • 1/29 plan to discuss April 15
    • CP-ITI-310-00.doc Vassil: Assign profile #s to PIXV3 and PDQV3
      • 1/29 Plan to discuss March 18
    • CP-ITI-364-00.doc Vassil: Make query continuations optional
      • 1/29 plan to discuss April 15
    • CP-ITI-376-00.doc Vassil: extend PIXV3/PDQV3 R-MIM
      • 1/29 plan to discuss April 15
  • PDO
    • CP-ITI-391-00.doc Alean: What does R2 mean for a PIX Manager
      • 1/27 Direction discussed, Alean to write up text
    • CP-ITI-400-00.doc Alean: Last Update Date/Time for v3 msgs with PDO option
  • PWP
    • CP-ITI-365-00.doc John: Required/optional attributes in PWP
      • Email correspondance with submittor, plan to discuss April 1

Agenda and Minutes from CP discussions

April 29, 2009

Agenda


Minutes



April 15, 2009

Agenda


Minutes



April 1, 2009

Agenda


Minutes



March 18, 2009

Agenda


Minutes



March 4, 2009

Agenda


Minutes



January 27-29, 2009

Agenda

  • CP Ballot release planned Feb 11
  • Plan tcons
  • CPs to review
  • incoming
    • CP-ITI-VDP-XCA_Meta_Data.doc

Minutes

January 27

  • CP-ITI-KW-GroupingNotTestable-00.doc
    • Lengthy discussion of changing XCA to use options instead of grouping. No strong consensus on the change. Decided to reject the CP in favor of fixing the connectathon testing process.
  • CP-ITI-JFM_BPPC_Clarrification_of_terms
    • assign to john 398
  • CP-ITI-JFM_CT_SNTP
    • duplicate submission
  • CP-ITI-JFM_DSG_title_page
    • assign to john 399
  • ITI_LF_PDO-last_upd_datetime_v3
    • assign to Alean 400
  • CP-ITI-391-00.doc Alean: What does R2 mean for a PIX Manager
    • a recommendation for how to address the concern was discussed and Alean will document that recommendation

January 28

  • CP-ITI-259-01.doc Bill: parentDocumentRelationship (parentDocumentId) is unclear
    • Fix editor instructions and verify with Sarah
  • CP-ITI-296-01.doc Bill: Improve Submission Set Description
    • Ready for ballot
  • CP-ITI-318-01.doc Bill: Query Example Typo
    • Fix bolded 350 (remove it) and then ready for ballot
  • CP-ITI-359-01.doc Bill: XDS document relations in a single submission set
    • Agreed, ready for ballot with minor fix
  • CP-ITI-384-02.doc Karen: Adding homeCommunityId information into NAV message
    • Wordsmithing to include shall, ready for ballot

January 29

  • CP-ITI-361-02.doc Bill: New Stored Query
    • Concern with this query that pulling multiple objects require that all objects be associated with the same patient. This restriction should apply to the existing queries as well as this proposed new one. Bill will submit a new CP to add the restriction to the existing queries for multiple objects and then update this query to have the same language.
  • CP-ITI-VDP-XCA_Meta_Data.doc
    • Use case can be addressed through a special code that identifies documents a potential rather than already existing. Would put new requirements on a Responding Gateway that supports this after retrieve of potential document. Given nature of the change will be done through a late season white paper started in June 2009. Assigned to Karen as CP 401.



January 22, 2009

Agenda

Goal, prepare CPs for ballot in February 2009

  • CPs continued from last call
    • CP-ITI-314-00.doc Bill: XDS Folder Entry Identifiers
      • Bill to query Keith
    • CP-ITI-359-00.doc Bill: XDS document relations in a single submission set
      • Bill to write text
    • CP-ITI-381-02.doc Karen: homeCommunityId needs definitition in metadata tables
      • Updated text available to review
    • CP-ITI-384-02.doc Karen: Adding homeCommunityId information into NAV message
      • Updated text available to review
    • CP-ITI-388-01.doc Karen: Unclear what error should result when Retrieve Document Set specifies an unknown uniqueID
      • Updated text available to review
    • CP-ITI-394-03.doc John: XCA and XDS.b ATNA Logging Enhancements
      • Updated text available to review
  • CPs ready to review
    • CP-ITI-393-00.doc George: Extend the support for encodedResponse to the HTTP Get and HTTP Post transport methods
  • CPs for discussion
  • incoming
    • CP_ITI_LF_duplicate_options_row.doc
    • CP_ITI_LF_NAV_sendAcknowledgementId.doc
    • cp-iti-bill-rep_return_size_hash - use case from Bill (or reject)
    • cp-iti-bill-repositoryUniqueId.doc
    • CP-ITI-JFM_BPPC_Clarrification_of_terms
    • CP-ITI-JFM_CT_SNTP
    • CP-ITI-JFM_DSG_title_page
    • CP-ITI-JMG_Extend_the_use_of_encodedResponse
    • CP-ITI-KW-GroupingNotTestable-00.doc
    • IHE_Change_Proposal-XUA
    • ITI_LF_PDO-last_upd_datetime_v3
  • Planning for f2f CP discussions (see Assigned CPs for list of CPs organized by technical area.)
    • Alean - 1
    • Bill - 14
    • Charles - 1
    • George - 3
    • John - 2
    • Karen - 5
    • Rob - 3
    • Vassil - 5
    • Yongjian - 1

Minutes


  • CP-ITI-314-00.doc Bill: XDS Folder Entry Identifiers
    • Bill to query Keith (still TBD)
  • CP-ITI-359-00.doc Bill: XDS document relations in a single submission set
    • Bill to write text (still TBD, waiting for a block of CPs to work on)
  • CP-ITI-381-02.doc Karen: homeCommunityId needs definitition in metadata tables
    • Ready for ballot
  • CP-ITI-384-02.doc Karen: Adding homeCommunityId information into NAV message
    • Defer for review at f2f
  • CP-ITI-388-01.doc Karen: Unclear what error should result when Retrieve Document Set specifies an unknown uniqueID
    • Ready for ballot
  • CP-ITI-394-02.doc John: XCA and XDS.b ATNA Logging Enhancements
    • Ready for ballot - Lynn will communicate requirement to connecatathon participants. Plan for CP Ballot second week in Feb.
  • CP-ITI-393-00.doc George: Extend the support for encodedResponse to the HTTP Get and HTTP Post transport methods
    • Incorporate this requirement into the revisions planned for RFD in the 2009 cycle. Some ad-hoc testing at connectathon discussed and discussions will continue at RFD specific connecatathon/HIMSS meetings.
  • CP-ITI-361-02.doc Bill: New Stored Query
    • Discussion needed with Rob and John - defer to f2f
  • CP-ITI-259-00.doc Bill: parentDocumentRelationship (parentDocumentId) is unclear
    • Bill to work up some language for us to review
  • CP-ITI-296-00.doc Bill: Improve Submission Set Description
    • cleanup of terms needed - Bill to prepare text
  • CP-ITI-358-00.doc Bill: Author semantics on documents and submission sets
    • Cancel - information moved to implementors guide
  • CP_ITI_LF_duplicate_options_row.doc
    • Ready for ballot, assign to Lynn
  • CP_ITI_LF_NAV_sendAcknowledgementId.doc
    • Assign to Lynn
  • cp-iti-bill-rep_return_size_hash - use case from Bill (or reject)
    • Reject - no compelling use case can be identified
  • cp-iti-bill-repositoryUniqueId.doc
    • Reject - value is defined in XDS.b
  • CP-ITI-JFM_BPPC_Clarrification_of_terms
    • Defered to f2f
  • CP-ITI-JFM_CT_SNTP
    • Defered to f2f
  • CP-ITI-JFM_DSG_title_page
    • Defered to f2f
  • CP-ITI-JMG_Extend_the_use_of_encodedResponse
    • Mistakenly left in incoming, needs to be deleted
  • IHE_Change_Proposal-XUA
    • Reject - duplicate with changes from 2008.
  • ITI_LF_PDO-last_upd_datetime_v3
    • Defer for f2f when Alean is available


January 9, 2009

Agenda

Goal, prepare CPs for ballot in February 2009

  • CPs ready to review
  • CPs waiting for Ballot
  • incoming
    • CP Forcare PDQ PIX Acknowledgment Code Inconsistency
    • CP_ITI_DSG_Folder_DSG
    • CP_ITI_NAV_folder
    • cp-iti-bill-rep_return_size_hash
    • CP-ITI-JFM_BPPC_Clarrification_of_terms
    • CP-ITI-JFM_CT_SNTP
    • CP-ITI-JFM_DSG_title_page
    • CP-ITI-JMG_Extend_the_use_of_encodedResponse
    • IHE_Change_Proposal-XUA
    • ITI_LF_PDO-last_upd_datetime_v3

Minutes


  • CP-ITI-314-00.doc Bill: XDS Folder Entry Identifiers
    • The committee is unsure whether this requirement is still needed. Bill will ask Keith.
  • CP-ITI-359-00.doc Bill: XDS document relations in a single submission set
    • This is just some clarifications needed, no technical change to requirements. Bill will write text.
  • CP-ITI-379-00.doc Lynn: Profile dependencies (grouping) inconsistencies
    • Move TI supplement updates out of TF update and into supplement text. Then ready for ballot. Suggests perhaps a template update which points out that supplements should be considering updating the table when they include dependencies.
  • CP-ITI-380-00.doc Lynn: BPPC Patient Patient Privacy Enforcement option is missing for the Integ. Doc Source / Rep actor
    • Check section reference for Doc Source of XDS.b. Then ready for ballot.
  • CP-ITI-381-01.doc Karen: homeCommunityId needs definitition in metadata tables
    • Change definition to be simply a unique id of community. Add TF-2 to references.
  • CP-ITI-384-01.doc Karen: Adding homeCommunityId information into NAV message
    • Add a new identifier homeCommunityId that is R2. Editing work followed by second review.
  • CP-ITI-386-00.doc Bill: SQ Bad Param
    • Cancel, recommend use of RegistryError in this case.
  • CP-ITI-388-00.doc Karen: Unclear what error should result when Retrieve Document Set specifies an unknown uniqueID
    • Security concern that we should not distinguish between doesn't exist and not authorized. Verify that these two problems are reflected in the same way, and update description to include both.
  • CP-ITI-390-01.doc Lynn: Document Registry is mentioned in PDO, but no rqmts in Vol 1 material
    • Ready for ballot.
  • CP-ITI-393-00.doc George: Extend the support for encodedResponse to the HTTP Get and HTTP Post transport methods
    • Ran out of time
  • CP-ITI-394-00.doc John: XCA and XDS.b ATNA Logging Enhancements
    • The audit message for retrieve document set was over-simplified so that its reuse by XCA was a problem. John will write up and distribute to be considered for connectathon.
  • incoming
    • CP Forcare PDQ PIX Acknowledgment Code Inconsistency
      • Apppendix C is planning to be re-written. Proposal is to include a proper definition of AE & AR in appendix C as a response to this request. Recommend including this changes as part of the appendix C changes. Karen to request Yongjian to open a CP to track the work on the appendix C and reject this CP as a duplicate of that larger CP.
    • CP_ITI_DSG_Folder_DSG
      • No strong use case for this right now so reject.
    • CP_ITI_NAV_folder
      • Assign to Rob - resolution is to put folder id in the signatureproperty as an informative value.
    • cp-iti-bill-rep_return_size_hash
      • Bill will review. Reject on next call unless compelling use case available.
    • The following were not reviewed because we ran out of time
      • CP-ITI-JFM_BPPC_Clarrification_of_terms
      • CP-ITI-JFM_CT_SNTP
      • CP-ITI-JFM_DSG_title_page
      • CP-ITI-JMG_Extend_the_use_of_encodedResponse
      • IHE_Change_Proposal-XUA
      • ITI_LF_PDO-last_upd_datetime_v3


Retrieved from "http://wiki.ihe.net/index.php?title=ITI_Change_Proposals_2009&oldid=30048"