ITI Change Proposals 2018: Difference between revisions

From IHE Wiki
Jump to navigation Jump to search
← Older editNewer edit →
Line 321: Line 321:
'''(3) Next in CPs'''
'''(3) Next in CPs'''
* CP Ballot 44 will come out in the coming days w/ completed CPs.
* CP Ballot 44 will come out in the coming days w/ completed CPs.
* We continue Assigned/Iincoming review next Thurs
* Need to identify bundle-focused calls for the rest of 2017


= Agenda and Minutes from past CP calls =
= Agenda and Minutes from past CP calls =

Revision as of 09:56, 10 August 2017

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

Out for ballot: Jun 30 - Aug 1, 2017. Comments/votes resolved on the Aug 3, 2017 CP review call.

Ballot 43 CPs are here: ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance/CPs/Ballots/2018/Ballot_43/

Comments, votes & resolution are here

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

CP-ITI Title Ballot Result
902-03 DSG conformity with ISO 17090-4 Approved w/ updates
974-04 TLS Version in ATNA Approved w/ updates
989-06 Clarify Required Query Parameter Error Codes Approved w/ updates
1041-00 APPC - Fix ReferenceIdList Example Approved
1042-01 APPC – Updates for Provider attributes Approved w/ updates
1046-01 Missing prefix in namespace Approved w/ updates
1048-02 DSG Content Consumer guidance on extra signatures Approved w/ updates
1053-01 Clarify location of document sharing metadata rqmts for BPPC and XDS-SD Approved w/ updates
1055-00 XDS-MU: Missing OnDemand column in Metadata Optionality table Approved


Ballot 44

Out for ballot: Aug x - Sep y, 2017. Comments/votes resolved on the Sep xx, 2017 CP review call.

Ballot 44 CPs are here: ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance/CPs/Ballots/2018/Ballot_44/

Comments, votes & resolution are

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

CP-ITI Title Ballot Result
917-01 Clarify use of Coding Scheme in metadata
976-01 Fix Folder.codeList example
985-11 Relationship Association Target in SubmissionSet
994-01 Increase XDS.b DocumentEntry.uniqueId maximum length
1026-05 ITI-18 cleanup
1057-00 Fix coded values in XDS author role and speciality
1058-02 ATNA Audit Message Optionality Definiitions
1061-01 ITI-18: Correct Queries for "AvailabilityStatus" Attribute


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

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.

July 17-21 ITI Tech F2F

See the face-to-face agenda for times devoted to Maintenance-related topics, and for call in details: July ITI F2F wiki page.

Maintenance topics we will cover, as time allows, are listed below. This will likely be modified during the week. They are more-or-less in priority order.

Quick links

(1) CPs that just need review - Assigned CPs with changes ready for the committee to confirm/tweak.

  • XDS-Vol3 bundle
    • 977-00 - datatype clarification for phone number (Rob)
    • 994-00 - Increase XDS.b DocumentEntry.uniqueId maximum length (Nick Radov) -- updated and now Completed are ready for future ballot
    • 1050-00 - Appendix B Cleanup (Elliott L) -- reviewed and scope was expanded; remains Assigned
    • 976-01 - Fix Folder.codeList example (Tarik) -- reviewed and now Completed and ready for future ballot 44
    • 917-00 - Recommend using OIDs for codingScheme (Rob) -- reviewed, updated, and now Completed and ready for future ballot 44
    • 925-02 - Clarify UTC offset within DTM datatype (Nader) - discussed; will be Cancelled
  • Security bundle
    • 1013-01 - Clarify UDP requirements in ITI-20 (again) (Rob)
  • Security-Audit bundle
    • 920-02 - Restore IHE Extensions in ITI-20 (Rob)
    • 938-01 - Audit messages for ITI-30 and 31 (Lynn)
  • HL7v3 bundle
    • 795-00 - Fix to match ITI-44 TF text to the schema
  • editorial bundle
    • 1022-00 - Specification of ITI-30 as optional transaction in PIX is incomplete (Lynn)

(2) Low-hanging fruit - CPs that could be finished with a bit of heads-down attention by editor, followed by committee confirmation

