Difference between revisions of "ITI Change Proposals 2008"

From IHE Wiki
Jump to navigation Jump to search
Line 196: Line 196:
 
* [ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2007-2008/CPs/Assigned/CP-ITI-211-02.doc CP-ITI-211-02.doc] Yongjian: PIX/PAM Integration
 
* [ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2007-2008/CPs/Assigned/CP-ITI-211-02.doc CP-ITI-211-02.doc] Yongjian: PIX/PAM Integration
 
* [ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2007-2008/CPs/Assigned/CP-ITI-304-00.doc CP-ITI-304-00.doc] Charles: XDR on-line confusion
 
* [ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2007-2008/CPs/Assigned/CP-ITI-304-00.doc CP-ITI-304-00.doc] Charles: XDR on-line confusion
−
* [ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2007-2008/CPs/Assigned/CP-ITI-305-01.doc CP-ITI-305-01.doc] George: RFD – Requests for Clarification to Profile text
+
* [ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2007-2008/CPs/Assigned/CP-ITI-305-02.doc CP-ITI-305-02.doc] George: RFD – Requests for Clarification to Profile text
 
* [ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2007-2008/CPs/Assigned/CP-ITI-307-00.doc CP-ITI-307-00.doc] Vassil: PDQ Continuation Protocol in One Socket or Multiple Sockets
 
* [ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2007-2008/CPs/Assigned/CP-ITI-307-00.doc CP-ITI-307-00.doc] Vassil: PDQ Continuation Protocol in One Socket or Multiple Sockets
 
* [ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2007-2008/CPs/Assigned/CP-ITI-308-00.doc CP-ITI-308-00.doc] Vassil: PDQv3 specify what fuzzy search means
 
* [ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2007-2008/CPs/Assigned/CP-ITI-308-00.doc CP-ITI-308-00.doc] Vassil: PDQv3 specify what fuzzy search means
Line 202: Line 202:
 
* [ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2007-2008/CPs/Assigned/CP-ITI-310-00.doc CP-ITI-310-00.doc] Vassil: Assign profile #s to PIXV3 and PDQV3
 
* [ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2007-2008/CPs/Assigned/CP-ITI-310-00.doc CP-ITI-310-00.doc] Vassil: Assign profile #s to PIXV3 and PDQV3
 
* [ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2007-2008/CPs/Assigned/CP-ITI-311-00.doc CP-ITI-311-00.doc] Karen: Fix MSH-17 typo in example HL7 ADT messages
 
* [ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2007-2008/CPs/Assigned/CP-ITI-311-00.doc CP-ITI-311-00.doc] Karen: Fix MSH-17 typo in example HL7 ADT messages
−
 
−
 
−
 
  
 
== April 30, 2008 ==
 
== April 30, 2008 ==

Revision as of 13:35, 25 April 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
CP-ITI-272-02.doc Clarify actions of the Form Manager when it receives Retrieve Clarification ransaction RFD
CP-ITI-285-03.doc RFD – Requests for Clarification to Profile text RFD
CP-ITI-210-03.doc PAM ADT^A16 Structure PAM
CP-ITI-277-02.doc Demographics search should not be strictly AND search PDQ
CP-ITI-306-00.doc Typo in vol 2 section N.6 Appendix N
CP-ITI-254-01.doc No Actors and Options section in ATNA Vol 1 ATNA
CP-ITI-302-02.doc XCN datatype in XDS should be more clearly defined XDS

The ITI specific CP Process

See CP Process for IHE specific processing.

  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.

CP's to be completed to allow Final Text publication

Profile/Supplement Author CPs critical CPs other
Web Services Appendix Vassil 288 -
XUA John Expecting some -
Stored Query Bill 147, 228, 265, 295, 297, 298, 299, 300, 301, -
XDS.b Teddy 265, 267, 268, 286, 287, 288, 292 -
XDS-SD Sarah Expecting? -
BPPC John 273 -
XDM Rob None -

Agenda and Minutes from CP discussions

