Difference between revisions of "ITI Change Proposals 2007"

From IHE Wiki
Jump to navigation Jump to search
Line 61: Line 61:
 
| XDS
 
| XDS
 
|-
 
|-
−
| [ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2006-2007/CPs/FinalText/CP-ITI-156-06.doc CP-ITI-156-06.doc]
+
| [ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2006-2007/CPs/FinalText/CP-ITI-156-07.doc CP-ITI-156-07.doc]
 
| ATNA PIX/PDQ Events
 
| ATNA PIX/PDQ Events
 
| PIX & PDQ
 
| PIX & PDQ

Revision as of 15:20, 25 July 2007

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.
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 Technical Framework and Supplements.

CP Title Profiles Affected Date
CP-ITI-229-01.doc RFD Needs ITI Transaction Numbers RFD May 2007

Final Text CPs

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

CP Title Profiles Affected
xds_028_08.doc Proposed Error Codes XDS
xds_117_05.doc Refinement of RPLC Semantics XDS
xds_130_03.doc DocumentEntry.legalAuthenticator should be multivalued XDS
xds_145_01.doc Date/Time Format XDS
CP-ITI-156-07.doc ATNA PIX/PDQ Events PIX & PDQ
CP-ITI-164-10.doc XDS ATNA Events XDS
CP-ITI-180-01.doc Missing Team message ATNA
xds_187_07.doc Extra metadata XDS
pdq_203_02.doc Update Examples of last name search PDQ
pix_204_04.doc Locator deprecation, multidomain issues (pid fields) PIX
CP-ITI-208-05.doc XDS metadata should clearly specify single vs. multi-valued XDS
all_209_00.doc Volume 1: Appendix F is obsolete ATNA
pix_xds_212_02.doc Why does Doc Reg get A08 messages XDS/PIX
xdssd_214_01.doc Format code not consistant with other profiles XDS-SD
xdssd_215_02.doc xs:base64Binary encoding XDS-SD
xdssq_216_01.doc Patient ID not quoted in example XDS-SQ
xdssq_217_01.doc Parameters for Required Queries XDS-SQ
xdssq_218_01.doc FindDocuments paremeter ConfidentialityCodeScheme missing XDS-SQ
xdssq_219_01.doc GetAssociations query parm should be Required XDS-SQ
xdssq_220_01.doc Status Value Typos XDS-SQ
xds_225_02.doc uniqueId enforcement XDS
xds_226_01.doc XDSDocumentEntry.uniqueID without extension XDS
CP-ITI-230-02.doc Clarify <softwareName> and <manufactureModelName> for virtually scanned documents XDS-SD
CP-ITI-232-03.doc ATNA Self Signed and CA Signed Certificates ATNA
CP-ITI-233-01.doc ATNA Key Length ATNA
CP-ITI-236-02.doc XDS ATNA immediate transfer not always required ATNA
CP-ITI-238-03.doc Combined Registry/Repository Breaks RFP Process XDS
CP-ITI-239-03.doc Audit Syslog Requirements (TAG field) ATNA
CP-ITI-240-02.doc Mapping CDA ID to XDS-SD XDS-SD
CP-ITI-242-01.doc PDQ Use case #2 correction PDQ
CP-ITI-243-02.doc PDQ RCP Field 2 clarification PDQ
CP-ITI-244-00.doc Consistent terminology specified in CP 150 not applied to Vol. 1 XDS
CP-ITI-245-01.doc Inconsistencies in PAM PAM
CP-ITI-246-03.doc Move XDS Metadata sections to separate chapter and reference from multiple transactions XDS
CP-ITI-247-01.doc ATNA Certificates format (DER / BER)transactions ATNA
CP-ITI-248-00.doc PWP should point at RFC3377 PWP
CP-ITI-250-03.doc UUID conversion to OID OID Appendix
CP-ITI-251-00.doc Typos in XDS metadata section (3.14.4.1.2) XDS

Canceled CPs

These CPs have been canceled because they did not pass ballot.

CP Title Profiles Affected
xds_030_06.doc Standardizaton of XDS Documents XDS
xds_227_01.doc Provide list of Content Integration Profiles XDS

Balloted CPs moved back to Assigned

These CPs had comments from the ballot that suggested they are not ready for final text yet. Have been moved back to assigned status.

