Difference between revisions of "ITI Change Proposals 2008"

From IHE Wiki
Jump to navigation Jump to search
Line 139: Line 139:
 
** [ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2007-2008/CPs/Assigned/CP-ITI-275-00.doc CP-ITI-275-00.doc] Can we re-use XDS.b transactions rather than declare new ones for XCA?
 
** [ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2007-2008/CPs/Assigned/CP-ITI-275-00.doc CP-ITI-275-00.doc] Can we re-use XDS.b transactions rather than declare new ones for XCA?
 
* George CPs - mostly RFD CPs
 
* George CPs - mostly RFD CPs
−
** [ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2007-2008/CPs/Assigned/CP-ITI-272-00.doc CP-ITI-272-00.doc] Clarify actions of the Form Manager when it receives Retrieve Clarification transaction
+
** [ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2007-2008/CPs/Assigned/CP-ITI-272-01.doc CP-ITI-272-01.doc] Clarify actions of the Form Manager when it receives Retrieve Clarification transaction
−
** [ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2007-2008/CPs/Assigned/CP-ITI-285-00.doc CP-ITI-285-00.doc]  RFD – Requests for Clarification to Profile text
+
** [ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2007-2008/CPs/Assigned/CP-ITI-285-01.doc CP-ITI-285-01.doc]  RFD – Requests for Clarification to Profile text
−
** [ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2007-2008/CPs/Assigned/CP-ITI-286-00.doc CP-ITI-286-00.doc] Repository should overwrite repositoryUniqueId if it is in metadata
+
** [ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2007-2008/CPs/Assigned/CP-ITI-286-01.doc CP-ITI-286-01.doc] Repository should overwrite repositoryUniqueId if it is in metadata
 
* John, Rob, Manuel - mostly Security CPs
 
* John, Rob, Manuel - mostly Security CPs
 
** [ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2007-2008/CPs/Assigned/CP-ITI-273-00.doc CP-ITI-273-00.doc] John: Fix Options descriptions in the BPPC profile
 
** [ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2007-2008/CPs/Assigned/CP-ITI-273-00.doc CP-ITI-273-00.doc] John: Fix Options descriptions in the BPPC profile
Line 191: Line 191:
 
** XDR use of SOAP with attachments - is it completed converted to MTOM use?
 
** XDR use of SOAP with attachments - is it completed converted to MTOM use?
 
** CP-ITI-AXO_PDQv3_specify_fuzzy_search.doc
 
** CP-ITI-AXO_PDQv3_specify_fuzzy_search.doc
−
 
  
 
== March 11, 2008 ==
 
== March 11, 2008 ==

Revision as of 08:24, 12 March 2008

Introduction

See Change Proposal process page.

Return to ITI Technical Committee

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.


Directory Structure

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.

Integrated CPs

These CPs have been integrated into the Version 4.0 of the Technical Framework and the 2007 version of Supplements.

CP Title Profiles Affected Date
TBD TBD TBD August 2008 (expected)

Canceled CPs

These CPs have been canceled.

CP Title Profiles Affected Date Reason
CP-ITI-290-00.doc XDS Document Relationship Model XDS March 7, 2008 Duplicate of 263

Final Text CPs

These CPs are ready for integration into the Technical Framework and Supplements.

CP Title Profiles Affected
CP-ITI-234-FT.doc ATNA Maintaining a List of Certificates for Trusted Nodes/Applications ATNA
CP-ITI-237-FT.doc Submission of Association Objects XDS
CP-ITI-241a&b-FT.doc Document source replace support from required to optional XDS
CP-ITI-249-FT.doc XDS Demographics XDS

Completed CPs

CP Title Profiles Affected
CP-ITI-231-01.doc PDQ Clarify Domains in Query PDQ
CP-ITI-276-00.doc XCA Audit messages contain XCA transactions names/numbers XCA
CP-ITI-282-00.doc ITI-9 mistakenly refers to ERR-1 for Error Location ATNA

The ITI specific CP Process

See CP Process for IHE specific processing.

  1. Submission into the Incoming directory
  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.

Agenda and Minutes from CP discussions

March 12, 2008

March 11, 2008

February 13, 2008

  • CP-ITI-277-00.doc - Demographics search should not be strictly AND search - agreed to wording for the section, Yongjian will provided updated CP for last review
  • CPs in Incoming directory
    • CP-ITI-MDG-Fix Audit Message boolean values.doc - assigned to John M. 279
    • CP-ITI-sek-typeo-in-237-04.doc - assigned 278 to Sarah
    • CP-ITI-ML-WSLD-mistakes-00.doc - assigned 288 to Vassil
    • CP-ITI-MDG-Clarification of Document Export Audit Message.doc - assigned 280 to Rob
    • CP-ITI-LF-Off-line-Mode-Sec-Ref.doc - assigned 284 to Manuel. Needs double check of references then its ready for ballot.
    • CP-ITI-LF_wrong_TF_ref.doc - assigned 282, ready for ballot
    • CP-ITI-gec-repositoryUniqueId.doc - assigned 286 to George
    • cp-iti-bill-xds_typos.doc - need Bill for review
    • CP-ITI-bill-xds_ss_description.doc - need Bill for review
    • cp-iti-bill-xds_doc_rel_model.doc - need Bill for review
    • cp-iti-bill_getsscontents.doc - need Bill for review
    • CP-ITI-BD-XDSStoredQueryMultiplePatientIDs-00.doc - need Ben for discussion of this
    • CP-ITI-BD-UseofPartialSuccess-00.doc - assigned 287 to Karen
    • CP Forcare Unclear specification of XDSFolder lastUpdateTime in PnR (2007-12-14).doc - belief of the group would be that lastUpdateTime be ignored by registry, replaced with registry time. Communicate with author to determine if a change is needed.
    • CP Forcare Confusing wording in GetRelatedDocuments query (2007-12-14).doc - need Bill for review
    • CP Forcare AssociationType identifiers not qualified in XDS-b and Stored Query (2007-12-14).doc - need Bill for review
    • ITI-CP-bill_xds_audit.doc - assigned 281 to John M.
    • CP-ITI-xxx-hash.doc - assigned 283 to John M.
    • ITI-CP_larocca_XD_hash.doc - duplicate of 283
    • CP_ITI_LF_RFD_Items.doc - assigned 285 to George
    • CP-ITI-storedquery_value_too_large.doc - need Bill to review
    • CP Forcare-IBM XCN datatype in XDS should be more clearly defined (2008-01-15).doc - need Rick & Sarah to review
    • CP Forcare Clarify ObjectRef generation in XDS LeafClass query responses (2007-01-15).doc - need Bill to review
    • Steve noted that he will be submitting a new CP on when HL7V2 is used for PDQ if one socket and/or multiple are supported
    • CP-ITI-John_remove_old_xds_security_section_references.doc - assisgned 289 to John M.
    • Brief discussion of when MTOM is allowed, response from P&R, on RDS request. CP to be submitted on this
  • Brief discussion on SOAP 1.1/1.2 support. CP already submitted, will need more detailed discussion.
  • CP-ITI-264-00.doc - Allow the deletion of Documents within XDS (if ready) - was not ready

Minutes from 2007 tcons

For minutes for 2007 CP tcons see Change Proposal (CP) Processing 2007

Return to

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