ITI Planning Committee 2015/2016 Meetings: Difference between revisions

From IHE Wiki
Jump to navigation Jump to search
Eheflin2 (talk | contribs)
No edit summary
Eheflin2 (talk | contribs)
 
(191 intermediate revisions by 3 users not shown)
Line 11: Line 11:
:*Each webinar will be divided into 20-minute time-slots, with the remaining time for introductory remarks and follow-up discussion.  
:*Each webinar will be divided into 20-minute time-slots, with the remaining time for introductory remarks and follow-up discussion.  
:*Each 20-minute time slot will be allocated to a profile/white paper proposal… the first 10 minutes will be taken up by a presentation by the proposal author, with the remaining 10 minutes reserved for discussion and any disposition (if required).  
:*Each 20-minute time slot will be allocated to a profile/white paper proposal… the first 10 minutes will be taken up by a presentation by the proposal author, with the remaining 10 minutes reserved for discussion and any disposition (if required).  
:*Each 10-minute presentation will be comprised of a maximum of 5 Powerpoint slides, presenting the proposal concisely and completely.
:*Each 10-minute presentation will be comprised of a maximum of 5 Powerpoint slides, presenting the proposal problem statement concisely and completely.


==Webinar 1==
==Webinar 1==
All times are Central Time


{| style="width:95%" border="1" cellpadding="1"
Webinar #1 was not needed and has been canceled.  Please see below for the schedule for the remaining webinars.
! Date
! Time
! Coordinates
! Recording of the meeting
|-
| 2015-Oct-13
| 10:00-12:00pm CDT
|[https://himss.webex.com/himss/j.php?MTID=mcf547147f4229d192fac8c98ddb215f9 Join Webex](password "meeting")


| Download Recording of Webinar #1
==Webinar 2==
|}


{| style="width:95%" border="1" cellpadding="1"
Webinar #2 was not needed and has been canceledPlease see below for the schedule for the remaining webinars.
! Time
! Proposal
! Author/Presenter
! Comments
|-
| 8:00-8:10
| Webinar Introduction, process
| Eric Heflin, Daniel Berezeanu : Co-Chairs
| The goal for this week's call is to just explain and socialize the problem.  Not to prioritize, not to select, not to talk about solution. Presenters should be prepared to present their brief proposal papers, or a power point with the same basic concepts.
|-
| 8:10-8:30
| [ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr13-2015-2016/Planning_Cmte/BriefProfileProposals/SAMLHealthcareWorkflowsProposal.docx SAML for Healthcare Workflows Deployment Profile]
| Alex DeJong
| Q: What is the relationship between this proposal and OATH?  A: To be determined, but the presenter recognizes that OATH may be important to include in the proposed workflows. Q: What countries have been identified that would be interested in using this? A: USA and Austria have been identified so far.
|-
| 8:30-8:50
| [ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr13-2015-2016/Planning_Cmte/BriefProfileProposals/IHESAMLwithHContextProposal.docx Health Context Sharing via SAML]
| Alex DeJong
| Q: Could this proposal be worked on in several phases: A: Probably. Q: What are the relationships between the two SAML proposals?  A: Different workflows.  One for overall patient medical record access, and one for rendering a specific patient or document.
|-
| 8:50-9:10
| [ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr13-2015-2016/Planning_Cmte/BriefProfileProposals/IHE_Profile_Proposal_ATNAquery-Brief2014.docx ATNA Query]
| Mauro Zanardini
| Q: Is this to generate computer or human readable responses? A: Both. Q: Would this include filtering?  A: Yes. Canada is interested in filtering.  Q: How many countries are interested?  A: Italy, many countries, 9 European countries. Presenter felt all other countries focused on IHE profiles would likely be of interest.  Q: Would this be implemented via stored queries? A: Yes.  It would be driven by use cases, and a limited set of stored queries.  Q: Are other domains interested in this profile?  A: QRPH would likely be interested.
|-
| 9:10-9:30
| [ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr13-2015-2016/Planning_Cmte/BriefProfileProposals/ITI_Restful_ATNA_Repository_access.docx ATNA Repository RESTful Access]
| Rob Horn
| Q: What are the differences or similarities between this proposal and the prior ATNA Query proposal?  A: The proposals probably should be combined.  Need to decide if this is restricted to healthcare only or is broader including for example building security events. Q: What is the target for this profile? A: Application developers more than patients or end users.  Q: Is this a topology profile? A: Yes. But that's not all.  It standardizes and allows applications the ability to interoperate.  Q: Is it of value as a interoperability profile?  A: Yes, this is a real problem for application developers. Q: What is the country target? A: A number of European countries, Canada, and USA. Q: Are other IHE Domains interested in this profile? A: We have not had that conversation yet but the presenter feels that the other IHE domains would likely view this as a problem for ITI to fix.
|-
| 9:30-9:50
| [ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr13-2015-2016/Planning_Cmte/BriefProfileProposals/XDN-BriefProposal-renamedFromVIAA.docx Cross-Enterprise Document Network Interchange (XDN)]
| Fred Behlen
| Q: Is this a profile for a direct connection to a file storage device? A: Yes, via an interoperable profile.  Q: What other countries and IHE domains are targets?  A: Unknown at this point.  The presenter asked if those on the call were aware of networking storage standards that could be leveraged? A: It was suggested to focus on the problem statement for now.  Q: Is this a breaking change? A: No.  The Document Consumer and Document Repository actors would be unchanged for legacy actors, but new actors could leverage the new document retrieval information if they are aware of the solution and if they so chose. Q: Would the metadata be generated? A: Currently this is likely viewed out of scope.  Q: How is this different than having documents make references to URL resources? A: The URL is a slot in the document entry in the registry.  Q: What would be held in the XDN Document Repository? A: Needs to be determined. Q: What's the industry value?  A: Large numbers of systems will need a solution like this as they are decommissioned. Q: Is this an interoperability problem.  Q: Yes, for internal organizations as they merge and evolveBut it may not be an interop program across organizations.  This likey touches on a new phase of the document lifecycle that we've addressed so far.
|-
| 9:50-10:00
| Discussion, Next Steps
| Co-Chairs
| Next steps: 1) more Brief Proposal webinars scheduled (please see below on this page for the details), 2) you should listen to all webinars prior to the October face-to-face meetings, 3) in Oct f2f meetings the ITI Planning Committee we will dive into these more deeply and assess against criteria in the spreadsheet (fit, value, effort, etc.), 4) vote on which move forward to ITI TC for their assessment. Also a reminder: All presenters should send their presentations so they can be posted on the public ftp site.
|}


==Webinar 2==
==Webinar 3==


All times are Central Time
All times are Central Time
Line 81: Line 30:
! Coordinates
! Coordinates
! Recording of the meeting
! Recording of the meeting
|-  
|-
| 2014-Oct-06
| 2015-Oct-15
| 8:00-10:00 CDT
| 12:00pm-2:00pm CDT
|[https://himss.webex.com/himss/j.php?MTID=m66b60834dab196f8b89442cca8fc9df3 Join webex](password "meeting")
|[https://himss.webex.com/himss/j.php?MTID=mf97d918c3dd68a2a033318d3e8363b33 Join Webex](password "meeting")
 
| [https://himss.webex.com/himss/lsr.php?RCID=efb4b070aadb4d97b331f23ae40d5dda Download recording of Session #3]
| [https://himss.webex.com/himss/lsr.php?RCID=d9196fc56f2b46368e160859637057a3 Download Recording of Session #2]
|}
|}
{| style="width:95%" border="1" cellpadding="1"
{| style="width:95%" border="1" cellpadding="1"
! Time
! Time
Line 95: Line 42:
! Comments
! Comments
|-
|-
| 8:00-8:10
| 12:00pm-12:10pm
| Webinar Introduction, process
| Webinar Introduction, process
| Eric Heflin, Daniel Berezeanu : Co-Chairs
| Daniel Berezeanu, Eric Heflin : Co-Chairs
| Re-iterated message from prior call to focus on the problem, not the solution.
| The goal for this series of webinars is to just explain and socialize the problem. The goals is NOT for the presenter to talk about the solutionAnd the goals is NOT for the ITI PC to prioritize or select which brief proposals move forward. Presenters should be prepared to present their brief proposal papers, or a power point with the same basic concepts. All webinars will be recorded and publicly postedAll ITI PC members are expected to review the webinars (live or via the recordings) prior to the F2F meetings.
|-
| 8:10-8:30
| [ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr13-2015-2016/Planning_Cmte/BriefProfileProposals/IHE_Profile_Proposal_Cross-Community.docx Next steps in Cross Community]
| Karen Witting
| Noted that this is an ITC PC activity, not an ITI TC activity. Q: Will this profile proposal include resources? A: Yes, the presenter will be the lead editor provided she is not working on her other proposal.  Q: What would be the format of this work product?  A: Enhancement to existing IHE for HIE white paper, or a separate WP, or a new WP.  An educational webinar would be possible too.  Comment was made that this should handle both projects with and without national IDs.  Another comment was made to not prescribe architectures, but that other architectural approaches may be worth mentioning in the work product.
|-
| 8:30-8:50
| [ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr13-2015-2016/Planning_Cmte/BriefProfileProposals/IHE_Profile_Proposal_XDStarRedoc-Brief.docx Redocumentation of XD* Profiles]
| Karen Witting
| Resubmission of prior proposalThe presenter can only work on one of her two proposals. Q: What's the size?  A: Medium large.  Q: Can this also include an conformance statement number for requirements traceability: A: Not viable from the perspective of the presenter.
|-
| 8:50-9:30
| [ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr13-2015-2016/Planning_Cmte/BriefProfileProposals/DAF%20Document%20IG_IHE_BriefProposal.docx Data Access Framework Document Access Implementation Guide]
| Dragon
| Last year presented a whitepaper was created for DAF under IHE ITI and IHE PCC jointly.  This year's proposal builds on the work from last year to make it more specific for for SOAP and REST.  An implementation guide has or will be created. Q: Is this going to be USA specific? It is of use to many other countries such as South Africa.  A: The ONC may be able to accommodate more of an international focus. A comment was made that this should not be USA-specific otherwise it is more limited in impact that possible, and it detracts from international work.  Another comment was made that the ONC seems receptive to work that is of use internationally.  
|-
| 9:30-9:50
| [ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr13-2015-2016/Planning_Cmte/BriefProfileProposals/ITI_National_Extensions_for_Confidentiality.docx National Extensions for Confidentiality]
| Rob Horn
| This proposal is an extension to the existing Data Segmentation for Privacy to extend it to be of use to other countriesA comment was made multiple other countries have worked on this now and are likely to be ready now.  France was mentioned as being a possible candidate target.  Determine data, by Oct 23rd, about other international targets.  A comment was made that most countries have already solved this via local laws and regulation. Q: What's the benefit? A: To normalize the solution across countries as there are multiple implementations in-flight that would likely have variations.  Presenter suggests dropping this if no other countries indicate interest prior to Oct f2f ballot.
|-
|-
| 9:50-10:00
| 12:10pm-12:30pm
| Discussion, Next Steps
| [ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr14-2016-2017/Planning_Cmte/BriefProfileProposals/IHE_Profile_Proposal_EnhancedPatientPrivacyConsents_v1.0.docx Enhanced Patient Privacy Consents]
| Co-Chairs
| Tarik Idris, John Moehrke, Frank Oemig, Jörg Caumanns
|
| 1-Facility specific consent
|}
2-Consent for an episode of care
3-Provider blacklist, document author/source, document metadata, roles, Xid


==Webinar 3==
There seems to be some overlap with existing standards. A full standards assessment will be required once the profile work begins.


All times are Central Time
Use of stylesheets, what will be the source of the policy statements, how are you planning to address specific policies. There could be many different sources of policies, but there are different approaches that could be applied including a central approach
We are looking to create a portion in consent within probably PBBC, which they can use the meaning behind the modifications to core consent.
Will this be applied to nation, state legislations within a determined structure?  We can certainly within IHE have specific reach outs but normal public comment mechanism should be minimally acceptable.


{| style="width:95%" border="1" cellpadding="1"
! Date
! Time
! Coordinates
! Recording of the meeting
|-
|-
| 2014-Oct-07
| 12:30pm-12:50pm
| 8:00-10:00 CDT
| [ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr14-2016-2017/Planning_Cmte/BriefProfileProposals/IHE_Profile_Proposal_DocSharingProfilesRedoc-Breif-09-24.docx Re-documentation of Document Sharing Profiles]
|[https://himss.webex.com/himss/j.php?MTID=mb20166dc2c3ec9c639e5bfc2b99c761a Join Webex](password "meeting")
| Karen Witting
|[https://himss.webex.com/himss/lsr.php?RCID=1f827b6f8c0445708254ec30391ba023 Download recording of Session #3]
| What is the positive impact of this work on IHE?
|}
Phase 1 most important, phase 2 more focused, the impact would be about the same as phase 2 and will provide significant impact with minimal work effort. The clarification and re-documentation of the existing standards provides ease of use and implementation without changes to any conformance criteria.
{| style="width:95%" border="1" cellpadding="1"
How was the decision on what order the profiles to re-document? The work group decided to cover the provide, register and retrieve transactions and would be complete and the Query transaction in a later phase.
! Time
! Proposal
! Author/Presenter
! Comments
|-
| 8:00-8:10
| Webinar Introduction, process
| Eric Heflin, Daniel Berezeanu : Co-Chairs
| Re-iterated message from prior call to focus on the problem, not the solution.
|-
| 8:10-8:30
| [ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr13-2015-2016/Planning_Cmte/BriefProfileProposals/IHE_Profile_Proposal_Alerts-Brief.docx Alerts Targeted at Humans]
| Carl Leitner
| OpenHIE community has been working on this. This concept has been approved twice (floundered due to lack of implementor support).  Countries of interest are in Liberia, New Guinea, Nigeria, Sierra Leon and many more. Q: How will this integrate into workflow? Will this be one-way or closed loop communications? A: These capabilities are under consideration.  Related to a PCC proposal for this year.  Comment: Need to include patient into the workflow.  Community will likely provide 5-10 people working on this. Carl can be the editor.  Other resources are committed too.
|-
| 8:30-8:50
| [ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr13-2015-2016/Planning_Cmte/BriefProfileProposals/AHIMA_Submission_to_IHE_ITI_HIT_Standards_for_IG_Final_2014-09-18.pdf HIT Standards for Information Governance White Paper]
| Anna Orlova
| Q: Are they approaching other IHE workgroups or the Board?  A: No. Only ITI for now. Q: How does this overlap with the HL7 Data Governance work?  A: The efforts are similar.  This proposal may serve a way to rationalize the efforts.  Q: Is this USA specific? A: No.  Would be broad.
|-
| 8:50-9:10
| [ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr13-2015-2016/Planning_Cmte/BriefProfileProposals/ITI_QRPH_Family_Planning_DeIdentification_04.docx De-identification of healthcare data to central reporting authority]
| Johanna Goderre Jones
| This is being submitted to ITI and QRPH at the same time to coordinate across domains. Would possibly be a case study for the existing IHE De-identification white paper.  Q: What countries would be interested?  A: At least France, USA, Italy, probably many others. Comment: This represents a way to educate people on how to use de-identification.  Also, this is a likely good way to pilot the de-identification paper to make sure it works well by collaborating with ITI TC.  Had over 600 comments, many from clinical people.  Shows good community interest.  Q: Would resources be available to assist? A: Broad community support. State of LA Dept of Health can likely provide resources.
|-
|-
| 9:10-9:30
| 12:50pm-1:10pm
| [ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr13-2015-2016/Planning_Cmte/BriefProfileProposals/ITI_Restful_PIX.docx RESTful PIX]
| [ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr14-2016-2017/Planning_Cmte/BriefProfileProposals/IHE_Work_Item_Proposal_2016_AHIMAImplementWhitePaper%20FINAL.docx HIT Standards for HIM Practices: Implementable White Paper Proposal]
| Rob Horn
| Harry Rhodes, Anna Orlova, Diana Warner
| Q: Can Rob help write this profile?  A: Probably.  Q: Why should IHE do this instead of HL7? Can this be a joint effort? A: Let's wait on HL7 if they are going to work on this. Comment: HL7's normal method is to work with others like IHE to profile items like this.  Q: What other countries are interested in this?  Comment: FHIR for PIX is a next logical step for core ITI work.  Useful for DICOM Web.
| Can this effort be internationalized? Yes, we are already working internationally with collaborators.
Impact, original WP received 149 comments external to ITI, HIM vendors and implementers are showing much interest in the work IHE is doing.
|-
|-
| 9:30-9:40
| 1:10pm-1:20pm
| Discussion, Next Steps
| Discussion, Next Steps
| Co-Chairs
| Co-Chairs
|
| Next steps: 1) more Brief Proposal webinars scheduled (please see below on this page for the details), 2) you should listen to all webinars prior to the October face-to-face meetings, 3) in Oct f2f meetings the ITI Planning Committee we will dive into these more deeply and assess against criteria in the spreadsheet (fit, value, effort, etc.), 4) vote on which move forward to ITI TC for their assessment. Also a reminder: All presenters should send their presentations so they can be posted on the public ftp site.
|}
|}


