Difference between revisions of "ITI Change Proposals 2018-19"

From IHE Wiki
Jump to navigation Jump to search
Line 238: Line 238:
 
'''The ITI CP tracking spreadsheet''' is [https://docs.google.com/spreadsheets/d/1gdr_Y8xZBvbb326J4z67cqprxOexFgtkPj_VlD3rB9E/edit#gid=0 here].
 
'''The ITI CP tracking spreadsheet''' is [https://docs.google.com/spreadsheets/d/1gdr_Y8xZBvbb326J4z67cqprxOexFgtkPj_VlD3rB9E/edit#gid=0 here].
  
'''(3) Process Incoming CPs'''  ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance/CPs/0_Incoming/
+
'''(1) Assigned CPs Ready for Discussion'''  ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance/CPs/1_Assigned/
 +
* 1093 - XDSUnknownPatientId error should be allowed in ITI-18 (John)
 +
* 1131 - ATNA – Clarify ITI-19 rqmts for All Connections carrying Protected Information (Elliot S)
 +
* 1087 - DEN and mimeTypeSufficient (John)
 +
 
 +
'''(2) Process Incoming CPs'''  ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance/CPs/0_Incoming/
 
* CP-ITI-SK-AssignedDeviceClasscode.doc
 
* CP-ITI-SK-AssignedDeviceClasscode.doc
 
* CP-ITI-LF-XCA-DocConsumerOptions.doc
 
* CP-ITI-LF-XCA-DocConsumerOptions.doc
 
* CP-ITI-LF-FixSectionNumberAS4supp.doc
 
* CP-ITI-LF-FixSectionNumberAS4supp.doc
* more tbd....
 
  
'''(2) Assigned CPs Ready for Discussion''' ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance/CPs/1_Assigned/
+
''' (3) Input on prioritization and categorization of MU/RMD CPs -- from Ken'''
* 1093 - XDSUnknownPatientId error should be allowed in ITI-18 (John)
+
Group One
* 1131 - ATNA – Clarify ITI-19 rqmts for All Connections carrying Protected Information (Elliot S)
+
 
* 1087 - DEN and mimeTypeSufficient (John)
+
<u>XDSb (needs a solution first)</u>:
 +
* 1021 - Clarify ITI-42 Expected Actions For Folders During RPLC/XFRM_RPLC  (XDSb)
 +
* 1071 - Clarify Replacement Associations (dependent on 1021) (XDSb)
 +
 
 +
<u>MU (and friends...that need XDSb resolved)</u>:
 +
* 1028 - MU-Add Requirements For Propagating SS-HM Associations 
 +
* 1030 - MU-Clarify Requirements For Propagating Relationship Associations
 +
* 1029 - MU: Clarify Requirements for Association Submit/Update Operations (parts can be handled independently - have more notes from Bill)
 +
 
 +
* 982 - MU Trigger Documentation (fell into the RMU trap - documentation)
 +
* 1031 - Reconcile XPID and MU Requirements (concurrent effort .. was assuming that MU would have been also been re-documented. XPID should be cross-referenced with aforementioned CPs.
 +
 
 +
<u> Group Two (Small) </u>:
 +
751 - UUID Type Incorrect Use in UML diagrams (XDSb) - yes, title is wrong...attempt to clean up the use of UUID and symbolicId
 +
981 - Conflict in ID format when updating & changing status (better defining use of symbolic Ids in MU submissions) (MU)
 +
 
 +
<u>Documentation Efforts (Work Items)</u>:
 +
* 1072 - Update Vol 3 graphics associated with replace/transform... This was important for communication in order to have everyone on the same page.
 +
* 1044 - Update Vol. 1, and Vol 2 Appendices to reflect RMD and XDS-M
  
 
'''(4) Next in CPs'''
 
'''(4) Next in CPs'''

Revision as of 16:39, 18 December 2018

This page contains the details of Change Proposal (CP) processing in the ITI domain for the 2018-19 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.

  1. Write a change proposal. Here is IHE's Change Proposal Template
  2. 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).
  3. 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.
  4. Committee works with editor to draft the CP. Versions are kept in Assigned directory and numbered -00, -01, -02, etc.
  5. Committee decides CP is ready for ballot. Latest version of CP is moved to Completed diretory and old versions are moved to old_versions.
  6. Co-chair collects Completed CPs into a ballot. The Ballot directory will be used for this.
  7. Ballot is released to the general community for voting for 4 weeks
  8. 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.
  9. CP approved in ballot are put in FinalText and scheduled to be integrated into the Technical Framework or Supplement.
  10. 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 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 in the upcoming publication cycle.
Integrated
contains the version of the CP that was integrated into the TF, organized by year.
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, organized by year.

CP status

ITI tracks status of its Change Proposals in this google doc: https://docs.google.com/spreadsheets/d/1gdr_Y8xZBvbb326J4z67cqprxOexFgtkPj_VlD3rB9E/edit?usp=sharing The Active CPs tab contains those that are Assigned, Completed, or Final Text in this cycle. There are also archive tabs for prior years.

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 "Approved CPs" 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 2018, CPs will be integrated & checked following this process : ITI CP Integration Process

Ballots

Ballot 48

Out for ballot: June 8 - July 9, 2018. Comments/votes resolved on the July 12, 2018 CP review call.

Ballot 48 CPs are here: ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance/CPs/Ballots/2019/Ballot_48/

Comments, votes & resolution are here

CPs approved in this ballot are Final Text and are stored here until they are incorporated in 2019: ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance/CPs/3_FinalText/

CP-ITI Title Ballot Result
1094-08 ATNA - Add Option: Require server certificate domain name validation for all traffic over the public internet Failed ballot; will be reballoted in Ballot 49
1124-09 ATNA – Add two options related to BCP195 TLS Secure Transport Connection Failed ballot; will be reballoted in Ballot 49


Ballot 49

Out for ballot: Aug 10 - Sep 10, 2018. Comments/votes were resolved on the Sep 13, 2018 CP review call.

Ballot 49 CPs are here: ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance/CPs/Ballots/2019/Ballot_49/

Comments, votes & resolution are here.

CPs approved in this ballot are Final Text and are stored here until they are incorporated in 2019: ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance/CPs/3_FinalText/

CP-ITI Title Ballot Result
697-02 PIXv3 Query Result Approved w/ updates; pending confirmation of update by Change HC
1094-10 ATNA - Add Option: Require server certificate domain name validation for all traffic over the public internet Approved w/ updates. This CP is cancelled, but approved text is now in CP-ITI-1145; see below.
1124-12 ATNA – Add two options related to BCP195 TLS Secure Transport Connection Approved w/ updates. This CP is cancelled, but approved text is now in CP-ITI-1145; see below.
1122-08 Redocumentation of Appendix V on SOAP Web Services Approved w/ updates; Vol 2x to be republished in Oct
1123-04 Redocumentation of Appendix V – HL7 V3 Sections Approved w/ updates; Vol 2x to be republished in Oct
1145-01 ATNA – Add three options affecting ITI-19 Approved. Includes text with resolved comments from CP 1094 and 1124 above


Ballot 50

Out for ballot: Sep 25 - Oct 24, 2018. Comments/votes resolved on the Oct 25, 2018 CP review call.

Ballot 50 CPs are here: ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance/CPs/Ballots/2019/Ballot_50/

Comments, votes & resolution are here.

CPs approved in this ballot are Final Text and are stored here until they are incorporated in 2019: ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance/CPs/3_FinalText/

CP-ITI Title Ballot Result
1051-01 Align BPPC Vol 1 with convention for Content Profiles & Grouping Failed ballot; needs to be addressed more broadly; back to Assigned
1134-00 Author Person Required Approved
1135-01 SAML – multiple levels of nesting must be supported Approved w/ updates.
1137-00 healthCareFacilityTypeCode example fix in ITI-18 Approved
1138-01 Update Form Receiver and Form Processor Role Definition in ITI-35 Approved
1139-00 NPFSm – wrong actor in message semantics Approved
1140-00 ITI TF-1 reference to background material is out of date Cancelled. Updated links in the TF to ihe.net now have redirects. This change is not needed.
1141-00 XCF – example is inconsistent with list of attributes
1142-00 Remove extra spaces in attribute values in ITI-43 Approved
1143-01 DEN: update to formatCode was done on pre-redoc Vol 3 content Approved w/ update.
1144-01 Reference in Vol 3 is circular rather than helpful Approved w/ updates.
1146-00 DSUB - Correct SubmissionSet Suscription Filter Text
1147-00 Out-of-date DICOM reference in ITI-19 Approved


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/

Strategies for smarter CP processing (from Jul-17 F2F)

We often have CPs that need a lot of rework after ballot:

  • There is not enough review prior to ballot
  • Perhaps too much effort on specificity vs remaining silent
  • Look for opportunities to suggest that a small subset take a time-consuming or editorial problem offline and come back to the group with an updated change.

Gateway questions prior to accepting a CP (or finishing work on an existing CP):

  • Is solving the problem necessary for interoperability?
  • Has an implementer reported this problem, or should they, or... is this theoretical?
  • Is the text inconsistent? If so, are we over-specifying, i.e. can we delete the inconsistency?
  • Strongly suggest that a submitter propose a solution.
  • Is this a problem that needs to be fixed?

Upcoming CP discussions

ITI CP review calls are typically held every Thursday from 10-11am Central US. Additional sessions may be scheduled during ITI Tech F2F meetings. Changes to the 'traditional' schedule for CP calls are announced on the ititech email list.

The Google Doc used to gather availability of ITI Tech Members and the focus of future CP calls is here.


Dec 20, 2018

Time: 10:00 - 11:00 CDT

Webex link: https://himss.webex.com/himss/j.php?MTID=m55e2149a5607fd5d96dc5d80f57dd434

Meeting: 926 708 864

Password: Meeting1

Attendees:

The ITI CP tracking spreadsheet is here.

(1) Assigned CPs Ready for Discussion ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance/CPs/1_Assigned/

  • 1093 - XDSUnknownPatientId error should be allowed in ITI-18 (John)
  • 1131 - ATNA – Clarify ITI-19 rqmts for All Connections carrying Protected Information (Elliot S)
  • 1087 - DEN and mimeTypeSufficient (John)

(2) Process Incoming CPs ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance/CPs/0_Incoming/

  • CP-ITI-SK-AssignedDeviceClasscode.doc
  • CP-ITI-LF-XCA-DocConsumerOptions.doc
  • CP-ITI-LF-FixSectionNumberAS4supp.doc

(3) Input on prioritization and categorization of MU/RMD CPs -- from Ken Group One

XDSb (needs a solution first):

  • 1021 - Clarify ITI-42 Expected Actions For Folders During RPLC/XFRM_RPLC (XDSb)
  • 1071 - Clarify Replacement Associations (dependent on 1021) (XDSb)

MU (and friends...that need XDSb resolved):

  • 1028 - MU-Add Requirements For Propagating SS-HM Associations
  • 1030 - MU-Clarify Requirements For Propagating Relationship Associations
  • 1029 - MU: Clarify Requirements for Association Submit/Update Operations (parts can be handled independently - have more notes from Bill)
  • 982 - MU Trigger Documentation (fell into the RMU trap - documentation)
  • 1031 - Reconcile XPID and MU Requirements (concurrent effort .. was assuming that MU would have been also been re-documented. XPID should be cross-referenced with aforementioned CPs.

Group Two (Small) : 751 - UUID Type Incorrect Use in UML diagrams (XDSb) - yes, title is wrong...attempt to clean up the use of UUID and symbolicId 981 - Conflict in ID format when updating & changing status (better defining use of symbolic Ids in MU submissions) (MU)

Documentation Efforts (Work Items):

  • 1072 - Update Vol 3 graphics associated with replace/transform... This was important for communication in order to have everyone on the same page.
  • 1044 - Update Vol. 1, and Vol 2 Appendices to reflect RMD and XDS-M

(4) Next in CPs

  • Dec 27 -- no ITI CP call - end of year break
  • Jan 3 - CP calls resume for 2019

Dec 27 -- No ITI CP call

Jan 3, 2019

Time: 10:00 - 11:00 CDT

Webex link: https://himss.webex.com/himss/j.php?MTID=m55e2149a5607fd5d96dc5d80f57dd434

Meeting: 926 708 864

Password: Meeting1

Attendees:

The ITI CP tracking spreadsheet is here.

(1) Process Incoming CPs ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance/CPs/0_Incoming/

  • tbd

(2) Assigned CPs Ready for Review ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance/CPs/1_Assigned/

  • tbd

(3) Next in CPs

  • ...

Minutes from past CP calls

See ITI CPs 2018-19-Agenda and Minutes from past CP calls