Difference between revisions of "ITI Change Proposals 2016"
(→Agenda) |
|||
| Line 338: | Line 338: | ||
=== Minutes === | === Minutes === | ||
| − | '''Attendees:''' | + | '''Attendees: Ken M, Gila P, Rob H, Tarik I, Manuel M, John M, Elliott L, Karen W.''' |
'''(1) Assigned CP outcomes''' | '''(1) Assigned CP outcomes''' | ||
| − | * CP-ITI-914-02 - | + | * CP-ITI-914-02 - Elliott L presented his CP for discussion. Elliott will send it to Bill for review to verify correctness. |
| − | * CP-ITI-910-01 - | + | * CP-ITI-910-01 - Could not review as Dick Donkers was unable to attend. |
| − | * CP-ITI-902-01 - | + | * CP-ITI-902-01 - John M is proposing to add the words "some regions also required conformance to ISO 17090, which includes additional certificate issuing, content, and validation rules" to section 5.5.2. Gila will email IHE-J to see what they think. If they require more than that, we will work with them to create volume 4 national extension content. |
| − | * CP-ITI-902-02 - | + | * CP-ITI-909-02 - (Typo -- was incorrectly listed on the agenda as 902-02) Karen W reviewed the proposal to restrict ITI-41 or ITI-42 from carrying On Demand Documents. Karen will finish the editorial work based on the extensive discussion, and will update the explanations and then it is ready for ballot! |
| − | |||
'''(2) Incoming CP outcomes''' | '''(2) Incoming CP outcomes''' | ||
| − | * CP-ITI-BM-Redoc-aggressive-validationCP.doc - | + | * CP-ITI-BM-Redoc-aggressive-validationCP.doc - Accepted and assigned CP number 923-00 and assigned to Ken Meyer. CP pertains to first round of volume 3 redocumentation. |
| − | * CP-ITI-LF-FixTFRefInXCDR.doc - | + | * CP-ITI-LF-FixTFRefInXCDR.doc - Accepted, and identified as part of this year's redocumentation effort and assigned to Karen Witting to find the correct reference in the new text. Assigned number 924-00 |
| − | * CP-ITI-NC-UTC-offset-DTM.doc - | + | * CP-ITI-NC-UTC-offset-DTM.doc - Group discussed concerns that this is a breaking change. |
| + | **Rob said that the value is explicitly UTC, so the offset is always zero | ||
| + | **Elliott L suggested that a single offset value is inadequate, because the offset changes as the location crosses a DST boundary. | ||
| + | ** Accepted the CP and assigned it to Nader C to work on with support from Rob Horn. CP ID number 925-00 | ||
'''(3) Next in CPs''' | '''(3) Next in CPs''' | ||
Revision as of 17:45, 8 April 2016
Introduction
This page contains the details of Change Proposal (CP) processing in the ITI domain for the 2015-2016 publication cycle.
The ITI Change Proposal process follows the general IHE CP process described on the Change Proposal process page. The following sections give more detail on the process for folks involved in the CP process in the ITI domain.
The ITI-specific CP Process
The following text explains what the process used by the ITI technical committee in processing submitted CPs. It is consistent with the general IHE CP process and is informative only.
- Write a change proposal. Here is IHE's Change Proposal Template
- Submit into the Incoming directory. This is typically done by directly updating the directory if you have access; otherwise send it an email to the ITI Technical Committee members in charge of CPs (currently Lynn Felhofer).
- The new CPs are considered by the committee at periodic CP review calls. 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.
- Committee works with editor to draft the CP. Versions are kept in Assigned directory and numbered -00, -01, -02, etc.
- Committee decides CP is ready for ballot. Latest version of CP is moved to Completed diretory and old versions are moved to old_versions.
- Co-chair collects Completed CPs into a ballot. The Ballot directory will be used for this.
- Ballot is released to the general community for voting
- 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.
- 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 involved are:
- 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.
- Assigned
- contains CPs that have been assigned an editor and are being actively worked on by the committee, i.e. Assigned 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.
- Integrated
- contains the version of the CP that was integrated into the TF.
- Rejected
- CPs that have been submitted by rejected by the committee
- Canceled
- contains CPs that have been canceled, i.e. Canceled status
- Ballots
- contains Ballots that have been released for voting by the general community
- Status
- contains spreadsheets describing the status of CPs.
Change Proposal pages from previous years
Ongoing work on CPs is placed on the current year CP page. Prior years work can be accessed at:
- ITI Change Proposals 2015
- ITI Change Proposals 2014
- ITI Change Proposals 2013
- ITI Change Proposals 2012
- ITI Change Proposals 2011
- ITI Change Proposals 2010
- ITI Change Proposals 2009
- ITI Change Proposals 2008
- ITI Change Proposals 2007
ITI CP Tracking
Location of CPs, and CP status
All Change Proposal management is done on the IHE ftp site here.
Since March 2015, the ITI tracks status of its Change Proposals on the "CPs tracking" tab in this google doc: https://docs.google.com/spreadsheets/d/1gdr_Y8xZBvbb326J4z67cqprxOexFgtkPj_VlD3rB9E/edit?usp=sharing
Approved CPs to be integrated in 2016
CPs that have passed ballot in this cycle, and that will be integrated into Version 12.0 of the Technical Framework and the 2016 version of Supplements in September 2016 are listed on the "Ballot Log" tab of the tracking spreadsheet.
In Aug 2016, CPs will be integrated & checked following this process (currently draft): ITI CP Integration Process
Ballots
Ballot 29
Out for ballot: Aug 13 - Sep 16 2015
Ballot 29 CPs, comments, and votes are archived here: ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2016/CPs/Ballots/ballot_29/
CPs approved in this ballot are here: ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2016/CPs/3_FinalText/from_Ballot_29/
Comments/votes were reviewed on the Sep 24 & 25 CP calls. Resolution is in the table below.
| CP-ITI | Title | Ballot Result |
|---|---|---|
| 559-02 | MPQ profiles queries vs. Metadata Update option | Approved |
| 801-04 | Update Vol 1 references to RFC 3881 | Approved w/ updates |
| 872-05 | Add ATNA Repository Forwarding and re-doc ITI-20 transaction | Approved w/ updates |
Ballot 30
Out for ballot: Nov 23 - Dec 1, 2015
Ballot 30 CPs, comments, and votes are archived here: ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2016/CPs/Ballots/ballot_30/
CPs approved in this ballot will be posted here: ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2016/CPs/3_FinalText/from_Ballot_30/
Comments/votes will be reviewed on the CP call on December 4, 2015
| CP-ITI- | Title | Ballot Result |
|---|---|---|
| 771-04 | Clarify hash validation rules in Volume 3 | Approved w/ updates |
| 797-07 | Definition of Document | Approved |
| 814-06 | Remove ambiguity about “Registry Enforcement” of display name in coded attributes | Failed; back to assigned |
| 857-03 | Clarify/update the use of homeCommunityID in XCA | Failed; back to assigned |
| 870-02 | Repository behavior on ITI-42 failure | Approved w/ updates |
| 879-01 | mACM - Fix inaccurate Field and Section references plus typos | Approved |
| 890-02 | mACM – Clarify resources included in ITI-84 and ITI-85 response | Approved w/ updates |
Ballot 31
Out for ballot: Dec 4, 2015 - Jan 6, 2016
Ballot 31 CPs, comments, and votes are archived here: ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2016/CPs/Ballots/ballot_31/
CPs approved in this ballot are posted here: ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2016/CPs/3_FinalText/from_Ballot_31/
Comments/votes were reviewed on the CP call on January 8, 2016
| CP-ITI- | Title | Ballot Result |
|---|---|---|
| 814-08 | Remove ambiguity about “Registry Enforcement” of display name in coded attributes | Approved w/ updates |
| 858-03 | Fix ITI-39 error reporting requirements | Approved w/ updates |
| 889-03 | Clarify Error Code used for ‘RPLC’ or ‘XFRM_RPLC’ Association Validation | Failed; updates made require reballoting |
| 893-00 | mACM – clarify actor requirements for create & read | Approved |
| 896-00 | referenceIdList Clarification | Failed; back to assigned |
| 898-01 | Update to MetadataLevel Parameter | Approved w/ updates |
| 899-00 | Typo in XCPD Query transaction | Approved |
| 900-00 | mACM – fix PCD-06 mapping for alert text | Approved |
| 903-01 | Add encounterID to referenceIdList | Approved w/ updates |
| 904-00 | Fix ASTM signature purpose vocabulary | Approved |
Ballot 32
Out for ballot: Feb 24 - Mar 15, 2016.
The ballot announcement is here.
The ITI Technical Committee will review comments/votes on these dates:
- Thu March 17, 2016, 9-11am CDT - MHD and Appendix Z comments
- Fri March 18, 9-11am CDT' - PIXm and PDQm comments
- Thu March 24, 8-11am CDT - MHD, Appx Z and PIXm comments
- Wed Apr 6, 8-10am - finish open review items
Ballot 32 CPs are archived here: ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2016/CPs/Ballots/ballot_32/
Ballot 32 consolidated comments & votes are here.
CPs approved in this ballot will be stored here: ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2016/CPs/3_FinalText/from_Ballot_32/
| CP-ITI | Title | Ballot Result |
|---|---|---|
| 884-00 | PIXm changes for DSTU2 | |
| 885-00 | PDQm changes for DSTU2 | |
| 886-00 | MHD changes for DSTU2 | |
| 919-00 | Split FHIR-specific Appendix Z out of PDQm supplement & update for DSTU2 |
Ballot 33
Out for ballot: March 21 - April 20, 2016
Ballot 33 CPs are archived here: ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2016/CPs/Ballots/ballot_33/
Ballot 33 consolidated comments and votes are here.
CPs approved in this ballot will be stored here:
Comments/votes will be reviewed during the April ITI Tech F2F. Date/time TBD.
| CP-ITI | Title | Ballot Result |
|---|---|---|
| 582-04 | Metadata Update correction for associations in GetAllQuery | |
| 799-01 | SubmissionSets are immutable | |
| 857-04 | Clarify/update the use of homeCommunityId in XCA | |
| 880-02 | Add new value for Study Instance UID in CXi.5 (Identifier Type Codes) | |
| 888-03 | ProducerReference in ITI-53 and ITI-54 – fix unclear usage | |
| 889-07 | Clarify Error Code used for ‘RPLC’ or ‘XFRM_RPLC’ Association Validation | |
| 895-03 | Clarify/update the use of homeCommunityID in XCPD | |
| 896-03 | referenceIdList Clarification | |
| 901-02 | On-Demand Document Source options | |
| 905-00 | ITI-8 PID field Optionality | |
| 906-00 | ITI-8 MSH message structure - Revert changes introduced in CP-ITI-786 | |
| 908-00 | Table 4.3.1.1-3: on-demand repositoryUniqueId should be required | |
| 918-00 | Fix workflowInstanceId specification in Vol 3 CXi datatype definition |
Assigned CPs
For a list of CPs that are currently assigned see the 'CP tracking' tab in the CP status google doc. Assigned CPs are stored here: ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2016/CPs/1_Assigned/
Upcoming CP discussions
ITI CP review calls are typically held the 1st Friday and 3rd Thursday of each month from 9-11am Central US. Additional sessions may be scheduled during ITI Tech F2F meetings. Changes to the 'traditional' schedule for CP calls is announced on the ititech email list.
April-8-2016
Fri, 9-11am CDT
- Webex link: https://himss.webex.com/himss/j.php?MTID=mad82628465e091fc04af8c484eef6da5
- Meeting number: 920 618 063
- Password: Meeting1
Agenda
The current CP status spreadsheet is here
(1) Assigned CPs for discussion ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2016/CPs/1_Assigned/
- CP-ITI-914-02 - Value of Content-Type HTTP header action parameter (Elliott L)
- CP-ITI-910-01 - HPD - Updates to ITI-58 – Provider Information Query (Dick D)
- CP-ITI-902-01 - DSG conformity with ISO 17090-4 (John M)
- CP-ITI-902-02 - On Demand Doc option (Karen W)
(2) Incoming CP processing ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2016/CPs/0_Incoming/
- CP-ITI-BM-Redoc-aggressive-validationCP.doc
- CP-ITI-LF-FixTFRefInXCDR.doc
- CP-ITI-NC-UTC-offset-DTM.doc
(3) Next in CPs
- Wed Apr 20 - Ballot 33 comments due
- Thu Apr 21, 9-11 CDT - we will resolve ballot 33 comments during this regular 3rd Thurs CP call
Minutes
Attendees: Ken M, Gila P, Rob H, Tarik I, Manuel M, John M, Elliott L, Karen W.
(1) Assigned CP outcomes
- CP-ITI-914-02 - Elliott L presented his CP for discussion. Elliott will send it to Bill for review to verify correctness.
- CP-ITI-910-01 - Could not review as Dick Donkers was unable to attend.
- CP-ITI-902-01 - John M is proposing to add the words "some regions also required conformance to ISO 17090, which includes additional certificate issuing, content, and validation rules" to section 5.5.2. Gila will email IHE-J to see what they think. If they require more than that, we will work with them to create volume 4 national extension content.
- CP-ITI-909-02 - (Typo -- was incorrectly listed on the agenda as 902-02) Karen W reviewed the proposal to restrict ITI-41 or ITI-42 from carrying On Demand Documents. Karen will finish the editorial work based on the extensive discussion, and will update the explanations and then it is ready for ballot!
(2) Incoming CP outcomes
- CP-ITI-BM-Redoc-aggressive-validationCP.doc - Accepted and assigned CP number 923-00 and assigned to Ken Meyer. CP pertains to first round of volume 3 redocumentation.
- CP-ITI-LF-FixTFRefInXCDR.doc - Accepted, and identified as part of this year's redocumentation effort and assigned to Karen Witting to find the correct reference in the new text. Assigned number 924-00
- CP-ITI-NC-UTC-offset-DTM.doc - Group discussed concerns that this is a breaking change.
- Rob said that the value is explicitly UTC, so the offset is always zero
- Elliott L suggested that a single offset value is inadequate, because the offset changes as the location crosses a DST boundary.
- Accepted the CP and assigned it to Nader C to work on with support from Rob Horn. CP ID number 925-00
(3) Next in CPs
- Wed Apr 20 - Ballot 33 comments due
- Thu Apr 21, 9-11 CDT - we will resolve ballot 33 comments during this regular 3rd Thurs CP call
April-21-2016
Thu, 9-11am CDT
- Webex link:
- Meeting number:
- Password: Meeting1
Agenda
(1) CP Resolve Ballot 33 comments
- Ballot 33 contents are here: ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2016/CPs/Ballots/ballot_33/
- Consolidated comments are here: https://docs.google.com/spreadsheets/d/1IQ8k8eEsuKfG8o8fldu2eQUxA1GVPJ5A8S4UfyuM1cI/edit?usp=sharing
(2) Next in CPs
- We will blitz again during the ITI F2F starting April 25
Agenda and Minutes from past CP calls
For 2015-16, they are collected here: ITI CPs 2015-16-Agenda and Minutes from past CP calls