Difference between revisions of "Rad Tech Minutes 2020-01-27-30"
Jump to navigation
Jump to search
Line 191: | Line 191: | ||
:12:30-14:00: AI Workflow (10.5) - Add references to UPS transactions to AIW-I and review those transactions to see if adjustments required. | :12:30-14:00: AI Workflow (10.5) - Add references to UPS transactions to AIW-I and review those transactions to see if adjustments required. | ||
:14:00-15:00: TF Maintenance (7.5) - Assign volume editor to start TF re-structure. Timeline for publication for final text (need to communicate to Mary) | :14:00-15:00: TF Maintenance (7.5) - Assign volume editor to start TF re-structure. Timeline for publication for final text (need to communicate to Mary) | ||
+ | |||
+ | ===Annex: PC-Prep Closing Assessments=== | ||
+ | |||
+ | * '''Profile Name: AI Workflow''' | ||
+ | ** Did we line-by-line the entire document | ||
+ | ** How ready is it to go out for PC: Completely, Almost, Soonish, Hmmm | ||
+ | ** Which open issues are risky, and why | ||
+ | ** Are all open issues phrased to solicit the needed information to close them? | ||
+ | ** Which use cases need more input | ||
+ | ** Which issues from the Kickoff Closing Assessment are still unresolved | ||
+ | ** What significant debates in PC-prep were not anticipated in the Kickoff | ||
+ | ** Review the "complexity points" in the evaluation. Did each get appropriate text coverage/resolution? | ||
+ | ** Do the effort points in the evaluation still seem right? | ||
+ | ** How does the scope feel in terms of being a useful chunk of work? (Needs more? Just right? More than enough?) | ||
+ | ** How is the work fitting in the allocated bandwidth? (Time to spare? Just right? Things were left undone?) | ||
+ | ** Did the Breakdown of Tasks accurately reflect the work? What extra tasks arose? | ||
+ | ** Looking forward, if you had to reduce scope to hit TI, what would you drop | ||
+ | ** Have the promised resources manifested | ||
+ | ** What vendors are engaged (for each actor) | ||
+ | ** When will we have sample data/objects | ||
+ | ** Who should specifically be targeted for Public Comment feedback | ||
+ | ** Was the profile where it needed to be at the start of the PC meeting (See "PC Prep Meeting" above), if not what was the gap | ||
+ | ** Was the profile where it needed to be at the end of the PC meeting, if not what was the gap | ||
+ | ** How many tcons would you like between now and PC Publication | ||
+ | ** Do you need any tcons before TI Prep Meeting | ||
+ | |||
+ | |||
+ | * '''Profile Name: AI Results''' | ||
+ | ** Did we line-by-line the entire document | ||
+ | ** How ready is it to go out for PC: Completely, Almost, Soonish, Hmmm | ||
+ | ** Which open issues are risky, and why | ||
+ | ** Are all open issues phrased to solicit the needed information to close them? | ||
+ | ** Which use cases need more input | ||
+ | ** Which issues from the Kickoff Closing Assessment are still unresolved | ||
+ | ** What significant debates in PC-prep were not anticipated in the Kickoff | ||
+ | ** Review the "complexity points" in the evaluation. Did each get appropriate text coverage/resolution? | ||
+ | ** Do the effort points in the evaluation still seem right? | ||
+ | ** How does the scope feel in terms of being a useful chunk of work? (Needs more? Just right? More than enough?) | ||
+ | ** How is the work fitting in the allocated bandwidth? (Time to spare? Just right? Things were left undone?) | ||
+ | ** Did the Breakdown of Tasks accurately reflect the work? What extra tasks arose? | ||
+ | ** Looking forward, if you had to reduce scope to hit TI, what would you drop | ||
+ | ** Have the promised resources manifested | ||
+ | ** What vendors are engaged (for each actor) | ||
+ | ** When will we have sample data/objects | ||
+ | ** Who should specifically be targeted for Public Comment feedback | ||
+ | ** Was the profile where it needed to be at the start of the PC meeting (See "PC Prep Meeting" above), if not what was the gap | ||
+ | ** Was the profile where it needed to be at the end of the PC meeting, if not what was the gap | ||
+ | ** How many tcons would you like between now and PC Publication | ||
+ | ** Do you need any tcons before TI Prep Meeting |
Revision as of 12:24, 30 January 2020
(Number in parentheses is cumulative total hours for week)
Monday, January 27, 2019: 8:30 am - 5:00 pm Central Time (CT)
- IHE Radiology Technical Committee Roster
- 08:30-09:00: Breakfast, Welcome, Patent Disclosure Announcement, Agenda Review
- Lynn Felhofer, IHE Radiology Technical Project Manager
- Kevin O'Donnell, Canon Medical
- Jonathan Whitby, Canon Medical
- Wim Corbijn, Philips
- Kinson Ho, Change Healthcare
- Harald Zachmann, IBM Watson
- Chris Lindop, Citius Tech
- Brad Genereaux, SIIM
- Antje Schroeder, Siemens Healthineers
- David Kwan, CCO
- Yi-Hwa Liu, Yale
- Andrei Leontiev, Visage Imaging
- Steve Nichols, GE
- Charles Parisot, InteropEhealth
- Hamid Neshat, Agfa
- Nichole Knox, RSNA
- Goal of meeting is to finalize documents by end of the meeting for Public Comment publication.
- Reviewed Patent Disclosure Announcement
- 09:00-10:30: AI Result (1.5)
- Read and agree document is okay for context
- Flag comments and highlight in yellow items to come back to for further review
- Action: Review new definition process; may need a new one for this document; add to DCC on either 1/28 or February call depending on outcome
- 10:30-12:00: AI Workflow (1.5)
- 12:00-13:00: Lunch
- 13:00-14:00: Technical Framework Maintenance (1) - Review Shareathon by Steve, CP Ballot Comments Review, SWF.b final text questionnaire
- Focused on Shareathon review by Steve
- 14:00-15:30: AI Result (3)
- Committee homework to review and return with questions and comments on 1/28
- 15:30-17:00: AI Workflow (3)
Tuesday, January 28, 2019: 8:30 am - 5:00 pm CT
- IHE Radiology Technical Committee Roster
- 08:30-09:00: Breakfast, Welcome, Patent Disclosure Announcement, Agenda Review
- Lynn Felhofer, IHE Radiology Technical Project Manager
- Kevin O'Donnell, Canon Medical
- Jonathan Whitby, Canon Medical
- Wim Corbijn, Philips
- Kinson Ho, Change Healthcare
- Harald Zachmann, IBM Watson
- Chris Lindop, Citius Tech
- Brad Genereaux, SIIM
- Antje Schroeder, Siemens Healthineers
- David Kwan, CCO
- Andrei Leontiev, Visage Imaging
- Nichole Knox, RSNA
- 09:00-10:30: AI Result (4.5)
- Committee homework - finish reading the display transaction and concept section. If committee can accomplish this, we can discuss open issues.
- 10:30-12:00: AI Workflow (4.5)
- 12:00-13:00: Lunch
- 13:00-15:00: TF Maintenance (3)
- CP-RAD-258: Accepted with changes as discussed; move to Final Text)
- CP-RAD-356: Accepted w/editorial changes; move to Final Text
- CP-RAD-378: pending; may be able to review again later in the week
- CP-RAD-379: Accepted; move to Final Text
- CP-RAD-379: Accepted; move to Final Text
- Due to number of people having problems accessing the IHE FTP site, Kinson is asking for a volunteer to maintain the FTP site, update the spreadsheet
- Discussion about TF Maintenance proposed breakdown of Radiology Technical Framework
- Editor will be assigned by end of this meeting but the plan is listed in link above.
- Goal is to finish in this cycle by June/July.
- 15:00-17:00: AI Workflow (6.5)
- Committee homework: Look at concept section. Pay particular attention to the 4.80.4.1.2.1.1. AI Service Request and the X.4.2.1 AI Workflow Clinical Example.
- Desired results for end of day on 1/29/2020
- TF Maintenance: SWF.b final text, incoming CP review, Final Review of CP-378, Connectathon debrief and preview of EU Connectathon
- AI Workflow morning: Review Concept Section (e.g. business logic separate from task management, consideration regarding Orchestrator and Performer, etc)
- AI Results afternoon – Through whole document, start review side bar comments
- AI Workflow afternoon – Vol 1 complete review, Attribute requests for Rad-80 Create Workitem
- Desired results for end of day on 1/29/2020
- Desired results for end of day on 1/30/2020
- AI Result morning: Completed review most side bar comments, ready for Public Comment publication (remaining side bar comments will be in open questions)
- AI Workflow morning: : Review Concept Section, in particular the reporting workflow integration, RAD-49 Instance Availability Notification
- Scheduling and Evaluation Checkpoint
- AI Workflow afternoon: Add references to UPS transactions to AIW-I and review those transactions to see if adjustments required.
- TF Maintenance – Assign volume editor to start TF re-structure. Timeline for publication for final text (need to communicate to Mary)
- Desired results for end of day on 1/30/2020
Wednesday, January 29, 2019: 8:30 am - 5:00 pm CT
- IHE Radiology Technical Committee Roster
- 08:30-08:30: Breakfast, Welcome, Patent Disclosure Announcement, Agenda Review
- Lynn Felhofer, IHE Radiology Technical Project Manager
- Kevin O'Donnell, Canon Medical
- Jonathan Whitby, Canon Medical
- Wim Corbijn, Philips
- Kinson Ho, Change Healthcare
- Harald Zachmann, IBM Watson
- Chris Lindop, Citius Tech
- Antje Schroeder, Siemens Healthineers
- Andrei Leontiev, Visage Imaging
- Teri Sippel Schmidt, Marquette University
- Brad Genereaux, SIIM
- Chris Carr, RSNA
- Nichole Knox, RSNA
- 08:30-10:00: TF Maintenance (4.5) - SWF.b final text, incoming CP review, Final review of CP-378, Connectathon debrief and preview of EU Connectathon
- IHE Rad Tech committee motioned to approve SWF.b for Final Text
- Unanimously approved. Now goes to the planning committee. Kinson will send email to planning committee co-chairs with information on technical committee recommendation and offer to help.
- IHE USA Connectathon Radiology Recap
- IHE Rad Tech committee motioned to approve SWF.b for Final Text
- 10:00-10:30: AI Results
- 10:30-12:00: AI Workflow (8) - Review Concept Section (e.g. business logic separate from task management, consideration regarding Orchestrator and Performer, etc.)
- 12:00-13:00: Lunch
- 13:00-13:30: Discuss communication strategy to promote the AI profiles to the AI communities
- AI Communication
- Activities
- February / March
- Public comments publication (February / March)
- Target audiences
- the RSNA AI vendors - get the list and contact from Chris Carr
- Neil's group
- DICOM WG-23 - Larry
- Webinar during public comment - Brad, Kevin Chris Lindop (March 3 1pm CT - 1 hour)
- Target specific sections in the profile - Rad Planning Committee, RSNA RIC - Chris Roth, David Mandelson
- Target audiences
- ECR (March) - Vienna - Plan to have DSI session, Peter is our evangelist
- HIMSS? (March 9-13) - Orlando - during the HIMSS-SIIM meeting?
- Public comments publication (February / March)
- April
- RBMA (April) - Interoperability session - Kinson
- IHE Rad TC Trial Implementation Preparation F2F meeting
- May
- Trial Implementation publication
- June
- SIIM
- SIIM Hackathon (June) - Mohannad
- SIIM session
- SIIM
- July / August
- IHE Radiology Webinar
- September
- SIIM C-MIMI (September 13-14)
- October
- ACR Informatics Summit (October 24-25)
- November
- RSNA (Nov) - Advocacy meeting at the AI Showcase area
- Other
- SIIM webinar - Any time - Brad / Kevin
- February / March
- Outreach opportunites
- SIIM Outreach committee - Raym, Brad
- SIIM machine learning committee
- ACR DSI
- RSNA RIC - Chris Roth
- AI Champions
- Kevin
- Chris Lindop
- Brad the Ambassador
- Brad's demo (to be open source in Github)
- 13:30-15:30: AI Results (6.5) - Through whole document, start review side bar comments
- 15:30-17:30: AI Workflow (10) - Vol 1 complete review, Attribute requests for RAD-80 Create Workitem
Thursday, January 30, 2019: 8.30 am - 3:00 pm CT
- IHE Radiology Technical Committee Roster
- Lynn Felhofer, IHE Radiology Technical Project Manager
- Kevin O'Donnell, Canon Medical
- Jonathan Whitby, Canon Medical
- Wim Corbijn, Philips
- Kinson Ho, Change Healthcare
- Harald Zachmann, IBM Watson
- Chris Lindop, Citius Tech
- Antje Schroeder, Siemens Healthineers
- Andrei Leontiev, Visage Imaging
- David Kwan, CCO
- Chris Carr, RSNA
- Nichole Knox, RSNA
- 08:30-10:00: AI Result (7.5) - Completed review most side bar comments, ready for Public Comment publication (remaining side bar comments will be in open questions)
- 10:00-11:00: AI Workflow (9) - Review Concept Section, in particular the reporting workflow integration, RAD-49 Instance Availability Notification
- 11:00-12:00: Scheduling + Evaluation Checkpoint
- 12:00-12:30: Lunch
- 12:30-14:00: AI Workflow (10.5) - Add references to UPS transactions to AIW-I and review those transactions to see if adjustments required.
- 14:00-15:00: TF Maintenance (7.5) - Assign volume editor to start TF re-structure. Timeline for publication for final text (need to communicate to Mary)
Annex: PC-Prep Closing Assessments
- Profile Name: AI Workflow
- Did we line-by-line the entire document
- How ready is it to go out for PC: Completely, Almost, Soonish, Hmmm
- Which open issues are risky, and why
- Are all open issues phrased to solicit the needed information to close them?
- Which use cases need more input
- Which issues from the Kickoff Closing Assessment are still unresolved
- What significant debates in PC-prep were not anticipated in the Kickoff
- Review the "complexity points" in the evaluation. Did each get appropriate text coverage/resolution?
- Do the effort points in the evaluation still seem right?
- How does the scope feel in terms of being a useful chunk of work? (Needs more? Just right? More than enough?)
- How is the work fitting in the allocated bandwidth? (Time to spare? Just right? Things were left undone?)
- Did the Breakdown of Tasks accurately reflect the work? What extra tasks arose?
- Looking forward, if you had to reduce scope to hit TI, what would you drop
- Have the promised resources manifested
- What vendors are engaged (for each actor)
- When will we have sample data/objects
- Who should specifically be targeted for Public Comment feedback
- Was the profile where it needed to be at the start of the PC meeting (See "PC Prep Meeting" above), if not what was the gap
- Was the profile where it needed to be at the end of the PC meeting, if not what was the gap
- How many tcons would you like between now and PC Publication
- Do you need any tcons before TI Prep Meeting
- Profile Name: AI Results
- Did we line-by-line the entire document
- How ready is it to go out for PC: Completely, Almost, Soonish, Hmmm
- Which open issues are risky, and why
- Are all open issues phrased to solicit the needed information to close them?
- Which use cases need more input
- Which issues from the Kickoff Closing Assessment are still unresolved
- What significant debates in PC-prep were not anticipated in the Kickoff
- Review the "complexity points" in the evaluation. Did each get appropriate text coverage/resolution?
- Do the effort points in the evaluation still seem right?
- How does the scope feel in terms of being a useful chunk of work? (Needs more? Just right? More than enough?)
- How is the work fitting in the allocated bandwidth? (Time to spare? Just right? Things were left undone?)
- Did the Breakdown of Tasks accurately reflect the work? What extra tasks arose?
- Looking forward, if you had to reduce scope to hit TI, what would you drop
- Have the promised resources manifested
- What vendors are engaged (for each actor)
- When will we have sample data/objects
- Who should specifically be targeted for Public Comment feedback
- Was the profile where it needed to be at the start of the PC meeting (See "PC Prep Meeting" above), if not what was the gap
- Was the profile where it needed to be at the end of the PC meeting, if not what was the gap
- How many tcons would you like between now and PC Publication
- Do you need any tcons before TI Prep Meeting