Rad Tech Minutes 2026-11-09-13: Difference between revisions

From IHE Wiki
Jump to navigation Jump to search
 
(5 intermediate revisions by the same user not shown)
Line 86: Line 86:
:*S1: 9:00am-11:00am: AI Service Capabilities[9.5 hr]
:*S1: 9:00am-11:00am: AI Service Capabilities[9.5 hr]
:*S2: 11:15am-12:45pm: Maintenance [10.25h]
:*S2: 11:15am-12:45pm: Maintenance [10.25h]
:*S3: 1:30pm-3:30pm: AI Service Capabilities - [[Checkpoint Assessment] checkpoint assessment] [11.5 hr]  
:*S3: 1:30pm-3:30pm: AI Service Capabilities - [[Checkpoint Assessment]] [11.5 hr]  
:*S4: 3:45pm-5:00pm: IRA Content[7.5 h]
:*S4: 3:45pm-5:00pm: Maintenance[7.5 h]
:** Reviewed and updated the Assessment of TI profile and plan for Final Text and Retire/Deprecate
:** DIFF is ready for FT approval - need to schedule PC vote to approve


=='''Friday, November 13, 2026'''==
=='''Friday, November 13, 2026'''==
Line 94: Line 96:
:** Completed CP-RAD-578 to go to Ballot 2026C
:** Completed CP-RAD-578 to go to Ballot 2026C
:** Discussed split of POCUS from "core" EBIW. As a result, we decided that the right way to do that would be to refactor the EBIW supplement to introduce 3 profiles making the Lightweight Modality and POCUS options into their own profiles referring to transactions in the "core" EBIW profile. Also need to determine if references from RAD-132 transaction in EBIW profile to RAD-128 in RD profile should be reversed (in case we are not expecting the RD to become FT soon)
:** Discussed split of POCUS from "core" EBIW. As a result, we decided that the right way to do that would be to refactor the EBIW supplement to introduce 3 profiles making the Lightweight Modality and POCUS options into their own profiles referring to transactions in the "core" EBIW profile. Also need to determine if references from RAD-132 transaction in EBIW profile to RAD-128 in RD profile should be reversed (in case we are not expecting the RD to become FT soon)
:*S2: 10:45am-12:45pm IRA Content including checkpoint assessment [9.5]
:** Discussed assignment of next Top 10 - agreed that addressing the SWF.b CPs will be a good goal for this cycle. Andrei and Jason will review which of 15 currently assigned CPs worth to move forward and which ones are no longer valid and should be cancelled.
 
:*S2: 10:45am-11:45pm IRA Content including checkpoint assessment [8.5]
Profile Name: IRA Finding Content
* Describe gaps in Use Case coverage
:* With the "Pattern A/B/C" work, a compelling range of use cases feel covered.
* Review ALL "uncertainty points" in the evaluation. Is there a resolution plan for each?
:* Reviewed. All were discussed. Some were resolved. Some have plan for further evolution.
* Do the effort points in the evaluation still seem right?
:* No, will likely need to do some re-writing of existing transactions, will likely need to introduce some mechanisms for "intention channels"
* Did the Breakdown of Tasks accurately reflect the work? What extra tasks arose?
:* See previous question
:* BoD was a good set of topics which were all discussed, but there are some deeper issues being prepped and hopefully resolved.
* Describe unresolved technical issues/tasks
:* Posting references to FHIRcast
:* Hosting transient instances (some of which might migrate to persistent) on a FHIR Server associated with the hub rather than inside the hub
:* List/Channels with an intention code to telegraph/coordinate collaboration behaviors (sender and receivers)
:* Review Marc's proposals for MQTT-based PubSub
* Describe potential practical issues
:* Will need to coordinate with Isaac/Bas/FHIRcast folks about our proposals.
:* Once concepts are properly prepared and vetted with a couple of TC folks, will schedule calls with Isaac
:* Then will come back to TC for discussion/confirmation/evolution
* Review the open issue list. Does it feel complete
:* Not yet. Many good open issues are captured in discussion text but are not yet collated into a properly worded list.
* Which open issues feel most risky; what other risks exist?
:* See unresolved Tech Issues and Practical Issues above
:* Need for schedule/technical coordination with other groups (FHIRcast)
* How is the work fitting in the allocated bandwidth? (Time to spare? Just right? Things were left undone?)
:* Time to spare but it's because there are issues needing groundwork. :-/
* How does the scope feel? (Room to expand? Just right? Pretty ambitious?)
:* Good functional scope but technical scope has expanded (involving foundational changes to IRA driven by well recognized issues).
:* Will need to make up ground to be in reasonable shape for February meeting.
* If you had to reduce scope, what would you drop?
:* Hard to say until after the groundwork solidifies the picture. Revisit at PC meeting.
* Have the promised resources manifested?
:* Yes-ish. Support offered; hope to leverage it once groundwork solidifies.
* What tasks would benefit from additional expertise?
:* FHIRcast mechanics will need discussion with Isaac etc, but that's already planned.
:* Implementation patterns will benefit from vetting by potential implementers. Andrei and Marc have already offered to review/recruit
* What implementers are engaged for each actor? Record how many.
:* Need to complete groundwork and framing to be able to meaningfully engage implementers.
* Was the profile where it needed to be at the start of the Kickoff meeting (See "Kickoff Meeting" above), if not what was the gap
:* No.
:* Branch of IRA was initiated and some edits started, but...
:* Un-forecasted Technical and Practical Issues emerged (see above) which precluded much draft profile text
:* COVID/health issues/bandwidth limits precluded proper mapping/documenting of the issues/candidate resolutions
:* Groundwork investigations with "owners" of underlying FHIRcast was not completed
* Was the profile where it needed to be at the end of the Kickoff meeting, if not what was the gap
:* No. See preceding question.
* How many tcons would you like between now and the PC Prep Meeting?
:* At least three. Mid-December, Early January, Mid-January
::* Dec 21 10am Central 2 hours
::* Jan 7 10am Central 2 hours
::* Jan 20 10am Central 2 hours
:* Will schedule FHIRcast discussions separately.


