Difference between revisions of "ITI Change Proposals 2017"
| (6 intermediate revisions by the same user not shown) | |||
| Line 250: | Line 250: | ||
Ballot 39 contents, comments/votes, and resolution are gathered [https://docs.google.com/spreadsheets/d/1FpSz0VYAG-Igb1RJnfWu_DdM55jwSYcStTucSwFitqk/edit?usp=sharing here]. | Ballot 39 contents, comments/votes, and resolution are gathered [https://docs.google.com/spreadsheets/d/1FpSz0VYAG-Igb1RJnfWu_DdM55jwSYcStTucSwFitqk/edit?usp=sharing here]. | ||
| − | CPs approved in this ballot are | + | CPs approved in this ballot are Integrated into TF documents published in 2017 and are archived here: ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance/CPs/4_Integrated/2017/ |
{| style="width:95%" border="1" cellpadding="1" | {| style="width:95%" border="1" cellpadding="1" | ||
| Line 301: | Line 301: | ||
Ballot 40 contents, comments/votes, and resolution are gathered [https://docs.google.com/spreadsheets/d/1QiWwKwnrWrEoNtokPUuMv1AugWE754e5ihDg01gXRys/edit?usp=sharing here]. | Ballot 40 contents, comments/votes, and resolution are gathered [https://docs.google.com/spreadsheets/d/1QiWwKwnrWrEoNtokPUuMv1AugWE754e5ihDg01gXRys/edit?usp=sharing here]. | ||
| − | CPs approved in this ballot are | + | CPs approved in this ballot are Integrated into TF documents published in 2017 and are archived here: ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance/CPs/4_Integrated/2017/ |
{| style="width:95%" border="1" cellpadding="1" | {| style="width:95%" border="1" cellpadding="1" | ||
| Line 340: | Line 340: | ||
Ballot 41 contents, comments/votes, and resolution are gathered [https://docs.google.com/spreadsheets/d/1hruDoqH0daltSSymUVWbX6_LFKgul4mO2QxXBykFuU8/edit?usp=sharing here]. | Ballot 41 contents, comments/votes, and resolution are gathered [https://docs.google.com/spreadsheets/d/1hruDoqH0daltSSymUVWbX6_LFKgul4mO2QxXBykFuU8/edit?usp=sharing here]. | ||
| − | CPs approved in this ballot are | + | CPs approved in this ballot are Integrated into TF documents published in 2017 and are archived here: ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance/CPs/4_Integrated/2017/ |
{| style="width:95%" border="1" cellpadding="1" | {| style="width:95%" border="1" cellpadding="1" | ||
| Line 365: | Line 365: | ||
| 956-02 | | 956-02 | ||
| IsSnapshotOf association documentation clean up | | IsSnapshotOf association documentation clean up | ||
| − | | | + | | Approved w/ updates |
|- | |- | ||
| 999-03 | | 999-03 | ||
| Line 411: | Line 411: | ||
Ballot 42 comments/votes, and resolution are gathered [https://docs.google.com/spreadsheets/d/1yxJa2Ti33QQ2xe3j3K_Dn-oeDqc6o_YrNpRvg4pGN4A/edit?usp=sharing here]. | Ballot 42 comments/votes, and resolution are gathered [https://docs.google.com/spreadsheets/d/1yxJa2Ti33QQ2xe3j3K_Dn-oeDqc6o_YrNpRvg4pGN4A/edit?usp=sharing here]. | ||
| − | CPs approved in this ballot are | + | CPs approved in this ballot are Integrated into TF documents published in 2017 and are archived here: ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance/CPs/4_Integrated/2017/ |
{| style="width:95%" border="1" cellpadding="1" | {| style="width:95%" border="1" cellpadding="1" | ||
Latest revision as of 16:21, 16 August 2017
Introduction
This page contains the details of Change Proposal (CP) processing in the ITI domain for the 2016-17 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 for 4 weeks
- 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.
- CP status and ballots are tracked here
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 2016
- 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
All Change Proposal management is done on the IHE ftp site here.
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. Its contents are approved by the Technical Committee and the CP 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 but rejected by the committee
- Cancelled
- contains CPs that were once assigned but have been cancelled, i.e. Cancelled status
- Ballots
- contains Ballots that have been released for voting by the general community
CP status
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 integrated into the ITI Technical Framework
CPs that have passed ballot in since 2015, and that have been, or will be, integrated into the ITI Technical Framework are listed on the "Ballot Log" tab of the tracking spreadsheet.
CPs that have already been integrated into the Technical Framework are stored here: ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance/CPs/4_Integrated/
In Aug 2017, CPs will be integrated & checked following this process : ITI CP Integration Process
Ballots
Ballot 36
Out for ballot: Aug 23 - Sep 23, 2016.
Ballot 36 CPs are archived here: ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance/CPs/Ballots/2017/Ballot_36/
Consolidated comments/votes are gathered here
Comments/votes were reviewed/resolved on the October 7 CP call.
CPs approved in this ballot are Integrated into TF documents published in 2017 and are archived here: ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance/CPs/4_Integrated/2017/
| CP-ITI | Title | Ballot Result |
|---|---|---|
| 738-03 | Replace should deprecate other associations | NOT approved |
| 787-07 | HL7 Encoding in SourcePatientinfo / Patient Id Use of Caret Symbol Clarification | Approved w/ updates |
| 864-05 | Clarification on Association Classifications (TF-3 4.2.2.2) | Approved w/ updates |
| 955-01 | Add DocumentEntry type to FindDocumentsByReferenceId | Approved w/ updates |
| 957-01 | Further Submission Set Immutability Cleanup | Approved w/ updates |
| 958-01 | Effects of Merge on Relationship Associations | Approved w/ updates |
| 960-00 | SoapActionRequired Mandatory | Approved |
| 963-01 | Add Pull Point rqmt to new DSUB Extensions TI Supplement | Approved w/ updates |
Ballot 37
Out for ballot: Sep 29 - Oct 31, 2016
Ballot 37 CPs are archived here: ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance/CPs/Ballots/2017/Ballot_37/
Consolidated comments/votes are gathered here:
Comments/votes were reviewed/resolved on the Nov 4 and 9 CP call
CPs approved in this ballot are Integrated into TF documents published in 2017 and are archived here: ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance/CPs/4_Integrated/2017/
| CP-ITI | Title | Ballot Result |
|---|---|---|
| 559-06 | MPQ profile queries vs Metadata Update option | Approved w/ updates |
| 765-07 | Metadata Update Queries with MU level not set/set to 1 | NOT approved; updated version agreed to during comment resolution and will be re-balloted |
| 810-06 | Update ITI Security Considerations in MU Supplement | Approved w/ updates |
| 939-06 | Update MU Supplement to adjust for redoc of ITI-41 and 42 | Approved w/ updates |
| 962-01 | MU - Add parameters for SQ-FindDocumentsByReferenceId | Approved w/ updates |
| 965-01 | MU - Actor Requirements | Approved w/ updates |
| 966-00 | MU – Correct ATNA Message-No Async | Approved |
| 967-03 | Update XDS-MU for newer XDR content in ITI TF Vol 1 | Approved w/ updates |
Ballot 38
Out for ballot: Dec 29 2016 - Jan 30 2017
Ballot 38 CPs are archived here: ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance/CPs/Ballots/2017/Ballot_38/
Consolidated comments/votes are gathered here.
Comments/votes were reviewed/resolved on the CP call Feb 2, 2017
CPs approved in this ballot are Integrated into TF documents published in 2017 and are archived here: ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance/CPs/4_Integrated/2017/
| CP-ITI | Title | Ballot Result |
|---|---|---|
| 765-15 | Metadata Update Queries with MU level not set/set to 1 shall return only the current Version of an XDSDocumentEntries/XDSFolders | Approved |
| 794-03 | DICOM hyperlinks for audit message specification | Approved w/ updates |
| 824-01 | Display name for audit event 110114 borrowed from DICOM is inconsistent with DICOM display name | Approved |
| 920-01 | Remove IHE Extension from Audit Event table in ITI-20 | Not approved; update rationale; back to assigned |
| 937-10 | DSUB - corrections for audit messages | Not approved; back to assigned to address ballot comments |
| 949-02 | Clarify Folder.lastUpdateTime | Approved w/ update |
| 961-0x | XCDR Cleanup | Approved w/ updates; one change extracted into new CP-ITI-1001 |
| 964-01 | Clarify XDS Async option with regard to transactions actors must support | Approved w/ update to the rationale |
| 969-01 | Allow Documentation on all Relationship Associations | Approved |
| 970-00 | Clarify purpose of hash | Approved |
| 971-01 | Clarify XDSResultNotSinglePatient Error application | Approved |
| 972-04 | Alignment on deprecation text (was Clarification of Chained Associations) | Approved w/ updates |
| 983-00 | Correct Table 4.2.3.2-1 for SourcePatientInfo Data Type | Approved |
| 987-00 | PDQm – Remove unneeded sentences in PDQm Response semantics | Approved |
| 988-00 | PDQm – 2 different errors for Unable to Respond in Requested Format | Approved |
Ballot 39
Out for ballot: Feb 14 - Mar 14, 2017. Comments/votes were resolved on the March 16 CP call
Ballot 39 contents, comments/votes, and resolution are gathered here.
CPs approved in this ballot are Integrated into TF documents published in 2017 and are archived here: ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance/CPs/4_Integrated/2017/
| CP-ITI | Title | Ballot Result |
|---|---|---|
| 923-07 | Redoc aggressive validation specification | Not approved; back to Assigned |
| 973-06 | Association names | Approved w/ updates |
| 990-00 | ITI-18 GetFolders Cleanup | Approved |
| 991-00 | SubmissionSet UniqueId | Approved |
| 993-00 | Specify usage of the AND/OR semantics in XCF parameters | Approved |
| 996-01 | Table V.2.4-1 XML NS and Prefix Corrections | Approved w/ updates |
| 998-01 | Fix AlternativeUserID in ITI-8 audit message | Approved |
| 1008-01 | Clarify NPI in XUA | Approved w/ updates |
| 1009-00 | TooManyResults should be allowed with Partial Success | Approved |
Ballot 40
Out for ballot: Mar 13 - Apr 11, 2017. Comments/votes were resolved on the April 13 CP call.
Ballot 40 contents, comments/votes, and resolution are gathered here.
CPs approved in this ballot are Integrated into TF documents published in 2017 and are archived here: ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance/CPs/4_Integrated/2017/
| CP-ITI | Title | Ballot Result |
|---|---|---|
| 997-03 | Allow multiple entries for PID-3 in sourcePatientInfo | Approved w/ updates |
| 1001-03 | Document the XML namespace and prefix for XCDR | Approved w/ updates |
| 1010-01 | Align supplementary info for InvalidDocumentContent error | Approved w/ updates |
| 1015-01 | Fix example in ITI-24 | Approved w/ updates |
| 1017-06 | Fix ambiguity in Vol 3 Section 4.2.3.1.1 Attribute Value Length' | Approved w/ updates |
| 1018-04 | Remove ITI-62 from XDS Metadata Update TI Supplement | Approved w/ updates |
Ballot 41
Out for ballot: Apr 21 - May 17, 2017. Comments/votes resolved on the May 18 CP call
Ballot 41 contents, comments/votes, and resolution are gathered here.
CPs approved in this ballot are Integrated into TF documents published in 2017 and are archived here: ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance/CPs/4_Integrated/2017/
| CP-ITI | Title | Ballot Result |
|---|---|---|
| 624-04 | Appendix V needs update to reference recent standards | Approved w/ updates |
| 839-06 | Clarify XPID audit messages | Approved w/ updates |
| 923-10 | Redoc aggressive validation specification | Approved w/ updates |
| 937-14 | DSUB - corrections for audit messages | Approved w/ updates |
| 956-02 | IsSnapshotOf association documentation clean up | Approved w/ updates |
| 999-03 | Make ITI-51 audit scheme conformant with DICOM | Approved w/ updates |
| 1016-02 | Clarify Extra Metadata Attributes Section | Approved w/ updates |
| 1020-00 | Remove “temporary” homeCommunityId restriction | Approved |
| 1026-02 | Correct ITI-18 references to missing TF-3 sections | Not approved; back to Assigned |
| 1032-00 | Update Volume 3 Section 4.2.3.1.2 - Creating Coded Attributes For Associations | Approved |
| 1034-01 | UniqueId in Relationships | Approved w/ updates |
| 1035-00 | Volume 3: Correct Section 4.1.4-Submission Request | Approved |
Ballot 42 - Updates to ITI FHIR-based TI Supplements
Out for ballot: May 1 - May 26, 2017.
The ballot announcement is here
Comments/votes to be resolved on webex calls:
- Tues May 30, 9-11 CDT
- Thurs June 1, 9-11 CDT
Ballot 42 contents are here.
Ballot 42 comments/votes, and resolution are gathered here.
CPs approved in this ballot are Integrated into TF documents published in 2017 and are archived here: ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance/CPs/4_Integrated/2017/
| CP-ITI | Title | Ballot Result |
|---|---|---|
| 1005-01 | RESTful ATNA update to FHIR STU3 | Approved w/ updates |
| 1006-01 | mACM updates to FHIR STU3 | Approved w/ updates |
| 1004-01 | PIXm update to FHIR STU3 | Approved w/ updates |
| 1003-01 | PDQm update to FHIR STU3 | Approved w/ updates |
| 826-02 | PDQm - Clarify requirements for Pediatric Demographics | Not approved; back to Assigned |
| 1002-01 | MHD update to FHIR STU3 | Approved w/ updates |
| 940-01 | MHD - ITI-65 should specify how to link to the Binary resource from the DocumentReference | Approved w/ updates |
| 941-01 | MHD - Encoding of UUIDs and OIDs in Identifiers | Approved w/ updates |
| 942-01 | MHD - Encoding of XDSDocumentEntry.referenceIdList in FHIR DocumentReference resource | Approved w/ updates |
| 943-01 | MHD - Encoding of XDSDocumentEntry.uniqueId in FHIR Identifier | Approved w/ updates |
| 944-01 | MHD - Clarification of hash and size attributes in FHIR | Approved w/ updates |
| 945-01 | MHD - ITI-65 should define how to reference patients in a provide transaction | Approved w/ updates |
| 946-02 | MHD - ITI-65 Provide Bundle response status codes should be clarified | Approved w/ updates |
| 1007-01 | Appendix Z updates to FHIR STU3 | Approved w/ updates |
| 1036-01 | Appx Z - Create general FHIR security considerations that can be referenced by other profiles | Approved w/ updates |
Assigned CPs
For a list of CPs that are currently assigned see the 'Active CPs' tab in the CP status google doc.
Assigned CPs are stored here: ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance/CPs/1_Assigned/
Upcoming CP discussions
As of June 29, 2017, we moved to the next CP cycle, and future CP calls will be identified here: http://wiki.ihe.net/index.php/ITI_Change_Proposals_2018#Upcoming_CP_discussions
Agenda and Minutes from past CP calls
See: ITI CPs 2016-17-Agenda and Minutes from past CP calls