Unassigned

April 30, 2008

XD* and XCA CPs processing

Agenda


Minutes

TBD

April 28, 2008

Incoming CPs

Agenda

  • CPs in Incoming directory
    • CP-ITI-MS-failure_to_specify_PDF_A_level_of_conformance.doc
    • CP_ITI_LF_XDS-SD-Code-Value.doc
    • CP-ITI-Additional_XDS_Document_Entry_Identifiers-03.doc
    • CP-ITI-Forcare-SubmissionSetAuthorUUIDTypo.doc
    • CP-ITI-JJS_add_unique_authorinstitution_id_to_registry_stored_query_response.doc
    • CP-ITI-LF_formatCode-XDS-SD.doc
    • CP-ITI-LFFC-MappingCDAMetadata.doc
    • CP-ITI-LFFC-PrefixError.doc
    • CP-ITI-LFFC-QueryError.doc
    • CP-ITI-LFFC-StoredQueryNewErrorCode.doc
    • CP-ITI-MM-FolderMetadataTypo.doc
    • CP-ITI-MM-RAD_ITI_MetadataCoherence.do
    • CP-ITI-MM-XuaEuaGrouping.doc
    • CP-ITI-MM-XuaFaultyTransaction.doc
    • CP-ITI-MM-XuaInformativeMaterial.doc
    • CP-ITI-NR-PDQ_Continuations_Optional.doc
    • IHE_ITI_Change_Proposal-AuditLogsForITI43.doc
    • IHE_ITI_Change_Proposal-CoexistanceOfXDSAandXDSB.doc
    • IHE_ITI_Change_Proposal-WebServicesMustUnderstand.doc
    • IHE_ITI_Change_Proposal-XDR_USE_of_URI.doc
    • CP-ITI-CP-XDM-use-of-folders.doc

Minutes

TBD

April 17, 2008

XD* and XCA CPs processing

Agenda

Minutes

  • CP-ITI-228-04.doc Mark: FindDocumentQuery eventCode problem (2007 Passed ballot - then Bill and Sarah agreed to revise)
    • Bill gave overview of concern. Negotiation of interpretation of both "and" and "or", solution is to use parens to group using normal form. Bill to make edits to CP, then send email notificaion for review by committee and then ready for ballot.
  • CP-ITI-265-01.doc Karen: What version of SOAP is requred/optional on Stored Query
    • Stored Query, either 1.1 or 1.2 are acceptable, registry has to support both, Vol. 2 line 210 3.18.3 referenced standards
    • Should this policy apply to all of web services, document in Appendix V and reference from all other places. Agree that service endpt must support both in all applicable places.
    • Should it be two endpoints or one endpoints. Must support an endpt for each, but can be the same endpt. Product will document ports for support of both SOAP 1.1 and 1.2. Write "shall comply with Appendix V requirements" in each transaction and put strong shall language in Appendix V.
    • Karen will make edits for review.
  • CP-ITI-286-03.doc George: Repository should overwrite repositoryUniqueId if it is in metadata
    • Discussion of repositoryUniqueId requirements between XDS.a and XDS.b. Use the URL and this element to indicate what the Repository can support. Optionality should be Cp/P. Online mode XDR does NOT require URI. XDR offline and XDM use URI to reference the data. Need a CP to review all the metadata and make sure requirements are clear for all of XDR, XDM, XDS.a, XDS.b. Should consider merging this CP with incoming coexistance of XDS.a&XDS.b from Sarah.
  • CP-ITI-287-00.doc Karen: Use of PartialSuccess
    • Agree that it should be added. Karen will edit next version.
  • CP-ITI-288-00.doc Vassil: Problems in WSDL
    • Changes have been made on the ftp site. Question of precedence - need to specify that examples are for illustration only and updated examples are available on the ftp site. Agree that the WSDL is only on ftp. Schema is presented in English text - as done in XDS.b - i.e. english text is normative, further requirements refer to the machine readable section on ftp. Change appendix W to list what is available - like a readme for the ftp. Effects RFD, PIX/PDQ V3, XDS.b - XCA handled under Karen's CP. Vassil to make changes to all except XCA using this CP.
  • CP-ITI-302-01.doc Rick: XCN datatype in XDS should be more clearly defined
    • Reviewed the update from Mark. Ready for ballot.
  • CP-ITI-303-00.doc Rick: Unclear specification of XDSFolder lastUpdateTime in P&R
    • Skip, no update from discussion at f2f
  • CP-ITI-278-00.doc Sarah: Submission of Association Objects
    • Skip, no update from discussion at f2f
  • CP-ITI-267-00.doc Bill: Use MTOM/XOP for XDS.b instead of MTOM
    • MTOM or MTOM/XOP. For large documents you must XOP them. Normal is toolkits choose MTOM for small things, XOP for large things, often dynamic. The recipient of a transaction shall accept either, the intitiator of a transaction may generate either. Most toolkits if you start with MTOM/XOP it will respond with the same format. If the request is MTOM/XOP the response may be MTOM/XOP or simple SOAP. Take to ITI tech mailing list.
      • Part 1: receivers of documents (Consumer on retrieve, and repository on submit) shall accept both MTOM and MTOM/XOP
      • Part 2: Response to Provide&register transaction shall be either XOP or simple SOAP
      • Part 3: all other requests and responses shall be simple soap
    • Bill will update CP with this understanding and email review through ititech
  • CP-ITI-264-00.doc Bill: Allow the deletion of Documents within XDS
    • Suggested solution is to support removal of objects request in ebXML shall be accepted by XDS.b repository, forward unaltered to registry. Registry labels the document as deprecated. Conflict all changes to metadata are documented in submission set. This conflicts with this. Question: who has the right to delete. This is supplement material. Also talk about versioning of metadata, allow changes to metadata. Concern with the impact of this and not following procedure. Bill will write a white paper on life cycle management which will address replace, update, remove, etc.

