Difference between revisions of "Rad Tech Minutes 2022-02-07-11"

From IHE Wiki
Jump to navigation Jump to search
 
Line 1: Line 1:
 
==Location==
 
==Location==
  
−
:* Virtual
+
:* Virtual Via Zoom
−
:* Via Zoom
 
  
 
==Meeting Directory==
 
==Meeting Directory==

Latest revision as of 16:03, 22 February 2022

Location

  • Virtual Via Zoom

Meeting Directory

Topics

  • Interactive Multimedia Reporting (55%)
  • AIR Datasets and Root Results (30%)
  • Maintenance (25%) (for this meeting we will work at 15% for Maintenance)

Notes to Explain Agenda

  • (Number in parentheses is cumulative total hours for week)
  • One action item that came out from the retrospective meeting is try to schedule some ‘editorial time’ vs ‘discussion time’.
    • Discussion Time: Focus on the actual design discussion
    • Editorial Time: Smaller group discussion with focus on getting the text in a good shape

Monday, February 7, 2022

  • A1: 8:30am-9:00am Administrative Time
  • S1: 9:00am-10:30am: AIR Datasets and Root Results (AIR) (1.5)
    • Finished first pass and Kevin will post today's version to Google Folder and resume with comments and improvements on Tuesday.
    • Will work through technical committee questions tomorrow.
  • S2: 10:45am-12:45pm: Interactive Multimedia Reporting (IMR) (2.0)
  • A2: 1:15pm-1:45pm: Administrative time not needed; used to start IMR early
  • S3: 1:45pm-2:45pm: Interactive Multimedia Reporting (IMR) (3.5)
    • Work in progress.

Tuesday, February 8

  • A1: 8:30am-9:00am Administrative Time
    • Introductions (Name and IHE Member Organization)
    • IHE Radiology Technical Committee Roster
    • IHE International Member Organizations
      • Brian Bialecki, ACR
      • Wim Corbijn, Philips
      • Kinson Ho, Arterys
      • David Kwan, Insygnia Consulting
      • Chris Lindop, GE
      • Weber Marett, IBM Watson Healthcare
      • Steve Nichols, GE
      • Kevin O'Donnell, Canon Medical
      • Antje Schroeder, Siemens Healthineers
      • Khaled Younis, Philips
    • Non-voting Attendees
      • Daniel Bach, Smile CDR
      • Seth Berkowitz, MD
      • Sean Doyle
      • Lynn Felhofer, IHE Radiology Technical Project Manager
      • Rob Horn
      • Nichole Knox, RSNA
      • TeRhonda McGee, RSNA
      • Neil Tenenholtz
      • Sophie Tekeste, Smile CDR
    • IHE Patent Disclosure
  • S1: 9:00am-11:00am: Interactive Multimedia Reporting (IMR) (5.5)
    • Continue to work on modeling the IMR FHIR resources.
  • S2: 11:15am-12:45pm: Maintenance (1.5)
    • SOLE CPs
      • CP-RAD-458-xx - SOLE: Add codes for AI and AIW-I (Chris)
        • Chris presented slides representing the decisions of the AI group on audit codes and AI-related event details, including a details spreadsheet of events.
        • NEXT STEP: Chris will translate today’s discussion into CP-RAD-448 with edits/additions to SOLE
      • CP-RAD-457-07 - SOLE: update to enable ITI-20 FHIR Feed semantics (Lynn)
        • - Lynn led a review of decisions that RAD Tech previously made regarding the requirements for the Event Reporter and Event Repository. Previously, we decided that the Repository shall support both syslog and FHIR semantics, and the Event Reporter could choose either (no options). Today we decided to follow the ITI/ATNA model and introduce ATX: FHIR Feed and ATX: TLS Syslog options for both the SOLE Reporter and Repository actors
        • NEXT STEP: Lynn will make those edits this week.
    • Prioritize Maintenance topics (see below)
  • S3: 1:15pm-2:45pm: AIR Datasets and Root Results (AIR) (3.0)