Those known to be attending the F2F are listed below with CPs that seem close to completion. Feel free to choose a different CP to work on.

  • Charles
    • 866-00 - Wrong Transaction Labels in XCDR Figure
  • Rob
    • 1047-00 - Remove mandatory User Authentication from ITI-19
    • 968-02 - Fix optionality for AlternativeUserId field in SeR audit messages ( - refer to Completed CP 1058-02 'ATNA Audit Message Optionality Definitions'
  • John
    • 736-00 - clarification of BPPC type code
    • 709-03 - Accounting of Disclosures audit message
  • Mauro
    • 915-00 - Clarify definition of COMPLETED task status in XDW
    • 1054-00 - XDW: Datatype fix and update diagram (Mauro or Gregorio)
  • Sylvie
    • 1052-00 - Corrections to Document Sharing Cardinality in Diagrams (review and make a recommendation: update the diagrams, or remove cardinality)
  • Ben
    • 1049-00 - Distinction between PIX vs PDQ should be made more clear
  • Elliot S
    • co-chair's choice
  • Joe
  • Luke
  • Eric
    • Any HPD: 766 or 921
  • Chris
  • Lynn
    • 541-03 - Remove configurable fallback for empty PID-3.4

(3) CPs that will benefit from broad committee input to provide direction

  • 1060-00 - Need Null Flavor for FormatCode
  • others to be brought forward...

(4) Tackle the 'optionality' monster Committee discussion to examine current state (optionality defined many, many place) and decide on a path forward.

  • Considerations:
    • CP 1059 - Refine optionality definitions in FHIR Appx Z (assigned to Elliot S)
    • IHE Common Appendix E (been there since 2014; largely unknown) See http://ihe.net/TF_Intro_Appendices.aspx
      • E.2 Profiling DICOM
      • E.3 HL7 Message Profiling Conventions
      • E.3.1 HL7 Message Profiling Conventions
      • E.4 (CDA) Optionality Constraints
    • ITI TF-2x: Appendix C - HL7 profiling conventions
    • ITI TF-3: Table 4.2.1-2 Sending Actor Metadata Attribute Optionality Code Definitions
    • ITI TF-3: Table 4.3.2.1-2 Responding Actor Metadata Attribute Optionality Code Definitions
    • ITI TF-3: 5.4.3 Optionality Definitions for XDW
    • ITI TI Supp Appx Z.20 Profiling conventions for constraints on FHIR
  • ITI TF-4: 4.1 Optionality for French extensions
    • Others in ITI documents..??
    • Definitions in underlying standards...
    • In other domains (not exhaustive list)
      • RAD TF-2:2.2 DICOM Usage Conventions
      • RAD TF-2:2.3 HL7 profiling conventions
      • CARD (and EYECARE) TF-2: 2.2 DICOM Usage conventions
      • CARD TF-2:2.3 HL7 profiling conventions
    • Others??

(5) Soliciting suggestions to the CP process for the coming year

  • ideas...???
  • some progress on move to Jira for tracking
  • create bundle-specific call schedule for fall??

(6) CPs that need a new owner

  • HL7v2 bundle
    • 211 - PIX/PAM integration
    • 307 - PDQ Continuation Protocol in One Socket or Multiple Sockets
    • 718 - Namespace ID required even if ISO OID set
  • Security bundle
    • 897 - Clarify that rqmts in ITI-19 provide a baseline set, and are not mandated at all deployments
  • XDS-Vol3 bundle
    • 817 - Add the Reference ID List slot to the Submission Set metadata

Aug 10, 2017

Time: 10:00-11:00am CDT

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

Meeting: 924 199 009

Password: Meeting1

Attendees:

--> ITI CP Tracking Spreadsheet is here.

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

  • 795-01 - Fix ITI-44 text to match the schema - confirm this small change:
  • Doc Sharing, Vol 3 CPs:
    • 995-02 - Align entryUUID descriptions (Tarik)
    • 977-01 - datatype clarification for phone number (Rob)
    • 1019-02 - Clarify Repository action required on duplicate uniqueId (Elliot)
    • 720-03 - Clarify Replacement for addendum and transformation docs
  • Security CPs
    • 920-02 - Restore IHE Extensions in ITI-20 (Rob)
    • 938-01 - Audit messages for ITI-30 and 31
  • Other
    • 795-01 - Fix ITI-44 text to match the schema
    • 1022-00 - Specification of ITI-30 as optional transaction in PIX is incomplete

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

  • CP-ITI-CXiExampleReferral.doc
  • CP-ITI-XUA-Subject-ID-XSPA.doc
  • CP-ITI-FixITI-54auditMsg.docx
  • CP-ITI-FixITI-86auditMsg.docx
  • CP-ITI-LF-AppxG-RemoveOutOfDateText.doc
  • CP-ITI-FixOutOfDateTFreference.docx

(3) Next in CPs

  • CP Ballot 44 will come out in the coming days w/ completed CPs.
  • We continue Assigned/Iincoming review next Thurs
  • Need to identify bundle-focused calls for the rest of 2017

Agenda and Minutes from past CP calls

See: ITI CPs 2017-18-Agenda and Minutes from past CP calls

Future CP prevention work

Exploring a new approach to audit message specification

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