ITI Change Proposals 2012: Difference between revisions

From IHE Wiki
Jump to navigation Jump to search
Rjh (talk | contribs)
Rjh (talk | contribs)
Line 365: Line 365:


* Ready for Integration
* Ready for Integration
** ITI-CP-524-FT XDS Metadata author and intended recipient extension
** ITI-CP-536-FT Datatype Typos
** ITI-CP-573-FT Remove XForms Option
** ITI-CP-577-FT  (Missed from integration step of August Publication)
** ITI-CP-577-FT  (Missed from integration step of August Publication)
** ITI-CP-600-FT Change table 4.1.9 Folder metadata for including “Deprecated availabilityStatus”
** ITI-CP-602-FT XUA Extension Subject:role version
** ITI-CP-603-FT Update expected Actions when Document Recipient receives metadata error
** ITI-CP-604-FT Correct outdated reference to Audit Trail message payload schema
** ITI-CP-605-FT Error message on size mismatch
** ITI-CP-607-FT Extension On Media Encryption
** ITI-CP-608-FT ZIP Over Email
** ITI-CP-609-FT ZIP Over Email Response
** ITI-CP-612-FT DSUB Specific Query UUID
** ITI-CP-619-FT XCPD WSDL elements not adequately defined


===  Minutes ===
===  Minutes ===

Revision as of 10:32, 14 March 2012

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-chair in charge of CPs (currently Rob Horn) or by directly updating the 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.

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

These CPs have been integrated into the Version 8.0 of the Technical Framework and the 2011 version of Supplements.

CP Title Profiles Affected
368 SMTP clarifications for XDS.a and XDM ATNA
376 extend PIXV3/PDQV3 R-MIM PIX/PDQ
454 Patient Name in V3 PIX Get Corresponding Query Should Match V2 PIXV3
455 PIX/PDQ V3 - ControlActProcess moodCode should be EVN PIX/PDQV3
459 Retrieve example is wrong XDS
460 SourcePatientId example wrong XDS
474 The PIX/PDQv3 supplement does not document Audit Record Rqmts in Security Considerations PIX/PDQv3
479 Improve error reporting for XDS,XCA,XDR "XCA,XDS,XDR"
481 Section references in table without a table title are incorrect PWP
485 RFD urn values are defined incorrectly based on V.3.2.1.1 IHE-WSP201 RFD
494 Permit Secure App in XCA XCA
505 Improve examples PIX/PDQV3
506 Profile Use Of Coding Systems PIX/PDQV3
509 XDS Stored Query which associations to return XDS.b
510 soapAction deprecation Appendix V
512 XDSDocumentSet.intendedRecipient XD*
518 XCPD comments XCPD
521 ExternalIdentifier Clarification X*
531 XCA specify passthru of query request/response content XCA
534 Wrong wrappers for ITI-55 XCPD
535 XCPD: one and only one actOrderRequired element XCOD
539 Allow wildcards in PDQv3 PDQ
542 Introduction section is missing for PDQ v3 PDQ
544 Correct type for On-Demand Document Entries object type XDS
546 Delete reference to ITI-16 XDS
547 On-Demand Document Source replaces persisted documents XDS
548 Document Registry or Document Recipient audit message XDS
549 HPD Duplicate OID HPD
555 BPPC code BPPC
556 HPD Corrections HPD
557 Wrong wrappers for ITI-55 XCPD
558 Case of arguments in XCA Retrieve examples not correct XCA
561 XUA++ PurposeOfUse example lists wrong child element XUA
563 Specify use of IHE Profile in MSH-21 all
564 Clarify IHE Profiling of Field Delimiters all
565 HPD - Attribute Name Wrong HPD
566 HPD - typos in attribute names HPD
567 XCA FindDocuments specifiation of homeCommunityId XCA
568 Typo in ISO standard number HPD
569 Both HTTP-POSTand SOAP allowed for Archive Form RFD
571 Use of CDATA in XDS-SD Content XDS-SD
572 Typo in XCPD example of homeCommunityId XCPD
574 Correct Optionality Typo HPD
577 Is SourcePatientID single or multi-valued XDS
578 XCA needs to more clearly call out the need for patient ID translation XDS
583 Fix incorrect reference XCA
585 Leading Zero in Transaction ID ITI-30, ITI-31
591 Error in 3rd component in PDQ Query Response PDQ
592 Fix section labelling in DSUB DSUB
593 Editorial change of CDA R1 into CDA R2 XDS
597 ATNA Reference in XUA XUA