Wednesday, February 9

  • A1: 8:30am-9:00am Administrative Time
    • Introductions (Name and IHE Member Organization)
    • IHE Radiology Technical Committee Roster
    • IHE International Member Organizations
      • Wim Corbijn, Philips
      • Matt Hayes, Radiology Partners
      • Kinson Ho, Arterys
      • David Kwan, Insygnia Consulting
      • Chris Lindop, GE
      • Yi-Hwa Liu
      • Weber Marett, IBM Watson Healthcare
      • Steve Nichols, GE
      • Kevin O'Donnell, Canon Medical
      • Antje Schroeder, Siemens Healthineers
      • Jonathan Whitby, Canon Medical
      • Khaled Younis, Philips
    • Non-voting Attendees
      • Daniel Bach, Smile CDR
      • Seth Berkowitz, MD
      • Lynn Felhofer, IHE Radiology Technical Project Manager
      • Nichole Knox, RSNA
      • TeRhonda McGee, RSNA
      • Sophie Tekeste, Smile CDR
    • IHE Patent Disclosure
    • Check w/AIR team about switching Friday's session to Thursday am maintenance time slot
  • S1: 9:00am-10:30am: Interactive Multimedia Reporting (IMR) (7.0)
    • Finish reviewing constraints on diagnostic report and dependent resources
    • Start reviewing transactions.
  • S2: 10:45am-12:45pm: AIR Datasets and Root Results (AIR) (5.0)
    • Continue working on updates from committee discussion and be prepared to review on Thursday.
  • A2: 1:15pm-1:45pm: Prioritize RAD's outstanding maintenance work? What can we accomplish this week? (2.0)
  • S3: 1:45pm-3:15pm: Interactive Multimedia Reporting (IMR) (8.5)


Thursday, February 10

  • A1: 8:30am-9:00am Administrative Time
    • Introductions (Name and IHE Member Organization)
    • IHE Radiology Technical Committee Roster
    • IHE International Member Organizations
      • Wim Corbijn, Philips
      • Kinson Ho, Arterys
      • David Kwan, Insygnia Consulting
      • Chris Lindop, GE
      • Weber Marett, IBM Watson Healthcare
      • Steve Nichols, GE
      • Kevin O'Donnell, Canon Medical
      • Antje Schroeder, Siemens Healthineers
      • Michael Kelm, Siemens Healthineers
      • Khaled Younis, Philips
    • Non-voting Attendees
      • Lynn Felhofer, IHE Radiology Technical Project Manager
      • Nichole Knox, RSNA
      • TeRhonda McGee, RSNA
    • IHE Patent Disclosure
  • S1: 9:00am-10:30am: Interactive Multimedia Reporting (IMR) (10.0)
  • S2: 10:45am-12:45pm: Maintenance (4.0)
  • A2: 1:15pm-2:15pm: Administrative Time
    • Nichole will email the IHE Rad Tech Committee asking their preference for switching the April meeting from the week of the 11th to the 25th. Preference deadline 2/17.
  • S3: 2:15pm-3:15pm: AIR Datasets and Root Results (AIR) (6.0)


