ITI Change Proposals 2013

From IHE Wiki
Revision as of 09:05, 11 January 2013 by Rjh (talk | contribs) (→‎Agenda)
Jump to navigation Jump to search

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-chairs in charge of CPs (currently Rob Horn and Derrick Evans) and directly updating the directory if you have access.
  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 2013

These CPs have been integrated into the Version 10.0 of the Technical Framework and the 2013 version of Supplements.

CP Title Profile or Volumes Affected
none yet none yet none yet

Note CP-644 was integrated without a ballot as part of the Profile retirement process.

Integrated CPs 2012

These CPs have been integrated into the Version 9.0 of the Technical Framework and the 2012 version of Supplements. 

 Links need to be fixed
 Entries need to be sorted
CP Title Profiles Affected
516 Correct hyperlinks to point to TF sections XUA
527 Remove *CodeDisplayName Registry enforcement 3
606 XUA++ Authz-Consent Option XUA
637 Address XDW Inconsistencies" XDW
640 Clarify option requirements in XDW XDW
641 Define Code for Workflow Status in eventCodeList XDW
642 Define Code for Workflow Status in eventCodeList XDW
524 XDS Metadata author and intended recipient extension 3
536 Datatype Typos 2b
573 Remove XForms Option RFD
600 Change table 4.1.9 Folder metadata for including “Deprecated availabilityStatus” 3
602 XUA Extension Subject:role version XUA
603 Update expected Actions when Document Recipient receives metadata error 2b
604 Correct outdated reference to Audit Trail message payload schema 2
605 Error message on size mismatch 3
607 Extension On Media Encryption 2b
608 Zip over Email 2b
609 Zip over Email Response 2b
612 DSUB Specific Query UUID DSUB
619 XCPD WSDL elements not adequately defined XCPD
516 Correct hyperlinks to point to TF sections XUA
527 Remove *CodeDisplayName Registry enforcement 3
606 XUA++ Authz-Consent Option XUA
637 Address XDW Inconsistencies" XDW
640 Clarify option requirements in XDW XDW
641 Define Code for Workflow Status in eventCodeList XDW
642 Define Code for Workflow Status in eventCodeList XDW
414 IHE ITI TF Vol 2: Appendix L 2
504 XDR Actors support Async Option 2b
516 Correct hyperlinks to point to TF sections 2
527 Remove *CodeDisplayName Registry enforcement 2a
550 Additional XDR errorCode values 2
587 Remove specialization of UserIsRequestor 2
589 ATNA Encrypttion Reference in XDS Vol1 Security Considerations 1
606 XUA++ Authz-Consent Option XUA
616 HPD Query and Feed operations use same parameter type HPD
618 XUA++ Authz-Consent Option - XACML Solution XUA
626 Typos in table 4.1-8 Document Metadata Attribute Enforcement 3
627 Author metadata attribute should not allow author with only a role or specialty 3
628 authorTelecommunication attribute should be multi-valued 3
631 XDSExtraMetadataNotSaved code inconsistent 3
636 XDS-SD Support for Character Set Encoding for plain text 3

Ballots

Ballot 16 (ballot issued)

CP Title Profile or Volumes Affected Ballot Result
537 No PID segment in PDQ response if PID-3 empty 2a Proposed -02 version to resolve comments. Confirm with Gerry and Elliot.
538 Handle CX datatype as undividable in PDQ query. 2a Proposed -02 version to resolve comments. Confirm with Gerry.
540 PIX Query, repeated ERR segment for Case 5 2a Comments resolved in 540-02
601 Extend HPD memberOf to support attributes on relationship HPD approved, no comments(affirmative 10, abstain 3)
610 DSUB correction for event ID in audit message DSUB approved, no comments(affirmative 10, abstain 3)
611 DSUB Correct Query Parameter Encoding DSUB approved, no comments(affirmative 10, abstain 3)
632 Metadata for stable versions of on-demand documents XD* approved, no comments(affirmative 10, abstain 3)
645 Folder DSUB approved, no comments(affirmative 10, abstain 3)
646 Author Encoding in XDW too limited XDW approved, no comments(affirmative 10, abstain 3)
647 DSUB contains reference to PCC APR profile that no longer exists DSUB approved, no comments(affirmative 10, abstain 3)

Assigned CPs

CP assignment

For a list of CPs as they are currently assigned see the latest CP-ITI-Tracking-2012-nn-nn.xls file in the Status directory.

Agenda and Minutes from CP discussions

11 January 2013, 9-11 Central

Agenda

  • Discuss CPs
    • CP-654-01
    • CP-659 Update for those who missed last week's tcon


  • Ballot-16 Results
    • Substantive comments with email discussion. Need to reach closure.
      • ITI-537 No PID segment in PDQ response if PID-3 empty (One negative vote)
      • ITI-538 Handle CS datatype as undividable in PDQ query (One negative vote)

Minutes

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