April 15, 2008

CPs processing (non XDS CPs: PIX/PDQ, RFD...)

Agenda

  • George CPs - RFD CPs
    • CP-ITI-272-02.doc Clarify actions of the Form Manager when it receives Retrieve Clarification transaction
    • CP-ITI-285-02.doc RFD – Requests for Clarification to Profile text
  • PIX/PDQ
    • CP-ITI-210-02.doc Yongjian: PAM ADT^A16 Structure - simple fix, version 02 ready for review
    • CP-ITI-211-01.doc Yongjian: PIX/PAM Integration - addressing in co-chair cmt and in PDO supplement
    • CP-ITI-277-02.doc Yongjian: Demographics search should not be strictly AND search - discussed and reviewed, version 02 ready for ballot approval
  • Charles XDR
  • RFD, PIX, PDQ, PAM CPs in Incoming directory
    • CP-ITI-GEC-RFD-actorTransactionNames.doc
    • CP-ITI-FM-N6SectionTitle.doc
    • CP-ITI-SMM_PDQ_Continuation_Protocol.doc
    • CP-ITI-NR-PDQ_Continuations_Optional.doc
    • CP-ITI-AXO_PDQv3_specify_fuzzy_search.doc
    • CP-ITI-KW-PAM.Names-00.doc
    • CP-ITI-KW-Numbers.for.pixpdqv3.doc
    • CP-ITI-NOR_fix_@MSH.17_example_typo.doc