CP Title Profiles Affected
CP-ITI-228-03.doc FindDocumentQuery eventCode problem XDS
CP-ITI-237-02.doc Submission of Association Objects XDS

Completed CPs

These CPs are ready for ballot. They have not yet been balloted.

CP Title Profiles Affected
CP-ITI-241-02.doc Document source replace support from required to optional XDS


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: dublicate, 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 starting with -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.

May 30, 2007

The CPs listed below were discussed on the call. The version listed below of each file is the version including the updates from today's discussion. If the link fails then the author has not yet submitted the promised fixes. To load previous version, copy/paste the link and edit.

May 25, 2007

  • CP-ITI-156-04.doc- editorial comments, updated version will be reviewed by email and then ready for ballot.
  • xds_164_09.doc - reformat to go into the Security Considerations sections of transactions (rather than in a separate appendix). Updated version will be reviewed by email and then ready for ballot.
  • CP-ITI-232-02.doc - small editorial update and then ready for ballot.
  • CP-ITI-239-02.doc - small editorial update and then ready for ballot.

May 24, 2007

May 23, 2007 Joint with PCC

  1. Additional XDS Document Entry Identifiers Change Proposal CP-ITI-Additional_XDS_Document_Entry_Identifiers-03.doc. Discussion fleshed out the details of the proposal and identified a solution. Probably needs to be released as a small supplement. Keith will write up next version and distribute to committees.
  2. CP-ITI-240-01.doc - after discussion and clarification this CP is ready to be issued for ballot
  3. BPPC - ready to go to final text after application of several PCC change proposals. Agreed to provided revised supplement to ITI mid-June for review and feedback in July. After updates based on review the supplement will be integrated into the ITI Vol. 1 and 2 Technical Framework documents as part of the update to V4.0 expected in August.
  4. Web Services - Both ITI and PCC are defining HL7 V3 Web SErvices transactions. This work needs to be harmonized. Keith will review ITI's work and give input.

Face-to-face May 15, 2007

Agenda & Minutes

  • CP-ITI-241-01.doc - agreed to general direction of the CP. Break the lifecycle management options into independent options (including replace). Add query to be an optional transaction that is required if any of the options are specified.
  • xds_117_02.doc - good and substantial comments were received, an updated version will be reviewed again

Face-to-face May 16, 2007

Tcon May 7, 2007

Agenda & Minutes

  • pix_204_02.doc Agreed in principle, Laurie and Dave will be asked to review detailed text and then it will be released for ballot.
  • xds_028_03.doc General agreement on the direction. Suggestion that there should be a partial sucess status added. Email to ititech will solicit further comments.
  • Submissions from Laurie accepted and assigned CP 242 & 243. With a few wording fixes these are ready for ballot.
  • xds_118_00.doc agreed to cancel
  • pdq_203_01.doc Agreed on direction, Yongjian will update and review with Laurie and then ready for ballot.
  • CP-ITI-239-01.doc Reassigned to John.
  • CP-ITI-241-00.doc Requires a Vol. 1 update as well and discussion of requirement of query.

Tcon April 2, 2007

Agenda & Minutes

  • Assigned CPs ready for review: (as time allows, in following order)
    • 209 - Move CP to complete. All the items in the referenced Appendix have been addressed by the standards body. So the list should be removed from the TF. This CP updates the appendix to be empty.
    • 164 - Reviewed discussion items in text. Agreed that this should be an XDS specific section in a new Appendix. The PDQ and PIX work will be another section in the same appendix.
    • CP-ITI-228-01.doc - Brief review. Needs review by originator (Sarah).
    • 156 - Warren: deferred
    • 212 - Charles: deferred
  • CP Planning: Plan future CP work
    • xds_118_00.doc- Requires clarification by original initiator. Steve/Karen to followup with possible initiator. Re-assigned to Karen. New version at CP-ITI-118-01.doc
    • xds_147_00.doc - Two possible approaches to this a) require registries to do unicode normalization b) require patient ids to be in the ASCII character set. Second option seems preferable. Rob will write that option up and it will be distributed to national areas that would have a concern (Korea, others?)
    • dsg_160_00.doc - This requires more thought and there seems to be no urgency. Still not enough vendors implementing DSG to require connectathon testing of it.
    • atna_180_00.doc - team login question requires further discussion with larger group.

Tcon March 23, 2007

See Minutes .

Return to

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