=='''Maintenance items for the meeting'''==
=='''Maintenance items for the meeting'''==
Line 116: Line 187:


<b>(4) Identify Next Top 10</b>.
<b>(4) Identify Next Top 10</b>.
Potential set of new Top-10 addressing SWF.b:
CP-RAD-224 Add Document References to MWL
CP-RAD-299 Effect of Rejected Instances on Availability Notification behavior
CP-RAD-304 Add Multiple Identity Resolution Option to SWF.b
CP-RAD-353 Update RAD-28 to send non-SR-based ORU
CP-RAD-354 Add Billing Transaction
CP-RAD-422 SWF.b Case 10 clarification
CP-RAD-445 Add note to Appendix A tables
CP-RAD-489 Clarify CT/MR Localizer image requirements
CP-RAD-506 Group Case clarification
CP-RAD-508 OBR Consistency for Modality
CP-RAD-509 Study Date/Time mapping from HL7 Order messages
CP-RAD-514 Vol 2x: Procedure Code Sequence clarifications
CP-RAD-515 Vol 2x:  Fully integrate SWF.b into Appendix D
CP-RAD-538 Clarify population of Institution attributes in Enterprise Identity Option
CP-RAD-558 SWF.b – Clarify Group Case Mapping in Appendix A


<b>(5) Assigned CPs ready for discussion:</b>.
<b>(5) Assigned CPs ready for discussion:</b>.

Latest revision as of 09:07, 14 November 2026

Participants

  • Wim Corbijn van Willenswaard | Philips | RadTech Co-chair
  • Andrei Leontiev | Visage Imaging | RadTech Co-chair
  • Mike Bohl | Dose Registry | RadPlan Co-chair
  • Kevin O'Donnall | Canon Medical Research | Domain Representative to IHE International Board
  • Jonathan Whitby | Canon Medical Research
  • Antje Schroeder | Siemens Healthineers
  • Marc Kämmerer | VISUS
  • Steve Nichols | GE
  • Charles Parisot | InteropEhealth*
  • David Kwan | Insygnia Consulting*
  • Harald Zachmann | Merge/Merative*
  • Bas van den Heuvel | Philips*
  • Yasunari "Salt" Shiokawa | JAHIS*
  • Griffin Fairchok | Epic*
  • Ana Kostadinovska | Philips*
  • Teri Sippel | Johns Hopkins
  • Khaled Younis | MedAiConsult LLC*
  • Lori Stolz*
  • Christopher Melo*
  • Rob Ferre*
  • Allan B.*
  • Darie Espinosa Garcia

Non-voting

  • Jason Nagels | IHE Radiology Technical Project Manager
  • Alia Khan | RSNA | Secretary
  • Chris Carr | RSNA | Secretary


(*) = Remote attendance


All times are U.S. Central Time.