==Webinar 4==
==Webinar 4==


All times are Central Time
All times are Central Time.  This call will be recorded and publicly posted.


{| style="width:95%" border="1" cellpadding="1"
{| style="width:95%" border="1" cellpadding="1"
Line 188: Line 90:
! Recording of the meeting
! Recording of the meeting
|-
|-
| 2014-Oct-14
| 2015-Oct-19
| 8:00-10:00 CDT
| 3:30pm-5:30pm CDT
|[https://himss.webex.com/himss/j.php?MTID=mb20166dc2c3ec9c639e5bfc2b99c761a Join Webex](password "meeting")
|[https://himss.webex.com/himss/j.php?MTID=m8ebb4b9cfeca04ae8667521cee0d1d12 Join Webex](password "meeting")
| [https://himss.webex.com/himss/lsr.php?RCID=c5c5918ea48746578e3211388ef42c69  Download recording of Session #4]
| [https://himss.webex.com/himss/lsr.php?RCID=44ec8d5267644605a846c960865b87e5 Download recording of Session #4]
|}
|}
{| style="width:95%" border="1" cellpadding="1"
{| style="width:95%" border="1" cellpadding="1"
Line 199: Line 101:
! Comments
! Comments
|-
|-
| 8:00-8:10
| 3:30pm-3:40pm
| Webinar Introduction, process
| Webinar Introduction, process
| Eric Heflin, Daniel Berezeanu : Co-Chairs
| Eric Heflin, Daniel Berezeanu : Co-Chairs
| Re-iterated message from prior call to focus on the problem, not the solution.
| Re-iterated message from prior call to focus on the problem, not the solution.
|-
|-
| 8:10-8:30
| 3:40pm-4:00pm
| [ftp://iheyr2@ftp.ihe.net/IT_Infrastructure/iheitiyr13-2015-2016/Planning_Cmte/BriefProfileProposals/IHE%20Proposal%20Brief%20-%20lwPAM.docx Lightweight Patient Administration Management]
| [ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr14-2016-2017/Planning_Cmte/BriefProfileProposals/IHE_ITI_Work_Item_Proposal_2015-09-17-Felhofer.docx Maintenance of Profiles Published in 2015 and earlier]
| Justin Fyfe
 
| Proposal has been withdrawnThis presentation did not occur as a result.
[ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr14-2016-2017/Planning_Cmte/BriefProfileProposals/ITI-BriefWorkItemProposal_TFmaintenance.pptx Presentation]
| Lynn Felhofer
| Q: What is the size of the CP work?  A: Will be available in Nov and is on Wiki's nowProbably a medium or large work item, but it depends on people doing the work and which CPs are selected for emphasis in the coming year if this proposal is selected. Q: Is this a heads up on normal governance or a specific ask?  A: Goal was to help the Planning Committee better determine capacity and specifically take maintenance into account when prioritizing Tech Cmte work in the coming year.
|-
|-
| 8:30-8:50
| 4:00pm-4:20pm
| [ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr13-2015-2016/Planning_Cmte/BriefProfileProposals/XDW%20with%20XCA-XCDR%20Detailed%20Proposal-v5.docx Extending the Use of XDW to Cross-Community Environments]  
| [ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr14-2016-2017/Planning_Cmte/BriefProfileProposals/IHE_Profile_Proposal_RESTful-DSUB.docx RESTful DSUB]
| Charles Parisot, David Pyke
| Rob Horn
| This proposal is to continue the evolution of XDWInternational impact is large.
| Q: What is the DSTU timeline? A: Probably DSTU3 will be several years out.  Q: Would this be a white paper or a profile?  A: We would decide together, but the editor is proposing a white paper this year, and then a profile next year.  Q: Why not wait for a few years when HL7 is done?  A: Need to accommodate for software development life cycles and lead time.  Q: Is DSUB used widely today? A: Hard to assess. Perhaps we could determine from IHE Product Registry. Q: Can we clarify the use case?  A: Yes.  Q: Why do mobile devices need a notification pattern?  A: "Tell me when this is ready." type of use casePerhaps contrast polling vs. push notifications.
|-
|-
| 8:50-9:10
| 4:20pm-4:40pm
| [ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr13-2015-2016/Planning_Cmte/BriefProfileProposals/IHE_Profile_Proposal-DSG-20140818.docx DSG Supplement Upate]  
| [ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr14-2016-2017/Planning_Cmte/BriefProfileProposals/IHE%20Brief%20ProposalBarcodeScanningPatientSafetyAndEfficiencyV1.docx Uniformal barcode processing for patient safety and efficiency] [ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr14-2016-2017/Planning_Cmte/BriefProfileProposals/Uniformal%20barcode%20processing%20for%20patient%20safety%20and%20efficiencyIHEWebinarOctober2015.pptx Presentation]
| John Moehrke
| Erik Zwarter, Vincent van Pelt
| Text is complete, pending feedbackWas originally a CP but it was turned into a proposal to provide better visibility and to solicit broader input than a CP would have generated.
| Q: What is the interoperability problem?  A: Each bar code used in the clinical care environment is different and not interoperableQ: In pharmacy a white paper has been done with a focus on the same problem.  How is this different?  A: Its not different except that the proposal is designed to work in any domain, not just pharmacy. Q: Determined it was not needed for pharmacy. What is the differentiating point? Q: Would you expect the data to be captured in a structured manner?  A: Acknowledged.  Will have to provide more information.  Q: Suggested coordination with Patient Care Devices domain and Pharmacy domain.  ITI may not have as much impact as it would if driven by Pharmacy.
|-
|-
| 9:10-9:30
| 4:40pm-4:50pm
| [ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr13-2015-2016/Planning_Cmte/BriefProfileProposals/IHE_Profile_Proposal-MHD-20140818.docx MHD and HL7 FHIR Harmonization ]  
| [ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr14-2016-2017/Planning_Cmte/BriefProfileProposals/IHE_Profile_Proposal_HPD-Updates-Brief-2015-10-19.docx HPD Updates/USA National Extension] [ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr14-2016-2017/Planning_Cmte/BriefProfileProposals/IHE_Profile_Proposal_HPD-Updates-Brief-Preso-2015-10-19.pptx Presentation]
| John Moehrke
 
| TBD
| Eric Heflin
| Q: Can this be broken into three proposals? A: Yes.  Q: Can the CP aspects be combined with Lynn's proposal? A: Will consider.  Seems like a good idea. Comment: USA national extension should not hold Final Text promotion.  Q: Can a use case be defined that better discerns the reason to implement a FHIR/RESTful approach? A: Will consider.
|-
|-
| 9:30-9:50
| 4:50pm-5:00pm
| [ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr13-2015-2016/Planning_Cmte/BriefProfileProposals/IHE_Profile_Proposal_Delete_Provide_&_Registered_Documentset.docx Delete Provide & Registered Document Set]
| Gil Levi, Bill Majurski
| This many have many policy considerations, but these are out of scope for now.  Proposal augments XDS with a needed delete functionality.  Large international impact.
|-
| 9:50-10:10
| [ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr13-2015-2016/Planning_Cmte/BriefProfileProposals/IHE%20ITI%20QDA%20Workitem%20Proposal%20V0_2.docx QDA - Query Dispatch and Aggregate]
| Vincent van Pelt
| The presenter was a no-show. As a result, the proposal was not reviewed on the webinar today. The co-chairs inquired if the proposal is being withdrawn and did not receive a response.
|-
| 10:10-10:20
| Discussion, Next Steps
| Discussion, Next Steps
| Co-Chairs
| Co-Chairs
|  
| Review agenda face-to-face meeting on Thursday 2015-10-22.
|}
|}
==Webinar 5==
Webinar #5 was not needed and has been canceled.  Please see above for the schedule for the remaining webinars.


==F2F Meeting==
==F2F Meeting==
The following agenda is a draft and may be adjusted based on needs of the meeting
The following agenda is a draft and may be adjusted based on needs of the meeting


==='''WEDNESDAY October 22 - DAY 1'''===
==='''Thursday October 22 2015 - In-person Meeting Day 1 (Decisional)'''===


NOTE: THIS AGENDA IS BEING REVISED AT THIS TIME (2014-10-20 12:44pm CST)
NOTE: THIS AGENDA WILL BE SUBJECT TO CONTINUOUS REVISION; IT WILL BE LIKELY REVISED UP TO AND DURING THE MEETING.
IT WILL BE LIKELY REVISED UP TO AND DURING THE MEETING


{| style="width:95%" border="1" cellpadding="1"
{| style="width:95%" border="1" cellpadding="1"
Line 255: Line 153:
:RSNA Headquarters
:RSNA Headquarters
:Oak Brook, IL  
:Oak Brook, IL  
| WEBEX INFO: [https://himss.webex.com/himss/j.php?MTID=m02682dad83a5ae315b40783c1cd3b7a8 Join webex]  
| [https://himss.webex.com/himss/j.php?MTID=m7c4f0df214ac333ff0de49ae2fdc006e Join webex] Meeting number: 928 183 704
Meeting Password: "Meeting1" (no quotes)


 
To receive a call back, provide your phone number when you join the meeting, or call the number below and enter the access code.
Meeting Password: Meeting
Call-in toll-free number (US/Canada): 1-866-469-3239
Call-in toll number (US/Canada): 1-650-429-3300
Access code:928 183 704
Global call-in numbers: https://himss.webex.com/himss/globalcallin.php?serviceType=MC&ED=403149227&tollFree=1
Toll-free dialing restrictions: http://www.webex.com/pdf/tollfree_restrictions.pdf


|}
|}
Line 267: Line 171:
! Minutes/Notes
! Minutes/Notes
|-
|-
|  8:30-8:45 CT
|  8:45-9:00 CT
| '''Welcome'''  
| '''Welcome'''
|
|
|
|
Line 279: Line 183:
:*Procedures, voting privileges, etc.
:*Procedures, voting privileges, etc.
:*Agenda review
:*Agenda review
|  
| Co-Chairs, Domain Sponsors
|
|
|-
|-
8:45-9:15 CT
9:00-9:45 CT
| '''ITI Capacity''' and '''Evaluation Criteria'''
| '''ITI Capacity''' and '''Evaluation Criteria'''
|
|
Line 293: Line 197:
:** [ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr11-2013-2014/Planning_Cmte/2012ITIProposalEvaluationMatrix_10.31final.xlsx 2012 Year Criteria Spreadsheet - final]
:** [ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr11-2013-2014/Planning_Cmte/2012ITIProposalEvaluationMatrix_10.31final.xlsx 2012 Year Criteria Spreadsheet - final]
:** [ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr12-2014-2015/Planning_Cmte/BriefProfileProposals/2013ITIProposalEvaluationMatrix_10.10_final.xlsx 2013 Year Criteria Spreadsheet - final]
:** [ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr12-2014-2015/Planning_Cmte/BriefProfileProposals/2013ITIProposalEvaluationMatrix_10.10_final.xlsx 2013 Year Criteria Spreadsheet - final]
:** [ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr13-2015-2016/Planning_Cmte/BriefProfileProposals/2014ITIProposalEvaluationMatrix_2.6-FINAL-TC-VOTE-Dispositions.xlsx 2014 Year Criteria Spreadsheet - final]
:*Process used to develop a prioritized work item list
:*Process used to develop a prioritized work item list
:** Ranking by Criteria
:** Ranking by Criteria
:*** [ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr13-2015-2016/Planning_Cmte/BriefProfileProposals/2014ITIProposalEvaluationMatrix_1.6.xlsx Initial spreadsheet]
:*** [ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr14-2016-2017/Planning_Cmte/BriefProfileProposals/2015ITIProposalEvaluationMatrix_1_1.xlsx Initial spreadsheet]
:** Ranking by Ballot
:** Ranking by Ballot
| ITI co-chairs
| ITI co-chairs
| Goal:Determine how many votes each organization will get.  Agree on approximate number of proposals to forward on to ITI TC. Evaluate each proposal at that time (while it is fresh).  Agree on physical voting logistics (google spreadsheet, flip chart, other.)
| Goal: Decide how many votes each organization will get.  Decide on approximate number of proposals to forward on to ITI TC. Evaluate each proposal at end of each presentation (while it is fresh).  Decide on physical voting logistics (google spreadsheet, flip chart, other.)
Outcome: Reviewed the process and agreed that each organization will get 7 electronic votes. Also agreed that the list of proposals would be limited and prioritized to approximately 5-10, depending on the size of the proposals.
Outcome: Decision: "Focus on value for today, not solution, size will only be a very rough estimate.  TC will determine size/effort. Each organization gets 51%+ of the number of proposals (5 points for 8 proposals, 7 proposals would result in 4 points).  Planning committee work items are in a different category. Items can be rejected due to wrong committee.  Items identified as "Must Do" will be excluded from the straw poll."
|-
|-
| 9:15-9:45 CT  
| 9:45-10:15 CT  
| '''Advocacy''' [ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr13-2015-2016/Planning_Cmte/BriefProfileProposals/SAMLHealthcareWorkflowsProposal.docx SAML for Healthcare Workflows Deployment]
| '''Advocacy''' [ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr14-2016-2017/Planning_Cmte/BriefProfileProposals/IHE%20Brief%20ProposalBarcodeScanningPatientSafetyAndEfficiencyV1.docx Uniformal barcode processing for patient safety and efficiency]
| Alex DeJong
| Esther Peelen, Vincent van Pelt, Tie Tjee, Erik Zwarter, Amanda deLaroque, Robert Breas
| [ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr13-2015-2016/Planning_Cmte/BriefProfileProposals/IHE_SAMLforHealthcareWorkflows.pdf presentation] Designed to allow two factor authentication using SAML for work-flows.  Required by some legal jurisdictions.  
| [ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr14-2016-2017/Planning_Cmte/BriefProfileProposals/ presentation link TBD]
Q: What is the interoperability problem? It is not apparent that there is a need. A: SAML is not constrained enough to be interoperabilityThey've identified about 30 factors that are not constrained enough. They took this to OASIS and they indicated that this level of constraints was for each industry to define. Constraint on the SAML Web SSO profile to enable government mandated authenticated methodQ: Where would it be of use?  A: USA, Canada, Europe. Initial ranking: 14 points.
Discussion: Determined need; Seems to be solved by a PIX managerSuggested that ITI address this use case to a PIX manager profile, and seems like the "content" side of this proposal is better suited to a domain like Pharmacy. Defined UDI as a globally unique ID, has a manufacturer tracing, FDA regulated, and is becoming an international identifier. Parsing is not a problemPharmacy domain has defined the workflow. Supply is cross domain. Proposal was to refer to Pharmacy, then Pharmacy will work as far as they can, and then will come back to ITI. Pharmacy has skill sets for this use case (bar coding). Wide variety of bar coding standards. Decision: This will be refereed to Pharmacy and removed from the ITI evaluation processJose will liaise with Pharmacy. ITI will keep this as a "parking lot" and ITI will re-assess this proposal for consideration if Pharmacy does NOT take this work item on this cycle.
|-
|-
| 9:45-10:00 CT  
| 10:15-10:45 CT  
| '''Advocacy''' [ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr13-2015-2016/Planning_Cmte/BriefProfileProposals/IHESAMLwithHContextProposal.docx Health Context Sharing via SAML]  
| '''Advocacy''' [ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr14-2016-2017/Planning_Cmte/BriefProfileProposals/IHE_ITI_Work_Item_Proposal_2015-09-17-Felhofer.docx Maintenance of Profiles Published in 2015 and earlier]
| Alex DeJong
| Lynn Felhofer
| [ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr13-2015-2016/Planning_Cmte/BriefProfileProposals/IHE_SAMLwithHContextProposal.pdf  presentation  ] Can be thought of as mapping CCOW to SAMLPresenter asserts CCOW is a valuable profile, but it is difficult to implement. Would allow applications to share a patient context via SAML in an interoperable wayComment was made that CCOW is dead. Would be a browser session based for some but not all information transfers.  
| [ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr14-2016-2017/Planning_Cmte/BriefProfileProposals/ITI-BriefWorkItemProposal_TFmaintenance.pptx Presentation] [ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr14-2016-2017/Planning_Cmte/BriefProfileProposals/WhoHasWhatCPs.xlsx WhoHasWhatCPs] Discussion: Suggestion was to assess CPs by value, effort, and urgency. Our current CP process is not making progressPerhaps have a "CP blitz" and dedicated time for CPs. Vendors are less willing to act on profiles if the profile is in Trial Implementation status.  And CPs are keeping DSUB, HPD, and others from moving to Final Text status. Concerted focus meetings (such as based on a specific profile) are productive. Discussed valueAssertion was made that lack of work last year equated to lack of value.  This issue is really that "are we going to add additional working sessions to work on CPs".  Do we separate FHIR CPs? Yes. What's the value of CP work?  1) Moving TIs to FT. 2) Perception issue (responsive). The CPs need to be broken out into categories so we can evaluate them better, such as value, effort, or other categories. Initial ranking: value 9/9, size large.
|-
|-
| 10:00-10:15 CT
| 10:50-11:05 CT
| '''Break'''  
| '''Break'''  
|
|
|
|
|-
|-
| 10:15-10:45 CT  
| 11:05-11:30 CT  
| '''Advocacy''' [ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr13-2015-2016/Planning_Cmte/BriefProfileProposals/IHE_Profile_Proposal_ATNAquery-Brief2014.docx ATNA Query]
| '''Advocacy''' [ftp://iheyr2@ftp.ihe.net/IT_Infrastructure/iheitiyr14-2016-2017/Planning_Cmte/BriefProfileProposals/IHE_Profile_Proposal_EnhancedPatientPrivacyConsents_v1.0.docx Enhanced Patient Privacy Consents]  
| Mauro Zanardini
| Tarik Idris, John Moehrke, Frank Oemig, Jörg Caumanns
| [ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr13-2015-2016/Planning_Cmte/BriefProfileProposals/ITI-Brief-ATNAQuery2014.ppt Presentation ] Policy an User driven requirements to have healthcare specific query mechanisms to ATNA.
| [ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr14-2016-2017/Planning_Cmte/BriefProfileProposals/ presentation TBD]  Discussion: Q: Who is the editor? A: Tarik. Q: What is the interoperability problem? A: Lack of a common vocabulary and common structure.  BPPC only works for pre-coordinated policies. Q: Whats the urgency?  A: The proposing team has identified an urgent need in current project(s). Multiple solutions are being deployed today that are not-interoperableProject would include a survey of existing solutions. This proposal would also a combinatorial explosion of per-coordinated policies. Q: Is this a conten profile? A: TBD by the Technical Committee. Q: Is this an overlap with the AHIMA governance implementable white paper.  A: Undecided. Several comments indicating the lack of this standard is impeding multiple live initiatives internationally (Illinois, Canada, Texas, NY, FL, more).  Q: Where is the enforcement point?  A: This proposed profile is independent of the enforcement engine. Effort includes survey of existing solutions/approaches, terminology confusion and definitions. Initial ranking: Value: 9/9 points. Size: Large.
|-
|-
| 10:45-11:15 CT
| 11:30-11:45 CT
| '''Advocacy''' [ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr13-2015-2016/Planning_Cmte/BriefProfileProposals/ITI_Restful_ATNA_Repository_access.docx ATNA Repository RESTful Access]
| '''Advocacy''' [ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr14-2016-2017/Planning_Cmte/BriefProfileProposals/IHE_Profile_Proposal_DocSharingProfilesRedoc-Breif-09-24.docx Re-documentation of Document Sharing Profiles]
| Rob Horn
| [ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr13-2015-2016/Planning_Cmte/BriefProfileProposals/ATNA-Repository-Access-brief.ppt Presentation ] Merging with ATNA Query
The 2 following proposals address similar use cases and will be joined together.
Have minimal healthcare content and leverage existing Syslog access standards to access ATNA logs. Permit audit logs forwarding from local audit repository to another more central audit repository, possibly based on filter rules.
 
|-
| 11:15-11:45 CT  
| '''Advocacy''' [ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr13-2015-2016/Planning_Cmte/BriefProfileProposals/XDN-BriefProposal-renamedFromVIAA.docx Cross-Enterprise Document Network Interchange (XDN)]
| Fred Behlen
| [ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr13-2015-2016/Planning_Cmte/BriefProfileProposals/XDN%202014%2010%2002.pptx Presentation ] Problem is moving a repository from one vendor to another.  Is an interoperability due to the amount of time to migrate due to insufficient speed. The current standards define an API, and vendors decide on how data is stored internally. It was asserted that this is not an interoperability issue and is a step backward to XDS.a which was similar. REST style indirection needed in XDS Registry .Security concerns in adding URI.  Proposer agrees to make this a white paper, with a small scope.
 
|-
| 11:45-11:55 CT
|'''Advocacy''' [ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr13-2015-2016/Planning_Cmte/BriefProfileProposals/IHE_Profile_Proposal_XDStarRedoc-Brief.docx Redocumentation of XD* Profiles]
| Karen Witting
| Karen Witting
| Resubmission of last year proposal.   
| [ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr14-2016-2017/Planning_Cmte/BriefProfileProposals/ Presentation TBD] Discussion: Document sharing is becoming a widely adopted profile for many different purposes.  This is resulting in many areas where the documentation is not optimal and it is not in-line with the IHE documentation approach. Q: Should ITI TC wait on this given that we are still working on last year's re-documentation work. Q: What's the value? Do we have evidence of confusion? A: The current problem is organization and lack of clarity.  Don't have evidence of the value. Q: Is there a way to measure the value provided by previous phases?  A: Need to gather informationQ: Can we break this into two groups, CPs and redoc work. Q: Yes. It can be phased/grouped. Comment, seems like too much work when combined with Lynn's CP suggestion, which is that this means 2015/2016 becomes mostly a "maintenance year" as opposed to new work. Important to keep the momentum. Initial ranking: Value: 5/9 points. Size: Medium.
 
|-
|-
| 11:55-12:00 CT
| 11:45-12:30 CT
| '''Advocacy''' DSG Supplement Update
| '''Advocacy''' [ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr14-2016-2017/Planning_Cmte/BriefProfileProposals/IHE_Profile_Proposal_RESTful-DSUB.docx RESTful DSUB]
| John M
| Rob Horn
| There is minimal work left to get this out for public comment.
| [ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr13-2015-2016/Planning_Cmte/BriefProfileProposals/ presentation TBD] Discussion: "mobile" is shorthand for a broad category of devices.  This is the proposed next step in IHE support for REST/mobile.  Proposer is comfortable making this a two-year work item. DSUB use cases will need to be revised as they doesn't all apply. Need to also need to survey of existing solutions such as web sockets, or other approaches. The TC will be asked to decide on this item being a whitepaper or a profile or both.  Q: Why do a white paper before a profile.  A: Need to validate the use cases, and the approach. FHIR has identified 5 mechanisms for the concept of a subscription, for example. REST is somewhat contrary to maintaining a state such as a subscription. For example, web sockets doesn't address devices that are turned off.  Comment: White paper is the right approach to ensure we get the use cases and requirements right. So this is a white paper proposal now as per the proposer.  Q: Is the timing right?  A: Yes, so we can do this in parallel with other industry work like FHIR. Also, this keeps the momentum up for RESTful work items. Q: Who would the white paper be used?  A: Feedback to FHIR and other groups. Comment: This is not really specific to DSUB; it's a notification / pub-sub concept. Initial ranking: Value: 5/9 points. Size: small.
 
|-
| 12:00-12:15
| '''Advocacy''' [ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr13-2015-2016/Planning_Cmte/BriefProfileProposals/IHE_Profile_Proposal_Cross-Community.docx Next steps in Cross Community]
| Karen Witting
| The presenter can only work on one of her two proposals. This is a Planning committee White paper which could include a webinar.
 
 
 
|-
|-
| 12:15-12:45 CT
| 12:30-13:15 CT
| '''Lunch Break'''
| '''Lunch Break'''
|
|
|
|
|-
|-
| 1:00-1:45 CT
| 13:30-14:00 CT
| '''Advocacy''' [ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr13-2015-2016/Planning_Cmte/BriefProfileProposals/ITI_QRPH_Family_Planning_DeIdentification_04.docx De-identification of healthcare data to central reporting authority]
| '''Advocacy''' [ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr14-2016-2017/Planning_Cmte/BriefProfileProposals/IHE_Work_Item_Proposal_2016_AHIMAImplementWhitePaper%20FINAL.docx HIT Standards for HIM Practices: Implementable White Paper Proposal]
| Johanna Goderre Jones
| Harry Rhodes, Anna Orlova, Diana Warner
| [ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr13-2015-2016/Planning_Cmte/BriefProfileProposals/20141022_FamilyPlanningIHE_DeIdent.pptx Presentation ]  ITI helping QPHR to produce the Profile, possible outcome include changes to the handbook as well as educational materials. This profile also has the potential de be an international template that can later be adapted by each region . ITI TC, could help write an addendum to the white paper, as an example implementation based on  Family Planning DeIdentification
| [ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr14-2016-2017/Planning_Cmte/BriefProfileProposals/ Presentation TBD] Discussion: Q: Please elaborate on the actual problem to be solved? A: A method to assess the completeness of the workflow.  Q: Would this apply internationally.  A: Authoring teams asserts "yes" but several comments were made stating that this is a USA-centric profile. Comment was made that this seems like a content profile. This appears to be a infinite number of documents being created. Comment made that this is out-of-scope of this committee. Q: Has this been compared to the DAF profile? A: DAF didn't address their needs.  Such as "what's inside the profile"? Q: What's the value?  A:  Need slide was discussed. Initial assessment: The ITI PC is still unclear on the request from the proposer team. We asked the proposers to clarify and re-present Friday morning.  We also stated we cannot evaluate the proposal at this time due to lack of understanding.  Not assessed at this time.
 
|-
|-
| 1:45-2:15 CT  
| 14:00-14:30 CT  
| '''Advocacy''' [ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr13-2015-2016/Planning_Cmte/BriefProfileProposals/AHIMA_Submission_to_IHE_ITI_HIT_Standards_for_IG_Final_2014-09-18.pdf HIT Standards for Information Governance White Paper]
| '''Advocacy''' [ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr14-2016-2017/Planning_Cmte/BriefProfileProposals/IHE_Profile_Proposal_HPD-Updates-Brief-2015-10-19.docx HPD Updates and USA National Extension Proposal]
| Diana Warner
| Eric Heflin
| [ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr13-2015-2016/Planning_Cmte/BriefProfileProposals/STDSforIGWhitePaper-10-10-14.pptx presentation]Q:Is this a marketing white paper on how to use and leverage IHE stantards? It’s not a marketing exercise; it’s more about documenting clinical principals policies, practices and operations policies from an interoperability perspective. This White paper is targeting people writing profiles.
| [ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr14-2016-2017/Planning_Cmte/BriefProfileProposals/IHE_Profile_Proposal_HPD-Updates-Brief-Preso-2015-10-22.pptx Presentation] RESTful provider directories have already been created without any interoperability (each effort is different and not based on standards).  Why can we not solve the problem with standard solutions? Directory solutions vendors work mostly with the Global Enterprises and do not have specific healthcare solutions. Q: Does this apply internationally? A: It is appears to apply internationally, but we do not know of any specific implementations at this time that are seeking a RESTful directory. About 1/3 of the Connectathon HPD registry entries appear to have an international (non US) focus. There is a concern that the RESTful API is so simple to implement that there might not be lots of value in creating an interoperable standard. Q: Could we create a Profile that refers to DAF, and then late promote this to international status? A: Yes (from the proposer).  Q: Can we 1) break out the CP work, 2) USA national extension, and 3) RESTful proposals.  A: Yes. It was suggested that the IHE USA be engaged to work on USA national extension (Proposer agreed).  It was also suggested that the CP aspect be removed and included in the other CP work (the Proposer agreed). And finally it was suggest that the RESTful version proposal be balloted (again the Proposer agreed).
Q:Is this a planning committee deliverable? TC is the audience for this, but PC delivers this.
ITI TC would have to review the White Paper. This White paper would have a large global international perspective.
 
|-
|-
2:15-2:30 CT
15:30-15:45 CT
| '''Break'''  
| '''Break'''  
|
|
|
|
|-
| 2:30-3:15 CT
| '''Advocacy''' [ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr13-2015-2016/Planning_Cmte/BriefProfileProposals/IHE_Profile_Proposal_Alerts-Brief.docx Proposal Alerts Targeted at Humans]
| Carl Leitner
| [ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr13-2015-2016/Planning_Cmte/BriefProfileProposals/IHE_Profile_Proposal_Alerts-Brief.pptx Presentation] Wide variety Clinical and public health use cases would be solved.
The complexity might be bigger than anticipated; we should diminish the scope by not doing the feedback options now. There is lots of interest in solving this, but sizing and slicing this problem will be challenging. Concerns that if we do not tackle the feedback mechanism, might loose clinical relevance. Design must be expandable.
From a need perspective this seems to have some overlap with PCD Alerts and Radiology Alerts, coordination will be required with other domains.
The feedback loop, which may be an option, could significantly increases the size equivalent to XDS.
|-
| 3:15-4:00 CT
| '''Advocacy''' [ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr13-2015-2016/Planning_Cmte/BriefProfileProposals/XDW%20with%20XCA-XCDR%20Detailed%20Proposal-v5.docx Extending the Use of XDW to Cross-Community Environments]
| Charles Parisot, David Pyke
| Radiology Workflow will cross borders; Radiology committee will give clear requirements
1 Profile and 1 supplement will be generated from this work
Dependency to moving XDW to final text while it supports single and multiple communities.
Other domains expect XDW to work in XCA.
|-
|-
| 3:45-4:15 CT
| 15:45-16:15 CT  
| '''Advocacy''' [ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr13-2015-2016/Planning_Cmte/BriefProfileProposals/IHE_Profile_Proposal_Delete_Provide_&_Registered_Documentset.docx Delete Provide & Registered Document Set]
| Gil Levi, Bill Majurski
| [ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr13-2015-2016/Planning_Cmte/BriefProfileProposals/Repository%20Document%20Deletion%20Proposed%20Work%20Item%20Presentation%20(2).pptx presentation] Delete is going to interact with medical records policies; requests for deletion need extensive policy and administration workflow. Data is generally not deleted in the US before the legal retention period.
Could Access control solve the temporary delete problem, and the offline storage for the long-term storage?
IOCM, requires a managed process to propagate changes.
Q: What is the use case driving this? To complete the document lifecycle. There is interest in using this to enforce legal retention period. This effort would demonstrate the completeness of the solution mostly for political reasons.
If the repository is the Archive of records, there is little need to delete. Acknowledgement can be Synchronous or asynchronous.
Q: Would there be a way to delete in multiple repositories? Yes, but the registry would have to inform the delete source of the existence and placement of all documents.
 
 
|-
| 4:15-4:30 CT
| [ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr13-2015-2016/Planning_Cmte/BriefProfileProposals/IHE_Profile_Proposal-MHD-20140818.docx MHD and HL7 FHIR Harmonization ]
| John M
| This is clearly understood by the workgroup, the presentation was skipped and we proceed directly to the evaluation. The Hackathon, should provide some feedback for incorporation. MHD will have to provide HL7 FHIR DSTU-1 response for January 2015. MHD will also have to incorporate HL7 FHIR DSTU-2 quickly .
 
|-
| 4:30-4:35 CT
| National Extensions for Confidentiality
| Rob H
| Withdrawn due to lack of interest yet. More interest is anticipated in the future.
 
 
|-
|  4:35-4:35 CT
| '''Advocacy''' [ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr13-2015-2016/Planning_Cmte/BriefProfileProposals/IHE%20ITI%20QDA%20Workitem%20Proposal%20V0_2.docx QDA - Query Dispatch and Aggregate]
| Vincent van Pelt
| No show.
 
|-
| 4:35-4:50 CT
| Restful PIX
| Rob H
| PDQm already supports RESTful PIX, only minimal profiling will be required.
Q: Will the consumer have the patient ID? Yes.
The PIX manager will not require a RESTful interface to register patients; they can keep using HL7V2 or V3.
 
 
 
|-
|  5:15-6:00 CT
| '''General Discussion and preparation for evaluation'''     
| '''General Discussion and preparation for evaluation'''     
| ITI Planning co-chairs
| ITI Planning co-chairs
|Voting procedures:
| Review of initial assessment. Discussion about which on-going work items will be sent to ITI TC. Discussion about combining proposals, reminders / decision about voting procedures, capacity reminder for ITI, and review of tomorrow's agenda (process used to develop a prioritized work item list). Some items may be work items for the ITI Planning Committee. The evaluation matrix as determined by the the ITI PC has been posted at ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr14-2016-2017/Planning_Cmte/BriefProfileProposals/2015ITIProposalEvaluationMatrix_1_6.xlsx
3 ongoing items will be passed on to ITI TC.
The group will vote to add 5 more profiles.
ITI TC will have to evaluate in more details the size of the proposals and could decide to take-on a subset of what is proposed to them.
 
Action items tomorrow:
Give Karen guidance on witch items we would like her to do.
We’ll vote before we give guidance.
 
We are ADJURNING the meeting.
 
|-
|-
|
| 16:15-17:30 CT
|
| '''Educational Activities'''   
:*Continued discussion for work items not fully understood
| ITI Planning co-chairs
:*Re-review of Evaluation Criteria
| Review of current gaps in the IHE ITI educational materials. Decide on items the ITI PC will work on this cycle in terms of webinars, presentations, and other educational materials.  Note that it may be time for a refresh of all educational materials at this point, plus new materials for updated work from the last two cycles in particular.  Current educational materials from ITI PC can be found here: http://wiki.ihe.net/index.php?title=Current_Published_ITI_Educational_Materials. Discussion: Security materials are current except for IUA, and IUA is premature due to rapid change.  Could add RESTful ATNA. Consider adding DEN. Suggested creating a "mobile" webinar (John M).  DSUB has a lot of updates, and the PPT at least needs to be updated (Mauro). XDR/XDR: Update the deck to include national uses and other updates (Charles).  XCDR and XCW over XCA: Needs a new deck and webinar (Charles). Patient ID mgmt: Needs updated slides. (Eric will updated slides and/or webinar to point Mobile Package).  Eric will see if HPD is current and then propose updates if need.  CSD is still current, no updates needed. XDW materials need updating (i/o documents, folders, etc.) (Mauro).  Plus new profiles for last year (RESTful ATNA (Rob), MACM (Carl L), PIXm (Daniel), MHD2 (John M), DSG (John M), National Extensions (done by local deployment domains)) Re-record all webinars that have been lost).  Need cross link webinars, put on Vimeo, YouTube, Slide Share, etc. Link from IHE.net educational materials.  Metadata update (Manuel M/Bill M).  We will also update the Wiki descriptions of profiles.
:*Conclude Process used to develop a prioritized work item list
|
|
|-
|-
| 6:00 pm CT
| 17:30 pm CT
| '''ADJOURN'''
| '''ADJOURN'''
|
|
Line 470: Line 273:
|}
|}


==='''THURSDAY October 23 - DAY 2'''===
==='''Friday October 23, 2015 - In-person Meeting Day 2 (Decisional)'''===
 
NOTE: THIS AGENDA WILL BE SUBJECT TO CONTINUOUS REVISION; IT WILL BE LIKELY REVISED UP TO AND DURING THE MEETING. As of 2015-10-19 it is incomplete for all items after the ballot.  We will try to wrap up the meeting by 3pm or earlier to accommodate travel schedules.
 
{| style="width:95%" border="1" cellpadding="1"
! Location
! Webex/Tcon
|-
|
:RSNA Headquarters
:Oak Brook, IL
| [https://himss.webex.com/himss/j.php?MTID=m02f5194c9c6d9bf4d21f716bde1871b4 Join webex] Meeting number: 928 522 664
Meeting Password: "Meeting1" (no quotes)
 
To receive a call back, provide your phone number when you join the meeting, or call the number below and enter the access code.
Call-in toll-free number (US/Canada): 1-866-469-3239
Call-in toll number (US/Canada): 1-650-429-3300
Access code:928 522 664
Global call-in numbers: https://himss.webex.com/himss/globalcallin.php?serviceType=MC&ED=402487097&tollFree=1
Toll-free dialing restrictions: http://www.webex.com/pdf/tollfree_restrictions.pdf
|}
{| style="width:95%" border="1" cellpadding="1"
{| style="width:95%" border="1" cellpadding="1"
! Time
! Time
Line 480: Line 304:
| '''Welcome, review of the day's plan'''     
| '''Welcome, review of the day's plan'''     
|
|
| WEBEX INFO(Password is Meeting): [https://himss.webex.com/himss/j.php?MTID=m02682dad83a5ae315b40783c1cd3b7a8 Join WebEx]
| Re-consider proposal from AHIMA, review evaluation spreadsheet, fill out "must do" column, ITI TC capacity (Gila), determine final list of proposals being considered, ballot, consider liaison, outreach, and other activities.
|-
|-
| 8:45-9:30 CT
| 8:45-9:00 CT
| '''Advocacy''' [ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr13-2015-2016/Planning_Cmte/BriefProfileProposals/IHE%20ITI%20QDA%20Workitem%20Proposal%20V0_3.docx QDA - Query Dispatch and Aggregate]
| Review proposals needing clarification
| Vincent van Pelt
| [ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr13-2015-2016/Planning_Cmte/BriefProfileProposals/QDA%20Proposal%20V0_9d.pptx Presentation ] QDA is inline with the ODD philosophy, what QDS adds seems to be more in relation to internal processing; normally IHE does not focus on internal processing but in interoperability.
Q: Does QDA display any actor interaction? Some interactions with Registry.
ODD, supports the snapshots of On Demand Documents using static documents.
Part of what QDA is proposing is supported by On Demand Documents.
QDA illustrates more a systems design/design pattern than system interoperability.
Is there something missing, or are you looking for
Q: What is your request for IT? Can the current profiles support the QDA workflow?
This sounds like requirements for a workbook/whitepaper.
ITI does not support non-patient specific documents such as templates.
Multiple of the existing profiles are/can be used for QDA.
Q: Does XCF support this workflow? No, XCF only exposes 1 query, and is not as complete as QDA.
XCF is designed to aggregate documents, the interfaces presented by XCF or ODD or RID could be used. Additional educational materials could be beneficial.
 
|-
|  9:30-10:15 CT
| Data Access Framework Document Access Implementation Guide
| Dragon
| [ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr13-2015-2016/Planning_Cmte/BriefProfileProposals presentation] The technical gaps are in the population and smtp? Yes, but right now, we are trying to build an implementation guide, not solve the gaps.
An existing White Paper Health Information Exchange: Enabling Document Sharing Using IHE Profiles serve as an example or base for improvement to meet guide requirements.
Data locked in EMR’s and this is a mean to enable the sharing if this data.
This is urgent for the US, but none of the other nations have expressed interest.
Q: QRPH domain has a proposal to allow breach clinical data that is in HIE for research, could there be a binding to that proposal? The MPQ aspect could be merged.
ONC FAD initiative will provide resources to work on this work item.
Is this a national extension? No, XDS based HIE would apply globally.
 
|-
| 10:15-10:30 CT
| '''Break''' 
|
|
|
| AHIMA paper (Harry, Anna, Diana).  Revised proposal were presented. Comment: Q: Option 3 seems similar to a security review, but with a focus on governance. Is that correct? A: Yes. Comment is that there is already an existing IHE governance document called "Template for XDS Affinity Domain Deployment Planning" that probably could use some updates.  Suggestion is to update this document. Q: Is the Proposal team receptive to this idea?  A: Yes, they will research this. http://www.ihe.net/Technical_Framework/upload/IHE_ITI_White_Paper_XDS_Affinity_Domain_Template_TI_2008-12-02.pdf.  Q: For the ITI PC, should this be an ITI TC or an ITI PC work item?  A: ITI TC was identified as the right work group.  Q: Will the proposal team consider recasting their work as being updates to the XDS Planning Document?  A: Yes. The must do column will not be used.
|-
|-
| 10:30-12:30 CT
| 9:00-10:15 CT
| '''Discussion and Voting on prioritized work item list'''   
| '''Discussion and Voting on prioritized work item list'''   
|
| Last year they published 13 points. Real capacity should be more like 10 points. One large, and a few smalls or a small and a medium is a reasonable capacity.  This year the work seems slightly too large.  TC still is seeking guidance on priorities.  Will likely have to cut.  Each organization casting 4 "points" for this prioritization exercise. Each organization will cast 4 ballots.  Use version 1.7 of the evaluation matrix: ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr14-2016-2017/Planning_Cmte/BriefProfileProposals/2015ITIProposalEvaluationMatrix_1_7.xlsx.  The 4 points will be tallied and sorted.  Then this will be discussed, force ranked, and voted for the formal ballot.  The result will be passed to the ITI TC for their assessment.
|Vote for Profiles Here: http://doodle.com/ta79mmrw36hmeufp
| Vote for Profiles: Contact Nancy R to vote if you are remote.  If you are in the room, please vote on the white board.  Results are posted here. ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr14-2016-2017/Planning_Cmte/BriefProfileProposals/2015ITIProposalEvaluationMatrix_1_8.xlsx.  In summary, Proposal #1 received 14 points.  Proposal #2 received 11 points. Proposal #3 received 4 points.  Proposal #4 received 9 points.  Proposal #5 received 5 points.  Proposal #6 received 5 points.  Proposal #7 was not subject to this prioritization process.  Proposal #8 received 0 points.  Note that proposal #8 was subject to discussion where it was proposed that the work proceed under IHE USA and with periodic communications to IHE International ITI TC and ITI PC.  Column U, called "Prioritization Point Count" in the evaluation matrix was renamed and reflects the total of the points received for the prioritization exercise. Next this will be discussed, the final rank will recorded in column V "Ballot based ranking". The detailed proposals November 3rd, 2015. Please send them to the ITI Co-Chars.  Please let the ITI TC Co-Chairs know if this date is a problem. A motion has been made to accept the prioritization in column V of the evaluation matrix to be passed to ITI TC. ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr14-2016-2017/Planning_Cmte/BriefProfileProposals/2015ITIProposalEvaluationMatrix_1_10.xlsx.  Motion carries.
|-
|-
|
|
|
|
|
:* Complete Ranking by Criteria spreadsheet and review results
:* Complete Ranking by Criteria spreadsheet and review results
:* Review last year's actual velocity (capacity)
:* Review last year's actual velocity (capacity)
:* Agree on voting approach - # of ballots per organization
:* Review voting procedures - # of ballots per organization
:* Ranking by Ballot - Voting
:* Ranking by Ballot - Voting
:* Ballot
:* Ballot
| Each organization will get 4 votes.  Results will be tallied in the eval spreadsheet. Link
|
[ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr13-2015-2016/Planning_Cmte/BriefProfileProposals/2014ITIProposalEvaluationMatrix_2.6-FINAL-TC-VOTE-Dispositions.xlsx Final Planning Committee Vote for TC Work]
| Each organization will get # votes.  Results will be tallied in the eval spreadsheet. Link
[ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr14-2016-2017/Planning_Cmte/BriefProfileProposals/ Final Planning Committee Vote for TC Work] It was suggested and agreed that the redocumentation work be a plan be presented instead of a new detailed proposal.  For the governance paper, it would be useful to have a scope statement with a list of key milestones. SMART methodology was suggested.  Also, an ITI TC Co-Chair was approached by a QRPHR Co-Chair with an additional request for a specific work item, for a some type of information profiling metadata for non-patient specific file registry / repository.  Clinical Trials has a similar use. This will be refereed to the ITI TC as well, in a manner similar to the USA National Extension.
|-
|-
| 12:15-1:00 CT
| 10:15-10:30 CT
| '''LUNCH'''
| '''Break'''
|
|
|
|-
| 10:30-11:30 CT
| Next steps for the proposals, Wiki Descriptions, Suggestions for improvement for next year (impact assessment process), Brainstorming on ITI PC whitepaper for this cycle, ITI Outreach and liaison activity
| All
| Lessons learned: Don't change voting procedures on the fly (from chat, to email, verbal, etc.).  Clarify process for national extensions is approved with respect to the planning committee. Agenda wasn't published in advanced and was too flexible.  Webex didn't start when the meeting was scheduled. Define terms in the eval spreadsheet. Write down the tally process!
Tally went OK, vote was OK. Should votes be public or semi-anonymous? Webex didn't work well.
Why did we receive so many proposals this year?  Do we need to publicize the work more to get more proposals?  We should perform a strategic planning exercise to identify multi-year directions and opportunities.  Contract profiles previously rejected to see if the need is still there?  Publish schedule longer in advance. Actively recruit members for ITI TC and PC both.
|-
| 11:30-12:30 CT
| '''IHE International Board Report'''
| Karen Witting (IHE ITI Board Liaison)
|
|
|-
|-
| 1:00-2:00 CT
| 12:15-13:00 CT
| '''Decision of Prioritized List of proposals'''
| '''LUNCH'''
|
|
|
|
|-
|-
|
| 13:00-14:00
|
|
|
:*Review voting results
:*Review voting results
:*Agree on prioritized list of proposals to be assessed by ITI Technical Committee
:*Agree on prioritized list of proposals to be assessed by ITI Technical Committee
:*Assignment of authors, due-dates, etc. for completion of Detailed Proposal ''(Nov 5th)'' for turn-over to TC in November
:*Assignment of authors, due-dates, etc. for completion of Detailed Proposal ''(Nov #)'' for turn-over to TC in November
|
|  
|  
*Proposals forwarded to ITI TC - due date for detailed Proposals Nov. 5th, 2014 at 11:59:59pm Central Time:
*Proposals forwarded to ITI TC - due date for detailed Proposals Nov. 4th, 2015 at 11:59:59pm Central Time:
** 15.0 ATNA Repository RESTful Access/ATNA Query
[ftp://iheyr2@ftp.ihe.net/Document_templates/IHE_Profile_Proposal_Template-Detailed.docx | link to template]
** 3.0 Redocumentation of XD(star) Profiles
** 8.0 De-identification of healthcare data to central reporting authority
** 9.0 Alerts Targeted at Humans
** 11.0 RESTful PIX
*Discussed proposals not forwarded to ITI TC and plans for ITI Planning followup tasks:
*Discussed proposals not forwarded to ITI TC and plans for ITI Planning followup tasks:
** 16.0 Health Context Sharing via SAML
** 13.0 Delete Provide & Registered Document Set
** 6.0 SAML for Healthcare Workflows Deployment Profile
** 12.0 Data Access Framework Document Access Implementation Guide
** 18.0 QDA - Query Dispatch and Aggregate
*Proposals accepted as ITI PC work
*Proposals accepted as ITI PC work
** 1.0 HIT Standards for Information Governance White Paper
** 2.0 Next steps in Cross Community (mutually exclusive with item 3.0)
*Work from prior years that are forwarded to ITI TC
*Work from prior years that are forwarded to ITI TC
** 5.0 Mobile access to Health Documents (MHD)
** 4.0 Document Digital Signature
** 19.0 Extending the Use of XDW to Cross-Community Environments
|-
|-
|  
| 14:15-14:30 pm CT
| Suggestions for improvement for next year
:*impact assessment process
|
|
Review of the process/suggestions for improvements
*Voting:
Doodle pool: good for enabling remote voting, and bad for anonymity.
Need a new electronic tool. Google Forms is blocked for some organizations.
Try another electronic voting mechanism that could anonymous, a survey tool was considered a viable option.
*Methodology:
We used a mixture of Agile and waterfall.
*Use of Story points:
We should use Agile tools to determine relative importance, but not size. The Planning Committee should provide a prioritized list not a cut off. The TC will have to do a deep dive in each proposal and this is too big of a task in the provided time, for that reason PC should provide a cutoff list.
Q: How do we engage everyone? Use via planning poker (silent cards) and use the outliners to spark the discussion.
*Process:
The notification process was late (or too early). The process was unclear.
Consolidation of the process with the other committees could be interesting.
The gathering of the proposals could be a better more organized process.
The schedule was hard to find on the wiki.
The proposals should be more problem focused (not solution).
We should mentor the proposal authors during the WebEx.
 
 
|-
| 2:00-2:30 pm CT
| '''Current Planning Committee proposals for the current cycle'''   
|
|*HIT Standards for Information Governance White Paper
*Next steps in Cross Community
|-
| 2:30-2:45 pm CT
| '''Current Planning Committee proposals for the current cycle'''   
|
|*HIT Standards for Information Governance White Paper
|-
| 2:15-2:30 pm CT
| '''Marketing and publicity planning'''     
| '''Marketing and publicity planning'''     
|
|
|-
|
|
|
:*[[ITI_Educational_Material | Educational presentation content and webinars]]
:*[[ITI_Educational_Material | Educational presentation content and webinars]]
Line 619: Line 372:
::*Assess status and work to be done
::*Assess status and work to be done
:*Discuss suggestions for other opportunities for communicating about ITI work
:*Discuss suggestions for other opportunities for communicating about ITI work
|
:*Review of wiki profile descriptions:
*Review of wiki profile descriptions:
:*Educational materials
**TBD
|Wiki details profiles:
*Educational materials
Patient Location Tracking  detailed description by Ben
** XDW continuation: Complete work begun in prior year - Mauro
Patient Identifier Cross-Reference for Mobile (PIXm) Daniel Berezeanu
** consent management statewide in texas - Eric
Mobile Alert Communication Management(mACM) Check with Karl
** XDS Metadata Update supplement educational Materials - Manuel to start April 2014
Secure Retrieve [SeR] Maurau
** On-demand Educational materials related to XDS & XCA - Karen
XCDR David Pyke
** Enhance introductory charts to include an overview to the other chart decks - Mike
 
** CSD educational material - Carl
Review and update Handbooks and White papers on the wiki
** Update S&P Part 1 to reflect XUA++ and IUA - John
 
|Potential Additions to be considered for this year
 
*XAD-PID in either XDS or the patient id one
Profile spotlight will probably remain and will be leveraged for marketing
*Mobile/REST specific materials
 
|-
Deprecation of Ccow [PSA] Patient Synchronized Application for the May F2F meeting
| 3:30-3:45 CT
 
| '''Consider suggestions for future ITI Planning Committee work''' 
Email Mary with the [ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr14-2016-2017/Planning_Cmte/Meetings/OctoberMeeting/Technical_Frameworks_CORRECTIONS.docx | Website changes]
|
 
|
Joint TC-PC meeting at 2pm Friday November 13
Educational work should get scheduled by Daniel and Eric offline with the presentors
Plan the re-recording of webinars should be scheduled by Daniel and Eric
 
 
|-
|-
|
| 2:30 - 3:00 pm CT
|
:*White Papers
:**Existing
**TBD
:**Consider suggestions for new white papers
**TBD
:*ITI Outreach and liason activity
::*Assess status and planning
|
*White Papers
**TBD
*Strategy areas
**TBD
|
|-
| 3:45 - 4:00 pm CT
| '''Wrap-up'''     
| '''Wrap-up'''     
|  
|  
|
|
|-
|-
|
| 3:00 pm CT
|
:*Schedule followup tcons
::*Assess Trial Implementation profiles movement to Final Text
::*Educational presentations and webinars
::*White Paper Updates
::*Other
|
*tcons schedule for HIE Outreach, XDW Educational Material, on-demand educational material, CSD educational material.
*joint tcon for response from ITI TC
*deferred scheduling joint tcon to assess TI move to FT, plan to schedule during May f2f
*other tcons to be scheduled as needed
|
|-
| 4:00 pm CT
| '''ADJOURN'''
| '''ADJOURN'''
|
|
Line 681: Line 408:




==='''THURSDAY November 13'''===
==='''November 13, 2015 - In-person Joint ITI PC/TC Meeting (Decisional)'''===
 
 
{| style="width:95%" border="1" cellpadding="1"
{| style="width:95%" border="1" cellpadding="1"
! Time
! Location
! Description
! Webex/Tcon
! Presenter
! Minutes/Notes
|-
|-
| 1:30-2:30 CT
|  
| '''Welcome, review of the joint TC/PC committee meeting'''   
:RSNA Headquarters
|
:Oak Brook, IL
| WEBEX INFO(Password is Meeting): [https://himss.webex.com/himss/j.php?MTID=mba6a9ce3a7ea4cca91f198e646d3b985 Join WebEx]
| See the ITI TC meeting invitation for the Web meeting details
Agenda:
 
:* IHE ITI Technical Committee presentation of assessment of work items
Joint ITI PC and TC decisional meeting at 11:30-12:30 Meeting notes may be found at: ftp://ftp.ihe.net//IT_Infrastructure/iheitiyr14-2016-2017/Planning_Cmte/Meetings/NovemberMeeting/The%20final%20ITI%20PC%202015%20decisions%20v2.docx%22
:** Technical Committee meeting notes are posted at [ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr13-2015-2016/Technical_Cmte/Detailed-Proposals/IHE_ITI_NovemberF2F_MeetingNotes-PCCQPRHITI_Joint.docx Meeting notes]
:** Are there any changes to the scope?  Size?
:** Are there any asks of the TC to the PC such as additional clarity on priorities?
:** Does the ITI TC feel it can do all of the work scheduled for this cycle?  Do you need more work? Less?
:** The two national extension work items seem to merit special discussion (size, process)?
:** What are the proposed timelines for each work item?
:* Discussion
:** Referencing [ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr13-2015-2016/Technical_Cmte/Detailed-Proposals/2014_TechnicalCommittee_prioritization_review_v01.xls ITI TC Assessment Spreadsheet]
:** Please explain the work item size changes for the first few items?
:** Confirm that the rest of the item's priorities are the same?
:** Please explain the TC assessment spreadsheet columns E, and the hours columns O to R and why they are blank for the two national extension items?
:** Is there anything the ITI Planning Committee can do to help the ITI TC?
:* Formal motion to accept the ITI TC workplan
:** A verbal vote occurred and the ITI TC workplan was accepted
:* Note that since Karen is the lead editor of XD*, she will NOT be available for the ITI PC work item Next Steps in Cross Community and ITI PC should consider that work item proposal withdrawn.
|}
|}
= ITI Planning/Technical Committee 2015 Final Text Review - May 30 2015 =
Joint ITI Planning/Technical Provisional Selection for Final Text
== Agenda May 30, 2015 ==
# Profiles to [[Final Text Process| consider for Final Text]]
## (XPID) XAD-PID Change Management
## (CSD) Care Services Discovery
## (XCF) Cross Community Fetch
## (XDW) Cross Enterprise Workflow
## (DEN) Document Encryption
## (DSG) Document Digital Signature
## (HPD) Healthcare Provider Directory
## (MHD) Mobile access to Health Documents
## (IUA) Internet User Authorization
## (PLT) Patient Location Tracking
## (SeR) Secure Retrieve
## (PDQm) Patient Demographics Query for Mobile
## (DSUB) Document Metadata Subscription
## Delayed Document Assembly  (option)
## Metadata update (options)
## XCDR
## XDW for XCA and XCDR (options)
## XCPD Health Data Locator and Revoke (Option)
# [http://wiki.ihe.net/index.php?title=File:2014-15-ITI-TI-supplement-connecthon-summary.xlsx  Summary of connectathon testing & tool status for 2014-15 ITI TI profiles]
# profiles to [[Evaluation of Published Profiles| consider for deprecation]] : None Proposed
# white papers to consider for archival: None Proposed

Latest revision as of 00:11, 12 December 2015

Introduction

This WIKI page documents the activities of the ITI Planning Committee during the 2015/2016 committee year (August 2015 - July 2016). These activities include:

  • Call for Proposals : August-October
  • Review and selection of Proposals : October-December
  • Updates/Additions to Educational Materials/White Papers/Etc. : December-July

Proposal Webinars

Webinar Organization

Each webinar will be organized as follows (this will vary slightly depending upon how many proposals we will be reviewing:

  • Each webinar will be divided into 20-minute time-slots, with the remaining time for introductory remarks and follow-up discussion.
  • Each 20-minute time slot will be allocated to a profile/white paper proposal… the first 10 minutes will be taken up by a presentation by the proposal author, with the remaining 10 minutes reserved for discussion and any disposition (if required).
  • Each 10-minute presentation will be comprised of a maximum of 5 Powerpoint slides, presenting the proposal problem statement concisely and completely.

Webinar 1

Webinar #1 was not needed and has been canceled. Please see below for the schedule for the remaining webinars.

Webinar 2

Webinar #2 was not needed and has been canceled. Please see below for the schedule for the remaining webinars.

Webinar 3

All times are Central Time

Date Time Coordinates Recording of the meeting
2015-Oct-15 12:00pm-2:00pm CDT Join Webex(password "meeting") Download recording of Session #3
Time Proposal Author/Presenter Comments
12:00pm-12:10pm Webinar Introduction, process Daniel Berezeanu, Eric Heflin : Co-Chairs The goal for this series of webinars is to just explain and socialize the problem. The goals is NOT for the presenter to talk about the solution. And the goals is NOT for the ITI PC to prioritize or select which brief proposals move forward. Presenters should be prepared to present their brief proposal papers, or a power point with the same basic concepts. All webinars will be recorded and publicly posted. All ITI PC members are expected to review the webinars (live or via the recordings) prior to the F2F meetings.
12:10pm-12:30pm Enhanced Patient Privacy Consents Tarik Idris, John Moehrke, Frank Oemig, Jörg Caumanns 1-Facility specific consent

2-Consent for an episode of care 3-Provider blacklist, document author/source, document metadata, roles, Xid

There seems to be some overlap with existing standards. A full standards assessment will be required once the profile work begins.

Use of stylesheets, what will be the source of the policy statements, how are you planning to address specific policies. There could be many different sources of policies, but there are different approaches that could be applied including a central approach We are looking to create a portion in consent within probably PBBC, which they can use the meaning behind the modifications to core consent. Will this be applied to nation, state legislations within a determined structure? We can certainly within IHE have specific reach outs but normal public comment mechanism should be minimally acceptable.

12:30pm-12:50pm Re-documentation of Document Sharing Profiles Karen Witting What is the positive impact of this work on IHE?

Phase 1 most important, phase 2 more focused, the impact would be about the same as phase 2 and will provide significant impact with minimal work effort. The clarification and re-documentation of the existing standards provides ease of use and implementation without changes to any conformance criteria. How was the decision on what order the profiles to re-document? The work group decided to cover the provide, register and retrieve transactions and would be complete and the Query transaction in a later phase.

12:50pm-1:10pm HIT Standards for HIM Practices: Implementable White Paper Proposal Harry Rhodes, Anna Orlova, Diana Warner Can this effort be internationalized? Yes, we are already working internationally with collaborators.

Impact, original WP received 149 comments external to ITI, HIM vendors and implementers are showing much interest in the work IHE is doing.

1:10pm-1:20pm Discussion, Next Steps Co-Chairs Next steps: 1) more Brief Proposal webinars scheduled (please see below on this page for the details), 2) you should listen to all webinars prior to the October face-to-face meetings, 3) in Oct f2f meetings the ITI Planning Committee we will dive into these more deeply and assess against criteria in the spreadsheet (fit, value, effort, etc.), 4) vote on which move forward to ITI TC for their assessment. Also a reminder: All presenters should send their presentations so they can be posted on the public ftp site.

Webinar 4

All times are Central Time. This call will be recorded and publicly posted.

Date Time Coordinates Recording of the meeting
2015-Oct-19 3:30pm-5:30pm CDT Join Webex(password "meeting") Download recording of Session #4
Time Proposal Author/Presenter Comments
3:30pm-3:40pm Webinar Introduction, process Eric Heflin, Daniel Berezeanu : Co-Chairs Re-iterated message from prior call to focus on the problem, not the solution.
3:40pm-4:00pm Maintenance of Profiles Published in 2015 and earlier

Presentation

Lynn Felhofer Q: What is the size of the CP work? A: Will be available in Nov and is on Wiki's now. Probably a medium or large work item, but it depends on people doing the work and which CPs are selected for emphasis in the coming year if this proposal is selected. Q: Is this a heads up on normal governance or a specific ask? A: Goal was to help the Planning Committee better determine capacity and specifically take maintenance into account when prioritizing Tech Cmte work in the coming year.
4:00pm-4:20pm RESTful DSUB Rob Horn Q: What is the DSTU timeline? A: Probably DSTU3 will be several years out. Q: Would this be a white paper or a profile? A: We would decide together, but the editor is proposing a white paper this year, and then a profile next year. Q: Why not wait for a few years when HL7 is done? A: Need to accommodate for software development life cycles and lead time. Q: Is DSUB used widely today? A: Hard to assess. Perhaps we could determine from IHE Product Registry. Q: Can we clarify the use case? A: Yes. Q: Why do mobile devices need a notification pattern? A: "Tell me when this is ready." type of use case. Perhaps contrast polling vs. push notifications.
4:20pm-4:40pm Uniformal barcode processing for patient safety and efficiency Presentation Erik Zwarter, Vincent van Pelt Q: What is the interoperability problem? A: Each bar code used in the clinical care environment is different and not interoperable. Q: In pharmacy a white paper has been done with a focus on the same problem. How is this different? A: Its not different except that the proposal is designed to work in any domain, not just pharmacy. Q: Determined it was not needed for pharmacy. What is the differentiating point? Q: Would you expect the data to be captured in a structured manner? A: Acknowledged. Will have to provide more information. Q: Suggested coordination with Patient Care Devices domain and Pharmacy domain. ITI may not have as much impact as it would if driven by Pharmacy.
4:40pm-4:50pm HPD Updates/USA National Extension Presentation Eric Heflin Q: Can this be broken into three proposals? A: Yes. Q: Can the CP aspects be combined with Lynn's proposal? A: Will consider. Seems like a good idea. Comment: USA national extension should not hold Final Text promotion. Q: Can a use case be defined that better discerns the reason to implement a FHIR/RESTful approach? A: Will consider.
4:50pm-5:00pm Discussion, Next Steps Co-Chairs Review agenda face-to-face meeting on Thursday 2015-10-22.

Webinar 5

Webinar #5 was not needed and has been canceled. Please see above for the schedule for the remaining webinars.

F2F Meeting

The following agenda is a draft and may be adjusted based on needs of the meeting

Thursday October 22 2015 - In-person Meeting Day 1 (Decisional)

NOTE: THIS AGENDA WILL BE SUBJECT TO CONTINUOUS REVISION; IT WILL BE LIKELY REVISED UP TO AND DURING THE MEETING.

Location Webex/Tcon
RSNA Headquarters
Oak Brook, IL
Join webex Meeting number: 928 183 704

Meeting Password: "Meeting1" (no quotes)

To receive a call back, provide your phone number when you join the meeting, or call the number below and enter the access code. Call-in toll-free number (US/Canada): 1-866-469-3239 Call-in toll number (US/Canada): 1-650-429-3300

Access code:928 183 704 Global call-in numbers: https://himss.webex.com/himss/globalcallin.php?serviceType=MC&ED=403149227&tollFree=1 Toll-free dialing restrictions: http://www.webex.com/pdf/tollfree_restrictions.pdf

Time Description Presenter Minutes/Notes
8:45-9:00 CT Welcome
  • Introductions
  • Housekeeping
  • Domain Sponsor Announcements
  • Procedures, voting privileges, etc.
  • Agenda review
Co-Chairs, Domain Sponsors
9:00-9:45 CT ITI Capacity and Evaluation Criteria
ITI co-chairs Goal: Decide how many votes each organization will get. Decide on approximate number of proposals to forward on to ITI TC. Evaluate each proposal at end of each presentation (while it is fresh). Decide on physical voting logistics (google spreadsheet, flip chart, other.)

Outcome: Decision: "Focus on value for today, not solution, size will only be a very rough estimate. TC will determine size/effort. Each organization gets 51%+ of the number of proposals (5 points for 8 proposals, 7 proposals would result in 4 points). Planning committee work items are in a different category. Items can be rejected due to wrong committee. Items identified as "Must Do" will be excluded from the straw poll."

9:45-10:15 CT Advocacy Uniformal barcode processing for patient safety and efficiency Esther Peelen, Vincent van Pelt, Tie Tjee, Erik Zwarter, Amanda deLaroque, Robert Breas presentation link TBD

Discussion: Determined need; Seems to be solved by a PIX manager. Suggested that ITI address this use case to a PIX manager profile, and seems like the "content" side of this proposal is better suited to a domain like Pharmacy. Defined UDI as a globally unique ID, has a manufacturer tracing, FDA regulated, and is becoming an international identifier. Parsing is not a problem. Pharmacy domain has defined the workflow. Supply is cross domain. Proposal was to refer to Pharmacy, then Pharmacy will work as far as they can, and then will come back to ITI. Pharmacy has skill sets for this use case (bar coding). Wide variety of bar coding standards. Decision: This will be refereed to Pharmacy and removed from the ITI evaluation process. Jose will liaise with Pharmacy. ITI will keep this as a "parking lot" and ITI will re-assess this proposal for consideration if Pharmacy does NOT take this work item on this cycle.

10:15-10:45 CT Advocacy Maintenance of Profiles Published in 2015 and earlier Lynn Felhofer Presentation WhoHasWhatCPs Discussion: Suggestion was to assess CPs by value, effort, and urgency. Our current CP process is not making progress. Perhaps have a "CP blitz" and dedicated time for CPs. Vendors are less willing to act on profiles if the profile is in Trial Implementation status. And CPs are keeping DSUB, HPD, and others from moving to Final Text status. Concerted focus meetings (such as based on a specific profile) are productive. Discussed value. Assertion was made that lack of work last year equated to lack of value. This issue is really that "are we going to add additional working sessions to work on CPs". Do we separate FHIR CPs? Yes. What's the value of CP work? 1) Moving TIs to FT. 2) Perception issue (responsive). The CPs need to be broken out into categories so we can evaluate them better, such as value, effort, or other categories. Initial ranking: value 9/9, size large.
10:50-11:05 CT Break
11:05-11:30 CT Advocacy Enhanced Patient Privacy Consents Tarik Idris, John Moehrke, Frank Oemig, Jörg Caumanns presentation TBD Discussion: Q: Who is the editor? A: Tarik. Q: What is the interoperability problem? A: Lack of a common vocabulary and common structure. BPPC only works for pre-coordinated policies. Q: Whats the urgency? A: The proposing team has identified an urgent need in current project(s). Multiple solutions are being deployed today that are not-interoperable. Project would include a survey of existing solutions. This proposal would also a combinatorial explosion of per-coordinated policies. Q: Is this a conten profile? A: TBD by the Technical Committee. Q: Is this an overlap with the AHIMA governance implementable white paper. A: Undecided. Several comments indicating the lack of this standard is impeding multiple live initiatives internationally (Illinois, Canada, Texas, NY, FL, more). Q: Where is the enforcement point? A: This proposed profile is independent of the enforcement engine. Effort includes survey of existing solutions/approaches, terminology confusion and definitions. Initial ranking: Value: 9/9 points. Size: Large.
11:30-11:45 CT Advocacy Re-documentation of Document Sharing Profiles Karen Witting Presentation TBD Discussion: Document sharing is becoming a widely adopted profile for many different purposes. This is resulting in many areas where the documentation is not optimal and it is not in-line with the IHE documentation approach. Q: Should ITI TC wait on this given that we are still working on last year's re-documentation work. Q: What's the value? Do we have evidence of confusion? A: The current problem is organization and lack of clarity. Don't have evidence of the value. Q: Is there a way to measure the value provided by previous phases? A: Need to gather information. Q: Can we break this into two groups, CPs and redoc work. Q: Yes. It can be phased/grouped. Comment, seems like too much work when combined with Lynn's CP suggestion, which is that this means 2015/2016 becomes mostly a "maintenance year" as opposed to new work. Important to keep the momentum. Initial ranking: Value: 5/9 points. Size: Medium.
11:45-12:30 CT Advocacy RESTful DSUB Rob Horn presentation TBD Discussion: "mobile" is shorthand for a broad category of devices. This is the proposed next step in IHE support for REST/mobile. Proposer is comfortable making this a two-year work item. DSUB use cases will need to be revised as they doesn't all apply. Need to also need to survey of existing solutions such as web sockets, or other approaches. The TC will be asked to decide on this item being a whitepaper or a profile or both. Q: Why do a white paper before a profile. A: Need to validate the use cases, and the approach. FHIR has identified 5 mechanisms for the concept of a subscription, for example. REST is somewhat contrary to maintaining a state such as a subscription. For example, web sockets doesn't address devices that are turned off. Comment: White paper is the right approach to ensure we get the use cases and requirements right. So this is a white paper proposal now as per the proposer. Q: Is the timing right? A: Yes, so we can do this in parallel with other industry work like FHIR. Also, this keeps the momentum up for RESTful work items. Q: Who would the white paper be used? A: Feedback to FHIR and other groups. Comment: This is not really specific to DSUB; it's a notification / pub-sub concept. Initial ranking: Value: 5/9 points. Size: small.
12:30-13:15 CT Lunch Break
13:30-14:00 CT Advocacy HIT Standards for HIM Practices: Implementable White Paper Proposal Harry Rhodes, Anna Orlova, Diana Warner Presentation TBD Discussion: Q: Please elaborate on the actual problem to be solved? A: A method to assess the completeness of the workflow. Q: Would this apply internationally. A: Authoring teams asserts "yes" but several comments were made stating that this is a USA-centric profile. Comment was made that this seems like a content profile. This appears to be a infinite number of documents being created. Comment made that this is out-of-scope of this committee. Q: Has this been compared to the DAF profile? A: DAF didn't address their needs. Such as "what's inside the profile"? Q: What's the value? A: Need slide was discussed. Initial assessment: The ITI PC is still unclear on the request from the proposer team. We asked the proposers to clarify and re-present Friday morning. We also stated we cannot evaluate the proposal at this time due to lack of understanding. Not assessed at this time.
14:00-14:30 CT Advocacy HPD Updates and USA National Extension Proposal Eric Heflin Presentation RESTful provider directories have already been created without any interoperability (each effort is different and not based on standards). Why can we not solve the problem with standard solutions? Directory solutions vendors work mostly with the Global Enterprises and do not have specific healthcare solutions. Q: Does this apply internationally? A: It is appears to apply internationally, but we do not know of any specific implementations at this time that are seeking a RESTful directory. About 1/3 of the Connectathon HPD registry entries appear to have an international (non US) focus. There is a concern that the RESTful API is so simple to implement that there might not be lots of value in creating an interoperable standard. Q: Could we create a Profile that refers to DAF, and then late promote this to international status? A: Yes (from the proposer). Q: Can we 1) break out the CP work, 2) USA national extension, and 3) RESTful proposals. A: Yes. It was suggested that the IHE USA be engaged to work on USA national extension (Proposer agreed). It was also suggested that the CP aspect be removed and included in the other CP work (the Proposer agreed). And finally it was suggest that the RESTful version proposal be balloted (again the Proposer agreed).
15:30-15:45 CT Break
15:45-16:15 CT General Discussion and preparation for evaluation ITI Planning co-chairs Review of initial assessment. Discussion about which on-going work items will be sent to ITI TC. Discussion about combining proposals, reminders / decision about voting procedures, capacity reminder for ITI, and review of tomorrow's agenda (process used to develop a prioritized work item list). Some items may be work items for the ITI Planning Committee. The evaluation matrix as determined by the the ITI PC has been posted at ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr14-2016-2017/Planning_Cmte/BriefProfileProposals/2015ITIProposalEvaluationMatrix_1_6.xlsx
16:15-17:30 CT Educational Activities ITI Planning co-chairs Review of current gaps in the IHE ITI educational materials. Decide on items the ITI PC will work on this cycle in terms of webinars, presentations, and other educational materials. Note that it may be time for a refresh of all educational materials at this point, plus new materials for updated work from the last two cycles in particular. Current educational materials from ITI PC can be found here: http://wiki.ihe.net/index.php?title=Current_Published_ITI_Educational_Materials. Discussion: Security materials are current except for IUA, and IUA is premature due to rapid change. Could add RESTful ATNA. Consider adding DEN. Suggested creating a "mobile" webinar (John M). DSUB has a lot of updates, and the PPT at least needs to be updated (Mauro). XDR/XDR: Update the deck to include national uses and other updates (Charles). XCDR and XCW over XCA: Needs a new deck and webinar (Charles). Patient ID mgmt: Needs updated slides. (Eric will updated slides and/or webinar to point Mobile Package). Eric will see if HPD is current and then propose updates if need. CSD is still current, no updates needed. XDW materials need updating (i/o documents, folders, etc.) (Mauro). Plus new profiles for last year (RESTful ATNA (Rob), MACM (Carl L), PIXm (Daniel), MHD2 (John M), DSG (John M), National Extensions (done by local deployment domains)) Re-record all webinars that have been lost). Need cross link webinars, put on Vimeo, YouTube, Slide Share, etc. Link from IHE.net educational materials. Metadata update (Manuel M/Bill M). We will also update the Wiki descriptions of profiles.
17:30 pm CT ADJOURN

Friday October 23, 2015 - In-person Meeting Day 2 (Decisional)

NOTE: THIS AGENDA WILL BE SUBJECT TO CONTINUOUS REVISION; IT WILL BE LIKELY REVISED UP TO AND DURING THE MEETING. As of 2015-10-19 it is incomplete for all items after the ballot. We will try to wrap up the meeting by 3pm or earlier to accommodate travel schedules.

Location Webex/Tcon
RSNA Headquarters
Oak Brook, IL
Join webex Meeting number: 928 522 664

Meeting Password: "Meeting1" (no quotes)

To receive a call back, provide your phone number when you join the meeting, or call the number below and enter the access code. Call-in toll-free number (US/Canada): 1-866-469-3239 Call-in toll number (US/Canada): 1-650-429-3300

Access code:928 522 664 Global call-in numbers: https://himss.webex.com/himss/globalcallin.php?serviceType=MC&ED=402487097&tollFree=1 Toll-free dialing restrictions: http://www.webex.com/pdf/tollfree_restrictions.pdf

Time Description Presenter Minutes/Notes
8:30-8:45 CT Welcome, review of the day's plan Re-consider proposal from AHIMA, review evaluation spreadsheet, fill out "must do" column, ITI TC capacity (Gila), determine final list of proposals being considered, ballot, consider liaison, outreach, and other activities.
8:45-9:00 CT Review proposals needing clarification AHIMA paper (Harry, Anna, Diana). Revised proposal were presented. Comment: Q: Option 3 seems similar to a security review, but with a focus on governance. Is that correct? A: Yes. Comment is that there is already an existing IHE governance document called "Template for XDS Affinity Domain Deployment Planning" that probably could use some updates. Suggestion is to update this document. Q: Is the Proposal team receptive to this idea? A: Yes, they will research this. http://www.ihe.net/Technical_Framework/upload/IHE_ITI_White_Paper_XDS_Affinity_Domain_Template_TI_2008-12-02.pdf. Q: For the ITI PC, should this be an ITI TC or an ITI PC work item? A: ITI TC was identified as the right work group. Q: Will the proposal team consider recasting their work as being updates to the XDS Planning Document? A: Yes. The must do column will not be used.
9:00-10:15 CT Discussion and Voting on prioritized work item list Last year they published 13 points. Real capacity should be more like 10 points. One large, and a few smalls or a small and a medium is a reasonable capacity. This year the work seems slightly too large. TC still is seeking guidance on priorities. Will likely have to cut. Each organization casting 4 "points" for this prioritization exercise. Each organization will cast 4 ballots. Use version 1.7 of the evaluation matrix: ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr14-2016-2017/Planning_Cmte/BriefProfileProposals/2015ITIProposalEvaluationMatrix_1_7.xlsx. The 4 points will be tallied and sorted. Then this will be discussed, force ranked, and voted for the formal ballot. The result will be passed to the ITI TC for their assessment. Vote for Profiles: Contact Nancy R to vote if you are remote. If you are in the room, please vote on the white board. Results are posted here. ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr14-2016-2017/Planning_Cmte/BriefProfileProposals/2015ITIProposalEvaluationMatrix_1_8.xlsx. In summary, Proposal #1 received 14 points. Proposal #2 received 11 points. Proposal #3 received 4 points. Proposal #4 received 9 points. Proposal #5 received 5 points. Proposal #6 received 5 points. Proposal #7 was not subject to this prioritization process. Proposal #8 received 0 points. Note that proposal #8 was subject to discussion where it was proposed that the work proceed under IHE USA and with periodic communications to IHE International ITI TC and ITI PC. Column U, called "Prioritization Point Count" in the evaluation matrix was renamed and reflects the total of the points received for the prioritization exercise. Next this will be discussed, the final rank will recorded in column V "Ballot based ranking". The detailed proposals November 3rd, 2015. Please send them to the ITI Co-Chars. Please let the ITI TC Co-Chairs know if this date is a problem. A motion has been made to accept the prioritization in column V of the evaluation matrix to be passed to ITI TC. ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr14-2016-2017/Planning_Cmte/BriefProfileProposals/2015ITIProposalEvaluationMatrix_1_10.xlsx. Motion carries.
  • Complete Ranking by Criteria spreadsheet and review results
  • Review last year's actual velocity (capacity)
  • Review voting procedures - # of ballots per organization
  • Ranking by Ballot - Voting
  • Ballot
Each organization will get # votes. Results will be tallied in the eval spreadsheet. Link

Final Planning Committee Vote for TC Work It was suggested and agreed that the redocumentation work be a plan be presented instead of a new detailed proposal. For the governance paper, it would be useful to have a scope statement with a list of key milestones. SMART methodology was suggested. Also, an ITI TC Co-Chair was approached by a QRPHR Co-Chair with an additional request for a specific work item, for a some type of information profiling metadata for non-patient specific file registry / repository. Clinical Trials has a similar use. This will be refereed to the ITI TC as well, in a manner similar to the USA National Extension.

10:15-10:30 CT Break
10:30-11:30 CT Next steps for the proposals, Wiki Descriptions, Suggestions for improvement for next year (impact assessment process), Brainstorming on ITI PC whitepaper for this cycle, ITI Outreach and liaison activity All Lessons learned: Don't change voting procedures on the fly (from chat, to email, verbal, etc.). Clarify process for national extensions is approved with respect to the planning committee. Agenda wasn't published in advanced and was too flexible. Webex didn't start when the meeting was scheduled. Define terms in the eval spreadsheet. Write down the tally process!

Tally went OK, vote was OK. Should votes be public or semi-anonymous? Webex didn't work well. Why did we receive so many proposals this year? Do we need to publicize the work more to get more proposals? We should perform a strategic planning exercise to identify multi-year directions and opportunities. Contract profiles previously rejected to see if the need is still there? Publish schedule longer in advance. Actively recruit members for ITI TC and PC both.

11:30-12:30 CT IHE International Board Report Karen Witting (IHE ITI Board Liaison)
12:15-13:00 CT LUNCH
13:00-14:00
  • Review voting results
  • Agree on prioritized list of proposals to be assessed by ITI Technical Committee
  • Assignment of authors, due-dates, etc. for completion of Detailed Proposal (Nov #) for turn-over to TC in November
  • Proposals forwarded to ITI TC - due date for detailed Proposals Nov. 4th, 2015 at 11:59:59pm Central Time:

| link to template

  • Discussed proposals not forwarded to ITI TC and plans for ITI Planning followup tasks:
  • Proposals accepted as ITI PC work
  • Work from prior years that are forwarded to ITI TC
14:15-14:30 pm CT Marketing and publicity planning
  • Assess status and impact
  • Plan work items for coming year
  • Assess status and work to be done
  • Discuss suggestions for other opportunities for communicating about ITI work
  • Review of wiki profile descriptions:
  • Educational materials
Wiki details profiles:

Patient Location Tracking detailed description by Ben Patient Identifier Cross-Reference for Mobile (PIXm) Daniel Berezeanu Mobile Alert Communication Management(mACM) Check with Karl Secure Retrieve [SeR] Maurau XCDR David Pyke

Review and update Handbooks and White papers on the wiki


Profile spotlight will probably remain and will be leveraged for marketing

Deprecation of Ccow [PSA] Patient Synchronized Application for the May F2F meeting

Email Mary with the | Website changes

Joint TC-PC meeting at 2pm Friday November 13 Educational work should get scheduled by Daniel and Eric offline with the presentors Plan the re-recording of webinars should be scheduled by Daniel and Eric


2:30 - 3:00 pm CT Wrap-up
3:00 pm CT ADJOURN


November 13, 2015 - In-person Joint ITI PC/TC Meeting (Decisional)

Location Webex/Tcon
RSNA Headquarters
Oak Brook, IL
See the ITI TC meeting invitation for the Web meeting details

Joint ITI PC and TC decisional meeting at 11:30-12:30 Meeting notes may be found at: ftp://ftp.ihe.net//IT_Infrastructure/iheitiyr14-2016-2017/Planning_Cmte/Meetings/NovemberMeeting/The%20final%20ITI%20PC%202015%20decisions%20v2.docx%22