Ballots

Ballot 14

CP Title Profiles or Volumes Affected
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
524 XDS Metadata author and intended recipient extension 3
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

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

March 9, 2012

1000h Central

Agenda

  • Incoming CP Discussions
    • CP-ITI-LF-XDW-corrections Address XDW inconsistencies
  • Discuss CPs
    • ITI-CP-543-01 Additional XDR errorCode values
    • ITI-CP-551-01 DSG URN Clarification
  • Ready for Ballot
    • ITI-CP-414-03 IHE ITI TF Vol 2: Appendix L
    • ITI-CP-504-02 XDR Actors support Async Option
    • ITI-CP-516-01 Correct hyperlinks to point to TF sections
    • ITI-CP-527-01 Remove CodeDisplayName registry enforcement
    • ITI-CP-550-00 Additional XDR errorCode values
    • ITI-CP-587-00 Remove specialization of UserIsRequestor
    • ITI-CP-589-01 ATNA Encryption Reference in XDS Vol 1 Security Considerations
    • ITI-CP-606-00 Simple solution to XUA++ Authz-Consent option
    • ITI-CP-616-02 HPD Query and Feed operations use same parameter type
    • ITI-CP-618-01 XUA++ Authz-Consent Option, XACML solution
    • ITI-CP-626-00 Typos in table 4.1-8
    • ITI-CP-627-00 Author metadata attribute should not allow author elements with only a role or specialty
    • ITI-CP-628-00 authorTelecommunication attribute should be multivalued
    • ITI-CP-631-00 XDSExtraMetadataNotSaved code inconsistent
    • ITI-CP-636-01 XDS-SD Support for Character Set Encoding for plain text
  • Ready for Integration
    • ITI-CP-524-FT XDS Metadata author and intended recipient extension
    • ITI-CP-536-FT Datatype Typos
    • ITI-CP-573-FT Remove XForms Option
    • ITI-CP-577-FT (Missed from integration step of August Publication)
    • ITI-CP-600-FT Change table 4.1.9 Folder metadata for including “Deprecated availabilityStatus”
    • ITI-CP-602-FT XUA Extension Subject:role version
    • ITI-CP-603-FT Update expected Actions when Document Recipient receives metadata error
    • ITI-CP-604-FT Correct outdated reference to Audit Trail message payload schema
    • ITI-CP-605-FT Error message on size mismatch
    • ITI-CP-607-FT Extension On Media Encryption
    • ITI-CP-608-FT ZIP Over Email
    • ITI-CP-609-FT ZIP Over Email Response
    • ITI-CP-612-FT DSUB Specific Query UUID
    • ITI-CP-619-FT XCPD WSDL elements not adequately defined

Minutes

  • Issue Ballot
  • Discussed CPs
    • 543 discussed, new version, work to be done in comments
    • 551 discussed, decided to define a urn for II data-type (OID+extension)
    • 622 discussed, will add fixes for supplements also. Reference format is correct.
  • New CPs
    • ITI-CP-637 Address XDW inconsistencies

January 06, 2012

0900h Central

Agenda

  • Incoming CP Discussions
  1. ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2012/CPs/Incoming/CP-ITI-PMa_Specification_Of_ATNA_Logging_for_%20XUA++.doc
  • Discuss CP-632
  • Write CPs especially Security CPs
  • Ready for Ballot
    • ITI-CP-504-02 XDR Actors support Async Option
  • Ready for Integration
    • ITI-CP-577-FT (Missed from integration step of August Publication)
  • People and number of CPs in Assigned
 | Assigned editor   | Number of CPs |
 |-------------------+---------------|
 | Bill Majurski     |            27 |
 | Elliott Lavy      |             3 |
 | Geoff Pascoe      |             1 |
 | John Moehrke      |  11 (one f2f) |
 | Karen Witting     |             3 |
 | Lynn Felhofer     |             2 |
 | Manual Metz       |             1 |
 | Mark Sinke        |             3 |
 | Massimiliano Masi |             1 |
 | Rob Horn          |            14 |
 | Vassil Peytchev   |             7 |
 | Walco van Loon    |             5 |
 | Dan Trainor       |             3 |
 |                   |               |

Minutes