Monday, November 09, 2026

  • A1: 8:45am-9:00am Administrative Time
  • S1a: 9:00am-9:45am: Clinical Consult on EBIW with ACEP (Steve) [0.75 hr]
  • S1b: 9:45am-11:00am: IRA Content [1.25 hr]
  • S2: 11:15am-12:45pm: IRA Content [2.75 hr]
  • S3: 1:30pm-3:00pm: Maintenance: Final Review and approval CP-RAD-575[1.5 hr]
    • Reviewed and approved for ballot 2026C
  • A2: 3:00pm-3:30pm: ISO21860 (The Clinical Imaging Reference Standards Portfolio)
  • S4a: 3:30pm-4:00pm: Maintenance: Imaging Access Initiative (Chris Carr) [2.0 hr]
  • S4b: 4:15pm-5:00pm: Maintenance [2.75 hr]
    • See List of Maintenance topics at the bottom of the agenda

Tuesday, November 10, 2026

Wednesday, November 11, 2026

  • A1: 8:45am-9:00am Administrative Time
  • S1: 9:00am-11:00am: AI Service Capabilities[5.5 hr]
  • S2: 11:15am-12:45pm: Maintenance [7.5 hr]
    • CP-RAD-576 Clarification of parameter capitalization in WADO-RS - Assigned
    • CP-RAD-577 Update Examples of Messages for RAD-107 - Completed and approved for ballot 2026C
    • CP-RAD-578 Update Section Identifiers in MADO
    • CP-RAD-565 Radiology Option for Consistent Time - Completed and approved for ballot 2026C
  • S3: 1:30pm-3:30pm: AI Service Capabilities [7.5 hr]
  • S4: 3:45pm-5:00pm: Maintenance[8.75 h]
    • CP-RAD-436 Fix inconsistencies in IOCM actor / transaction and grouping requirements - detailed review.
    • See List of Maintenance topics at the bottom of the agenda
  • Group Dinner (Antico Posto) @ 6:00pm

Thursday, November 12, 2026

  • A1: 8:45am-9:00am Administrative Time
  • S1: 9:00am-11:00am: AI Service Capabilities[9.5 hr]
  • S2: 11:15am-12:45pm: Maintenance [10.25h]
  • S3: 1:30pm-3:30pm: AI Service Capabilities - Checkpoint Assessment [11.5 hr]
  • S4: 3:45pm-5:00pm: Maintenance[7.5 h]
    • Reviewed and updated the Assessment of TI profile and plan for Final Text and Retire/Deprecate
    • DIFF is ready for FT approval - need to schedule PC vote to approve

Friday, November 13, 2026

  • A1: 8:45am-9:00am Administrative Time
  • S1: 9:00am-10:30am Maintenance [11.75 hr]
    • Completed CP-RAD-578 to go to Ballot 2026C
    • Discussed split of POCUS from "core" EBIW. As a result, we decided that the right way to do that would be to refactor the EBIW supplement to introduce 3 profiles making the Lightweight Modality and POCUS options into their own profiles referring to transactions in the "core" EBIW profile. Also need to determine if references from RAD-132 transaction in EBIW profile to RAD-128 in RD profile should be reversed (in case we are not expecting the RD to become FT soon)
    • Discussed assignment of next Top 10 - agreed that addressing the SWF.b CPs will be a good goal for this cycle. Andrei and Jason will review which of 15 currently assigned CPs worth to move forward and which ones are no longer valid and should be cancelled.
  • S2: 10:45am-11:45pm IRA Content including checkpoint assessment [8.5]