Minutes

  • CP-ITI-272-02.doc Clarify actions of the Form Manager when it receives Retrieve Clarification transaction
    • Reviewed updated version with fixed formatting and text change. Ready for Ballot.
  • CP-ITI-285-02.doc RFD – Requests for Clarification to Profile text
    • Discussed suggested resolutions to issues. Areed to change #1. Agreed to change #2. Agreed #3. Break #4&5 into a separate change proposal (305) and ask Dave to help with the text. Version 03 will be ready for ballot.
  • CP-ITI-210-02.doc Yongjian: PAM ADT^A16 Structure - simple fix, version 02 ready for review
    • Reviewed version 02. A small editorial change to do (move text outside the box) then 03 version ready for ballot.
  • CP-ITI-211-01.doc Yongjian: PIX/PAM Integration
    • #1) Handled by Domain Coordination Committee (DCC) work group on HL7. The CP will be updated once conclusion of this work group is reached. #2&3) addressed outside the CP process, Yongjian will update CP to indicate the resolution of #2&3 and #1 will be delayed waiting for DCC work group.
  • CP-ITI-277-02.doc Yongjian: Demographics search should not be strictly AND search
    • Discussed and reviewed, version 02 ready for ballot approval
  • CP-ITI-304-00.doc XDR on-line confusion
    • Charles not present, reminder sent to Charles to write this CP. Will review text once suplied by Charles.
  • CP-ITI-GEC-RFD-actorTransactionNames.doc
    • Concern that this is an extensive change and only one point of view. Those on the call agreed not to make this change. Reject, because its not a compelling rationale for the significance involved in the change.
  • CP-ITI-FM-N6SectionTitle.doc
    • Move to complete, author Manuel.
  • CP-ITI-SMM_PDQ_Continuation_Protocol.doc
    • Vol. 2 Section C.2.1 Network Guidelines line 7880 client must use same connection unless server drops. Continuation is not a new transaction, just one transaction in multiple steps. CP 307 assigned to Vassil.
  • CP-ITI-NR-PDQ_Continuations_Optional.doc
    • Concern that in real world applications there is no need for continuation. Alternatively clients need a way to restrict the quantity of data they will get back. Proposing that clients specify a size limit and supplier supports and sends error if there is more than that # of matches.
    • Lynn will solicit feedback from actual implementors and we will re-discuss at incoming call.
  • CP-ITI-AXO_PDQv3_specify_fuzzy_search.doc
    • Wild cards are not allowed. CP 308 assigned to Vassil.
  • CP-ITI-KW-PAM.Names-00.doc
    • Agree with concept - not with the name. Assign to Karen, keep tabs on HL7 work group to get outcome for this. Question #2 Vassil will check into it. Assiged CP 309.
  • CP-ITI-KW-Numbers.for.pixpdqv3.doc
    • Open issue in terms of how to incorporate them. Resolve how to incorporate because XDS.b does not have a separate profile #. Thinking that it should be done similar to XDS.b the way it was incorporated. CP 310 assigned to Vassil.
  • CP-ITI-NOR_fix_@MSH.17_example_typo.doc
    • Assign to Karen CP 311 - Nick to help with details if needed.

April 1, 2008

Security related CPs

Agenda

