ITI Change Proposals 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.

Final Text

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

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

Completed CPs

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

CP	Title	Profiles Affected
xds_227_01.doc	Provide list of Content Integration Profiles	XDS
xds_145_01.doc	Date/Time Format	XDS
xds_130_03.doc	DocumentEntry.legalAuthenticator should be multivalued	XDS
xds_030_06.doc	Standardizaton of XDS Documents	XDS
all_209_00.doc	Volume 1: Appendix F is obsolete	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: 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.

Tcon April 2, 2007

Agenda & Minutes

• Incoming CP review (ATNA only), see incoming directory
  • CP-ITI-ATNA-MOORE-TLS-Break-Glass.doc Reject this CP as inappropriate.
  • CP-ITI-232-00.doc (originally named CP-ITI-ATNA-MOORE-Self-Signed-Certificate.doc) Assign to John, # 232
  • CP-ITI-233-00.doc (originally named CP-ITI-ATNA-MOORE-Key-Length.doc) Systems must be able to be configurable to key lengths between 1024-4096. Assign to John, #233
  • CP-ITI-ATNA-MOORE-Certificate-Request-Process.doc Reject, but process should be a part of the testing environment.
  • CP-ITI-234-00.doc (originally named CP-ITI-ATNA-MOORE-Certificate-Per-System-Not-CA.doc) Assign to John, #234
  • CP-ITI-235-00.doc (originally named CP-ITI-ATNA-MOORE-Certificate-Contents.doc) Assign to Rob, #235. Should require that a system be able to configure off the checking of hostname.
  • CP-ITI-236-00.doc (originally named CP_ATNA_070216.doc] Assign to John, #236

• 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

• ITI Technical Committee