Profile Name: IRA Finding Content

  • Describe gaps in Use Case coverage
  • With the "Pattern A/B/C" work, a compelling range of use cases feel covered.
  • Review ALL "uncertainty points" in the evaluation. Is there a resolution plan for each?
  • Reviewed. All were discussed. Some were resolved. Some have plan for further evolution.
  • Do the effort points in the evaluation still seem right?
  • No, will likely need to do some re-writing of existing transactions, will likely need to introduce some mechanisms for "intention channels"
  • Did the Breakdown of Tasks accurately reflect the work? What extra tasks arose?
  • See previous question
  • BoD was a good set of topics which were all discussed, but there are some deeper issues being prepped and hopefully resolved.
  • Describe unresolved technical issues/tasks
  • Posting references to FHIRcast
  • Hosting transient instances (some of which might migrate to persistent) on a FHIR Server associated with the hub rather than inside the hub
  • List/Channels with an intention code to telegraph/coordinate collaboration behaviors (sender and receivers)
  • Review Marc's proposals for MQTT-based PubSub
  • Describe potential practical issues
  • Will need to coordinate with Isaac/Bas/FHIRcast folks about our proposals.
  • Once concepts are properly prepared and vetted with a couple of TC folks, will schedule calls with Isaac
  • Then will come back to TC for discussion/confirmation/evolution
  • Review the open issue list. Does it feel complete
  • Not yet. Many good open issues are captured in discussion text but are not yet collated into a properly worded list.
  • Which open issues feel most risky; what other risks exist?
  • See unresolved Tech Issues and Practical Issues above
  • Need for schedule/technical coordination with other groups (FHIRcast)
  • How is the work fitting in the allocated bandwidth? (Time to spare? Just right? Things were left undone?)
  • Time to spare but it's because there are issues needing groundwork. :-/
  • How does the scope feel? (Room to expand? Just right? Pretty ambitious?)
  • Good functional scope but technical scope has expanded (involving foundational changes to IRA driven by well recognized issues).
  • Will need to make up ground to be in reasonable shape for February meeting.
  • If you had to reduce scope, what would you drop?
  • Hard to say until after the groundwork solidifies the picture. Revisit at PC meeting.
  • Have the promised resources manifested?
  • Yes-ish. Support offered; hope to leverage it once groundwork solidifies.
  • What tasks would benefit from additional expertise?
  • FHIRcast mechanics will need discussion with Isaac etc, but that's already planned.
  • Implementation patterns will benefit from vetting by potential implementers. Andrei and Marc have already offered to review/recruit
  • What implementers are engaged for each actor? Record how many.
  • Need to complete groundwork and framing to be able to meaningfully engage implementers.
  • Was the profile where it needed to be at the start of the Kickoff meeting (See "Kickoff Meeting" above), if not what was the gap
  • No.
  • Branch of IRA was initiated and some edits started, but...
  • Un-forecasted Technical and Practical Issues emerged (see above) which precluded much draft profile text
  • COVID/health issues/bandwidth limits precluded proper mapping/documenting of the issues/candidate resolutions
  • Groundwork investigations with "owners" of underlying FHIRcast was not completed
  • Was the profile where it needed to be at the end of the Kickoff meeting, if not what was the gap
  • No. See preceding question.
  • How many tcons would you like between now and the PC Prep Meeting?
  • At least three. Mid-December, Early January, Mid-January
  • Dec 21 10am Central 2 hours
  • Jan 7 10am Central 2 hours
  • Jan 20 10am Central 2 hours
  • Will schedule FHIRcast discussions separately.

Maintenance items for the meeting

Note: Strikethrough font marks topics completed as the week proceeds

RAD Tech Monthly CP Processing

--> See RAD CP Tracking Spreadsheet

(1) Process Newly Submitted CPs:

Link to Submitted folder on Google Drive

(2) Process Top Ten CPs

  • CP-RAD-436 Fix inconsistencies in IOCM actor / transaction and grouping requirements (Jason)
  • CP-RAD-474 Extensions to RAD-106 for IMR (Kinson)
  • CP-RAD-500 RAD-137 clarify request/response (Kevin)

(3) Profile Promotion Retirement 2027 planning: Link to the Profile management tracker

(4) Identify Next Top 10. Potential set of new Top-10 addressing SWF.b: CP-RAD-224 Add Document References to MWL CP-RAD-299 Effect of Rejected Instances on Availability Notification behavior CP-RAD-304 Add Multiple Identity Resolution Option to SWF.b CP-RAD-353 Update RAD-28 to send non-SR-based ORU CP-RAD-354 Add Billing Transaction CP-RAD-422 SWF.b Case 10 clarification CP-RAD-445 Add note to Appendix A tables CP-RAD-489 Clarify CT/MR Localizer image requirements CP-RAD-506 Group Case clarification CP-RAD-508 OBR Consistency for Modality CP-RAD-509 Study Date/Time mapping from HL7 Order messages CP-RAD-514 Vol 2x: Procedure Code Sequence clarifications CP-RAD-515 Vol 2x: Fully integrate SWF.b into Appendix D CP-RAD-538 Clarify population of Institution attributes in Enterprise Identity Option CP-RAD-558 SWF.b – Clarify Group Case Mapping in Appendix A

(5) Assigned CPs ready for discussion:.

link to Assigned folder on Google Drive

  • CP-RAD-565 Radiology Option for Consistent Time