Friday, February 11

  • A1: 8:30am-9:00am Administrative Time
    • Introductions (Name and IHE Member Organization)
    • IHE Radiology Technical Committee Roster
    • IHE International Member Organizations
      • Wim Corbijn, Philips
      • Matt Hayes, Radiology Partners
      • Kinson Ho, Arterys
      • David Kwan, Insygnia Consulting
      • Andrei Leontiev, Visage Imaging
      • Chris Lindop, GE Healthcare
      • Kevin O'Donnell, Canon Medical
      • Antje Schroeder, Siemens Healthineers
      • Steve Nichols, GE Healthcare
      • Weber Marett, IBM Watson Healthcare
      • Jonathan Whitby, Canon Medical
      • Khaled Younis, Philips
    • Non-voting
      • Seth Berkowitz, MD
      • Lynn Felhofer, Radiology Technical Project Manager
      • Nichole Knox, RSNA
      • TeRhonda McGee, RSNA
      • Sophie Tekeste, Smile CDR
    • IHE Patent Disclosure
  • S1: 9:00am-10:30am: Interactive Multimedia Reporting (IMR) (11.5)
  • S2: 10:45am-12:45pm: Interactive Multimedia Reporting (IMR) (13.5)
  • A2: 1:15pm-1:45pm: AIR Datasets and Root Results (AIR) (6.5)
    • Motion to approve AIR Datasets and Root Results as modified.
      • Unanimously approved.
  • S3: 1:45pm-2:45pm: Administrative (voting)
    • Decisions to move to Public Comment
    • Briefly revisit moving the April meeting
    • Wrap-up assessment
    • Tconn scheduling
    • 2/21 - 11:00am-1pm CT - IMR
    • 2/24 - 10am-12pm CT - IMR
    • 2/25 - 10am-12pm CT - IMR
    • Timeline for publication
      • Feb 21 - deliver to Mary
      • Mar 9 - deliver to Mary
      • Mar 1 - start of public comment AIR
      • Mar 16 - start of public comment AIR
      • Mar 29 - end of public comment AIR
      • Apr 18 - start of public comment AIR
      • - (tentative) t-conns to triage public comments prior to F2F
      • Apr-25?? - beginning of RAD Tech April meeing
    • Draft (in progress): Basic Guide to Public Comment on an IHE FHIR IG (in the IMR folder on google drive)
    • 2022 Connectathon update


PC-Prep Closing Assessments