Minutes

  • CP-ITI-160-01.doc Rob: DSG use of URNs
    • Covered in call earlier today. Requires re-review.
  • CP-ITI-254-01.doc Rob: No Actors and Options section in ATNA Vol 1
    • Version 01 provided. Move rationale into rationale section. Agreed to release for ballot.
  • CP-ITI-147-01.doc Rob: Patient ID Encoding
    • The question of Patient ID should be generalized to matching of any string that may have international characters. XDS should specify the details of matching strings which may contain international characters. Currently XDS only describes a string match. Bill will review reference for normalizing strings. The group suggest to normalize the strings (based on standards referenced in the CP) and then do a bit compare. Rob will write the text and we will figure out where in XDS it would be best to insert it. Requires re-review.
  • CP-ITI-280-00.doc Rob: Clarification of Document Retrieve Import/Export Audit Message
    • Note ready, Rob to write text for later review.
  • CP-ITI-255-00.doc Manuel: Renaming of two sections on security in XDS
    • Reviewed security sections. Agreed to move any valid content of the Security Requirements section to Vol. 1. Security Considerations will stay and have a subsection on audit requirements. Where the security considerations section should go we have several options and will try them out and work out in the template update. In looking at the template its not clear if 3.Y.4.1 should be message name rather than transaction name, John will fix the template and distribute for review. Once we are comfortable with the template will be distributed to the DCC for cross domain consideration and approval. Then the CP can make the appropriate updates to be consistent with the template. May need to review other supplements (i.e. XCA) where the template was mis-interpreted.
    • During the discussion the question of having a link to the risk assessment in the TF because of maintanence problems. XCA included the link as a footnote. There have been no maintenance issues. Conclusion that this problem belongs in the cookbook discussion but that including a link to the risk assessment on the ftp site as a footnote is reasonable practice.
  • CP-ITI-284-00.doc Manuel: Incorrect section reference for off-line transaction option in XDS.a
    • Manuel needs to check a link, has not done yet. Ready to ballot once link is checked.
  • CP-ITI-273-00.doc John: Fix Options descriptions in the BPPC profile
    • John agrees with all the changes, Rob would like to review. Discussion is how to deliver to the ballot, as a referenced link, included inline using word tracking, included inline using standard change tracking. Agreed to compromise position, included inline (and referenced) using word tracking. John will not in an editorial box that this CP is "special" so is allowed to use word tracking rather than the normal change tracking formatting.
  • CP-ITI-279-00.doc John: Clarification of Document Retrieve Import/Export Audit Message
    • Simple change, John to write up editorial changes
  • CP-ITI-281-00.doc John: XDS Audit
    • John needs to investigate prior to being able to discuss
  • CP-ITI-283-00.doc John: Document in XD* the standard used for document hash
    • John to write up editorial changes
  • CP-ITI-289-00.doc John: Remove old security section references
    • subsumed into Manuel's CP 255. CP 289 canceled as merged into 255.

March 12, 2008

  • CP-ITI-272-01.doc Clarify actions of the Form Manager when it receives Retrieve Clarification transaction
    • Clarify CP editorial formatting. First change reworded to offer one approach as grouping.
  • CP-ITI-285-01.doc RFD – Requests for Clarification to Profile text
    • Agreed to resolution of points 1-2. Points 3-5 to be addressed in next revision.
  • CP-ITI-257-03.doc XCA Missing Protocol Requirements (WSDL info)
    • Agreed with text but question of which ftp directory to keep associated files
  • CP-ITI-228-04.doc Mark: FindDocumentQuery eventCode problem (2007 Passed ballot - then Bill and Sarah agreed to revise)
    • Bill, Mark, Sarah to discussion in Oxford
  • CP-ITI-286-01.doc Repository should overwrite repositoryUniqueId if it is in metadata
    • Larger issue of supplements that imply new requirements on actors in other profiles. For instance, repositoryUniqueId must be ensured empty by XDS.a Repository actors even if specified by source. Larger issue to be addressed separately.

March 11, 2008

  • CP-ITI-302-00.doc Rick: XCN datatype in XDS should be more clearly defined
    • Concern that this could break current implementations, suggested re-wording, encourage assigning authority rather than requiring it.
  • CP-ITI-303-00.doc Rick: Unclear specification of XDSFolder lastUpdateTime in P&R
    • Discussion of hash/size being ignored, suggestion that it is useful to validate these values to detect transmission errors. Concern that this has been confusing for a while and we need to settle on a stable solution. Suggestion that we could allow repository to validate but not require it. Submittor would need to detect the error. This change effects many places and the editorial work of getting it right may be significant. Left to the author to deal with - when done committee will review again.
  • CP-ITI-291-00.doc Multiple patient Ids for a single Stored Query
    • Discussed use case that resulted in this requirement. Committee suggested other methods for solving the use case. General resistence to making this kind of change. Agreed to cancel this CP.
  • CP-ITI-263-00.doc XDS Document Relationship Model
    • Lots of discussion and alternatives for dealing with the use case. Agreed that a clear definition about relationship inter-dependecies change as relationships change is needed.

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