ITI Change Proposals 2009: Difference between revisions

From IHE Wiki
Jump to navigation Jump to search
← Older editNewer edit →
Witting (talk | contribs)
editor
1,865 edits
Witting (talk | contribs)
editor
1,865 edits
Line 136: Line 136:
* XDS Metadata
* XDS Metadata
** [ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2009/CPs/Assigned/CP-ITI-188-01.doc CP-ITI-188-01.doc] Bill: XDSFolder.codelist inconsistent
** [ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2009/CPs/Assigned/CP-ITI-188-01.doc CP-ITI-188-01.doc] Bill: XDSFolder.codelist inconsistent
** [ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2009/CPs/Assigned/CP-ITI-259-00.doc CP-ITI-259-00.doc] Bill: parentDocumentRelationship (parentDocumentId) is unclear
*** [ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2009/CPs/Assigned/CP-ITI-259-00.doc CP-ITI-259-00.doc] Bill: parentDocumentRelationship (parentDocumentId) is unclear
** [ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2009/CPs/Assigned/CP-ITI-296-00.doc CP-ITI-296-00.doc] Bill: Improve Submission Set Description
*** [ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2009/CPs/Assigned/CP-ITI-296-00.doc CP-ITI-296-00.doc] Bill: Improve Submission Set Description
** [ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2009/CPs/Assigned/CP-ITI-314-00.doc CP-ITI-314-00.doc] Bill: XDS Folder Entry Identifiers
** [ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2009/CPs/Assigned/CP-ITI-314-00.doc CP-ITI-314-00.doc] Bill: XDS Folder Entry Identifiers
** [ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2009/CPs/Assigned/CP-ITI-316-05.doc CP-ITI-316-05.doc] Bill: Add Unique Identifier Slot for (planned discussion for 10/3)
** [ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2009/CPs/Assigned/CP-ITI-316-05.doc CP-ITI-316-05.doc] Bill: Add Unique Identifier Slot for (planned discussion for 10/3)
** [ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2009/CPs/Assigned/CP-ITI-351-02.doc CP-ITI-351-02.doc] Bill: Nested Folders
** [ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2009/CPs/Assigned/CP-ITI-351-02.doc CP-ITI-351-02.doc] Bill: Nested Folders
** [ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2009/CPs/Assigned/CP-ITI-352-04.doc CP-ITI-352-04.doc] Bill: Adding folders by reference to Submission Set
** [ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2009/CPs/Assigned/CP-ITI-352-04.doc CP-ITI-352-04.doc] Bill: Adding folders by reference to Submission Set
** [ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2009/CPs/Assigned/CP-ITI-359-00.doc CP-ITI-359-00.doc] Bill: XDS document relations in a single submission set
*** [ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2009/CPs/Assigned/CP-ITI-359-00.doc CP-ITI-359-00.doc] Bill: XDS document relations in a single submission set
** [ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2009/CPs/Assigned/CP-ITI-385-00.doc CP-ITI-385-00.doc] Bill: Create XDS Metadata Model
** [ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2009/CPs/Assigned/CP-ITI-385-00.doc CP-ITI-385-00.doc] Bill: Create XDS Metadata Model
* Registry Stored Query
* Registry Stored Query
** [ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2009/CPs/Assigned/CP-ITI-361-02.doc CP-ITI-361-02.doc] Bill: New Stored Query  
** [ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2009/CPs/Assigned/CP-ITI-361-02.doc CP-ITI-361-02.doc] Bill: New Stored Query  
* XDS.a
* XDS.a
** [ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2009/CPs/Assigned/CP-ITI-318-00.doc CP-ITI-318-00.doc] Bill: Query Example Typo
*** [ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2009/CPs/Assigned/CP-ITI-318-00.doc CP-ITI-318-00.doc] Bill: Query Example Typo
* XDS.b
* XDS.b
** None
** None
Line 157: Line 157:
* XCA
* XCA
** [ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2009/CPs/Assigned/CP-ITI-383-00.doc CP-ITI-383-00.doc] Karen: XCA return home in error messages
** [ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2009/CPs/Assigned/CP-ITI-383-00.doc CP-ITI-383-00.doc] Karen: XCA return home in error messages
** [ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2009/CPs/Assigned/CP-ITI-384-00.doc CP-ITI-384-00.doc] Karen: Adding homeCommunityId information into NAV message
*** [ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2009/CPs/Assigned/CP-ITI-384-00.doc CP-ITI-384-00.doc] Karen: Adding homeCommunityId information into NAV message
** [ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2009/CPs/Assigned/CP-ITI-389-00.doc CP-ITI-389-00.doc] Karen: Responding Gateway requires two WSDL endpoints
** [ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2009/CPs/Assigned/CP-ITI-389-00.doc CP-ITI-389-00.doc] Karen: Responding Gateway requires two WSDL endpoints
* Web Services
* Web Services

Revision as of 08:43, 29 January 2009

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
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
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 TBD XDS-SD

Assigned CPs

CP's waiting for Ballot

See Ballot 1

CP's to be addressed in whitepaper/supplement

Organized by technical area

Agenda and Minutes from CP discussions

January 27, 2009

Agenda

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

Minutes



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=29826"