Expectations (Copied from Guidance)

  • PC Prep Meeting (Januaryish)
  • Arrive with a draft Public Comment version of the document
  • Committee will review in detail and vote it ready for public comment if it meets the following criteria
  • All parts of the profile are written (not in stone, but the parts are all in place)
  • All questions where you want or need input/confirmation/consent from the wider community are listed in the Open Issues section
  • Issues that have been decided but you want to avoid rehashing with the email reviewers who didn’t hear the discussion are documented in Closed Issues
  • Reviewers are permitted to re-open closed issues but they had better introduce new facts/considerations beyond what’s documented in the closed issue.
  • Goal: Leave with a ready to publish for PC (possibly after some remaining tidy-up edits)


  • Profile Name: AI Results+ (AIR+)
    • Did we line-by-line the entire document
      • Basically yes. (Except for some of the examples)
    • How ready is it to go out for PC: Completely, Almost, Soonish, Hmmm
      • Almost Completely
    • Which open issues are risky, and why
      • None. Don't think any would drive significant change.
    • Are all open issues phrased to solicit the needed information to close them?
      • Yes.
    • Which use cases need more input
      • Comments on display/navigation of trees is welcome
    • Which issues from the Kickoff Closing Assessment are still unresolved
      • Still need to get tooling for example binary object generation.
    • What significant/long debates in PC-prep were not anticipated in the Kickoff
      • (Need cochairs to log this during the week)
      • There was one or two things but I can't remember what they were now.
    • Review ALL "uncertainty points" in the evaluation. Are all now resolved?
      • Yes
    • Review ALL "complexity points" in the evaluation. Did each get appropriate text coverage/resolution?
      • Yes
    • Review the "effort points" in the evaluation. Still seems right? Need more?
      • Yes (maybe increased examples a bit and decreased a couple specification bits)
      • (Add markup/review of Story points inline in spec might be good.)
    • How does the scope feel in terms of being a useful chunk of work? (Needs more? Just right? More than enough?)
      • Feels right.
    • How is the work fitting in the allocated bandwidth? (Time to spare? Just right? Things were left undone?)
      • Feels Right
    • Did the Breakdown of Tasks accurately reflect the work? What extra tasks arose?
      • Yes. Slight shifts.
    • Looking forward, if you had to reduce scope to hit TI, what would you drop
      • Still binary objects and fewer text examples.
    • Have the promised resources manifested
      • Yes. Focus group was helpful.
    • What vendors are engaged (for each actor)
      • Evidence Creator: Siemens, Canon, GE, IBM
      • Image Display: Siemens, Canon, IBM
    • When will we have sample data/objects
      • Text by TI, hopefully binaries not too long after, sometime in the summer. (DCMTK xml->DICOM)
    • Who should specifically be targeted for Public Comment feedback
      • RIC, MITA AI, ACR, IAIP Demo List,
    • 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
      • Yes. A couple holes in examples.
    • Was the profile where it needed to be at the end of the PC meeting, if not what was the gap
      • Yes.
    • How many tcons would you like between now and PC Publication
      • 0
    • Do you need any tcons before TI Prep Meeting
      • Maybe - depends on feedback. Nice to triage comments. Set timeframe/timeline today but actual call schedule can wait.
  • Profile Name: Interactive Multimedia Reporting (IMR)
    • Did we line-by-line the entire document
      • Not yet.
    • How ready is it to go out for PC: Completely, Almost, Soonish, Hmmm
      • Soonish? Maybe 30% left? Covered most uncertainty but basic review and maybe some complexity to still cover?
    • Which open issues are risky, and why
      • Too early to say (risky)
      • Some gaps with FHIR R4 that R5 MIGHT address (e.g. ImageSelection)
      • (Wim) Medico-legal requirements on report content - do we need to profile that and if so, to what degree. (e.g. DLP/Dose regs)
      • Maybe more later...
    • Are all open issues phrased to solicit the needed information to close them?
      • ?? Haven't reviewed yet.
    • Which use cases need more input
      • Maybe OK.
    • Which issues from the Kickoff Closing Assessment are still unresolved
      • Still adding concept section for Structured (findings, impressions sections) vs Structured (coded contents)
      • (Effort was indeed low, but didn't stay in the ballpark)
      • IHE RAD (and author) getting familiar with IG style and tooling is still resolving, hopefully mostly OK soon.
      • Accurately identified key issues if not the amount of effort
        • DiagnosticReport mapping
        • How to profile FHIR resources, what constraints IMR need to impose on each resource
    • What significant debates in PC-prep were not anticipated in the Kickoff
      • Many debate topics were predicted (but maybe more involved)
      • Hadn't anticipated "How to scope/review IG content"
    • Review ALL "uncertainty points" in the evaluation. Are all now resolved?
      • Most are. Some left.
    • Review ALL "complexity points" in the evaluation. Did each get appropriate text coverage/resolution?
      • Mostly. Still working on it.
    • Review the "effort points" in the evaluation. Still seems right? Need more?
      • Having to juggle between tools (where edits are made vs where the committee can see the text) increased worktime.
      • Also time for the author to learn/adapt to very different tools. (Which have some pluses)
      • TODO review this later when we are closer to done.
    • How does the scope feel in terms of being a useful chunk of work? (Needs more? Just right? More than enough?)
      • Feels about right. It's a lot of work, but are being pragmatic to avoid scope creep in the display functions and encoding
    • How is the work fitting in the allocated bandwidth? (Time to spare? Just right? Things were left undone?)
      • Running over, but feels like we have a handle on it.
    • Did the Breakdown of Tasks accurately reflect the work? What extra tasks arose?
      • TODO consider adding learning/familiarizing with the new tools and how they affect our content and process
    • Looking forward, if you had to reduce scope to hit TI, what would you drop
      • Query/retrieve
      • otherwise if we go too far over we drop it completely.
    • Have the promised resources manifested
      • Yes. Clinical and Technical have been great.
    • What vendors are engaged (for each actor)
      • Report Creator - Mmodal (maybe),
      • Report Reader - Arterys, Canon,
      • Report Repository -
    • When will we have sample data/objects
      • Have some now. Tooling helps a lot with this
    • Who should specifically be targeted for Public Comment feedback
      • TODO
    • 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
      • Not quite. There were uncertainty discussions that were not resolved in November. (e.g. Display pathways)
    • Was the profile where it needed to be at the end of the PC meeting, if not what was the gap
      • Not yet. There was more effort/complexity to work through
    • How many tcons would you like between now and PC Publication
      • 3x2hour Sessions
    • Do you need any tcons before TI Prep Meeting
      • Maybe - depends on feedback. Nice to triage comments. Set timeframe/timeline today but actual call schedule can wait.
Retrieved from "http://wiki.ihe.net/index.php?title=Rad_Tech_Minutes_2022-02-07-11&oldid=127752"