Rad Tech Minutes 2026-04-20-24: Difference between revisions

From IHE Wiki
Jump to navigation Jump to search
← Older editNewer edit →
Charles (talk | contribs)
517 edits
Charles (talk | contribs)
517 edits
Line 94: Line 94:
:* ''The TI version of MADO has been produced in two steps.  The TI version released mid-March included all volumes, but only the DICOM KOS Based imaging manifest specification.  At this meeting the plan was to complete the comment resolution and performing the line by line review of the three missing sections related to the FHIR based Manifest (6.X.3), the MHD envelope (6.X.4) and the mapping of FHIR manifest format into the KOS Manifest format (6.X.5)."
:* ''The TI version of MADO has been produced in two steps.  The TI version released mid-March included all volumes, but only the DICOM KOS Based imaging manifest specification.  At this meeting the plan was to complete the comment resolution and performing the line by line review of the three missing sections related to the FHIR based Manifest (6.X.3), the MHD envelope (6.X.4) and the mapping of FHIR manifest format into the KOS Manifest format (6.X.5)."
* How ready is it to go out for TI: Completely, Almost, Soonish, Hmmm
* How ready is it to go out for TI: Completely, Almost, Soonish, Hmmm
:*''Soonish.  All major comments are close to have been resolved on the FHIR Manifest IG, but the final line by line review of FHIR envelope has only been covered at 50% and the Mapping needs to be completely reviewed.''  
:*''Soonish.  All major comments have been resolved on the FHIR Manifest IG (60% of the three sections), but the final line by line review of FHIR envelope (20% of the three sections) has only been covered at 50% and the Mapping (20% of the three sections) needs to be completely reviewed.''
* How did the work fit in the allocated bandwidth? (Time to spare? Just right? Things were left undone?)
* How did the work fit in the allocated bandwidth? (Time to spare? Just right? Things were left undone?)
:*''bandwidth was not sufficient, not quite sufficient to secure good resolution''
:*''bandwidth was not sufficient, not quite sufficient to secure good resolution''

Revision as of 22:06, 23 April 2026

Quick Links

Participants

In Person

  • Andrei Leontiev
  • Wim Corbijn
  • Mike Bohl
  • Brad Genereaux
  • Kevin O'Donnell
  • Steve Nichols
  • Antje Schroeder
  • Alia Khan
  • Jamie Dulkowski
  • Chris Carr

Remote

  • Jason Nagels (TPM)
  • Charles Parisot
  • Yasunari "Salt" Shiokawa
  • Harald Zachmann
  • David Kwan
  • Griffin Fairchok
  • Bas van den Heuvel
  • Ana Kostadinovska


All times are U.S. Central Time.

Monday, April 20, 2026

  • Wim (in future meetings) will tally topics we spend significant time on (to compare to assessments)
  • A1: 8:45am-9:00am Administrative Time
  • S1: 9:00am-11:00am: Manifest-based Access to DICOM Objects (MADO) [2 hr]
  • S2: 11:15am-12:45pm: Imaging Diagnostic Report (IDR) - Phase 2 [1.5 hr]
  • S3: 1:30pm-3:30pm: Imaging Diagnostic Report (IDR) - Phase 2 [3.5 hr]
  • S4: 3:45pm-5:00pm: Maintenance [1.25 hr]
    • Explore idea of formalizing the specification conventions for SR templates probably in conjunction with CP-RAD-562 Move DICOM Usage Conventions
    • See List of Maintenance topics at the bottom of the agenda

Tuesday, April 21, 2026

  • A1: 8:45am-9:00am Administrative Time
  • S1: 9:00am-11:00am: Imaging Diagnostic Report (IDR) - Phase 2 [5.5 hr]
  • S2: 11:15am-12:45pm: Manifest-based Access to DICOM Objects (MADO) [3.5 hr]
  • S3: 1:30pm-3:30pm: Manifest-based Access to DICOM Objects (MADO) [5.5 hr]
  • S4: 3:45pm-5.00pm: Maintenance [2.5 hr]
    • See List of Maintenance topics at the bottom of the agenda
  • Group Dinner @ 6:00pm

Wednesday, April 22, 2026

  • A1: 8:45am-9:00am Administrative Time
  • S1: 9:00am-11:00am: Imaging Diagnostic Report (IDR) - Phase 2 [7.5 hr]
  • S2: 11:15am-12:45pm: Manifest-based Access to DICOM Objects (MADO)[7 hr]
  • S3: 1:30pm-3:30pm: Imaging Diagnostic Report (IDR) - Phase 2 [9.5 hr]
    • 1:30pm-2:30:pm: Clinical Consult Hour
  • S5: 3:45pm-5:00pm: Maintenance [3.75 h]
    • See List of Maintenance topics at the bottom of the agenda

Thursday, April 23, 2026

  • A1: 8:45am-9:00am Administrative Time
  • S1: 9:00am-10:30am: Manifest-based Access to DICOM Objects (MADO) [8.5 hr]
  • S2: 10:45am-12:45pm: Imaging Diagnostic Report (IDR) - Phase 2 [11.5 hr]
  • S3: 1:30pm-3:30pm: Imaging Diagnostic Report (IDR) - Phase 2 [13.5 hr]
  • S4: 3:45-5:00pm Maintenance [5 hr]
    • See List of Maintenance topics at the bottom of the agenda

Friday, April 24, 2026

Profile Name: MADO

  • Did we line-by-line the entire document
  • The TI version of MADO has been produced in two steps. The TI version released mid-March included all volumes, but only the DICOM KOS Based imaging manifest specification. At this meeting the plan was to complete the comment resolution and performing the line by line review of the three missing sections related to the FHIR based Manifest (6.X.3), the MHD envelope (6.X.4) and the mapping of FHIR manifest format into the KOS Manifest format (6.X.5)."
  • How ready is it to go out for TI: Completely, Almost, Soonish, Hmmm
  • Soonish. All major comments have been resolved on the FHIR Manifest IG (60% of the three sections), but the final line by line review of FHIR envelope (20% of the three sections) has only been covered at 50% and the Mapping (20% of the three sections) needs to be completely reviewed.
  • How did the work fit in the allocated bandwidth? (Time to spare? Just right? Things were left undone?)
  • bandwidth was not sufficient, not quite sufficient to secure good resolution
  • Review the evaluation. Which complexity/uncertainty/effort points missed the mark?
  • very specific details that were not obvious surfaced. Committee/Commenters reversed earlier agreed position (e.g. one new transaction or adpat existing, shift use case aspects on rendered images, scope induced by combining with existing profiles). Coordination with base stand for allignement was not planned. Underestimated size ofr PC text.
  • Or alternatively, estimate how many points you went over and assign the overage effort/complexity/uncertainty to the appropriate points.
  • most points that went over are mostly none of the major topics identified in the evaluation, but details that appeared unexpected complex issues.
  • Are all the open issues closed?
  • Yes, the three open issues have been closed.
  • What significant debates in TI-prep were not anticipated in the Kickoff or PC-Prep
  • These were: one new transaction or adapt existing, shift use case aspects on rendered images, scope induced by combining with existing profiles, style of use case description, obtaining referenced instances for significant images, design of the profile actors, t-ime zone offset mgt.
  • Did the Breakdown of Tasks accurately reflect the work? What extra tasks arose?
  • It is was a logical functional breakdown. The issues are focussed on specific issues at a lower level.
  • What residual risks are worth noting
  • There does not seem to be any "substance residual risks", but the challenge to complete the TI version is an execution challenge given the large number of comments to finalize, irrespective if they were minor or major. Success requires a consitent engagement from the RAD Tech Committee and the Commenters to bring adequate efficiency to support the comments resolution review/closure and perform the TI line-by-line review in a distributed fashion.
  • Does it feel we've met all the use cases
  • Yes
  • Did the promised resources manifest
  • On the European side in a reasonble way, but a broader membership engagement may be needed.
  • What vendors are engaged (for each actor)
  • Doc Source / Content Creator: Philips, Siemens, GE, Founda, Univ of Leuven/Agfa.
  • Consumers:: Philips, Founda, Univ of Leuven/Agfa.(Merge)
  • Modality: Canon
  • Who should specifically be targeted for TI notification (implementors & advocates)
  • The TI notification has started in a very visible way in Europe through the EHDS initiative/Xt-EHR Project and the organization of a Projectathon end of March, with good participation, including test tools development. However, the timely availability of the MADO TI version by mid-February is critical to support this momentum. A specific effort is needed in the rest of the world. In the USA, the current Federal consultation on image exchange is an important opportunity.
  • When will we have sample data/objects
  • We already have samples available to be used to prepare for the end of March MADO/XC-WADO Projectathon. They are waiting for the TI version to be updated and completely aligned.
  • Was the profile where it needed to be at the start of the TI meeting, if not what was the gap
  • The Comments resolution with a proposal for each comment was available in the Comment Spreadsheet. An update draft of the TI was not.
  • Was the profile where it needed to be at the end of the TI meeting, if not what was the gap
  • The expectation was that the comment resolution would be completed. It is unlikely to be completed. Additional reviews will be neded. And reviews for the TI version needed.
  • Do you need any tcons between now and TI Publication
  • Yes:
    • A complete Comment Resolution Spreadsheet to be completed and applied to create a TI Draft for review on Thursday Feb 12th. At least 5 volunteers should agree to review and flag any resolution (In comment spreadsheet/TI Draft) and identifies what needs further clarification.
    • TI finalization 2 hour T-cons to be scheduled around (1)Tuesday February 17th, (2)Thursday February 19th, (3)Monday February 23rd. Proposed time is 10:00am Central Time (17:00 European time).

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 (Lynn)
  • CP-RAD-464 EBIW MWL Message semantics behavior (Wim)
  • CP-RAD-500 RAD-137 clarify request/response (Kevin)
  • Identify additional Top 10 from the XDS-I.b- and SWF.b-related CPs :
    • CP-RAD-248 Clarify bodyPartExamined in XDS-I Metadata
    • CP-RAD-251 RAD-69 WADO-WS Refactor
    • CP-RAD-252 Request to add C-GET to XDS-I.b
    • CP-RAD-294 Update RAD-55 transaction name to WADO-URI Retrieve
    • CP-RAD-333 Author and creation date metadata
    • CP-RAD-335 XDS-I report update on image availability
    • CP-RAD-336 XDS-I clarify references to prior submissions
    • CP-RAD-402 XDS-I.b Update Async Language and Support AS4
    • CP-RAD-437 New ATNA STX options & updates to XDS-I.b, XCA-I dependencies / mandatory groupings
    • CP-RAD-421 Clarify mimeType for CDA-wrapped text & PDF docs
    • CP-RAD-228 MIMA Query optional when IM/IA grouped with XDS-I Image Document Source
    • CP-RAD-232 Items for clarification in HL7v2.5.1 option
    • CP-RAD-239 Refactor RAD-01 and RAD-12 Transactions with IHE ITI PAM
    • CP-RAD-257 Clearly add Admitting Diagnosis to SWF for REM and TCE
    • CP-RAD-259 Clarify that Scheduled Protocol Code is required
    • CP-RAD-137 IM/IA receives more or less instances than it expects as per MPPS
    • 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-558 SWF.b – Clarify Group Case Mapping in Appendix A
    • CP-RAD-538 Clarify population of Institution attributes in Enterprise Identity Option

(3) Assigned CPs ready for discussion:

link to Assigned folder on Google Drive

  • CP-RAD-305-03 - Revise profile dependencies (grouping) in Vol 1) (Lynn; + input from Philips in Sep 2024) -- cmte input needed
  • CP-RAD-410-03 - XCA-I is out of date for Async (Lynn)
  • CP-RAD-487 - Enterprise Identity Option - Institution mapping context (Andrei)
  • CP-RAD-493-00 - ARI Ambiguity (Andrei)
  • CP-RAD-559 - EBIW – Image Manager mandatory option specification (Jason)
  • CP-RAD-561 - XC-WADO – option doesn’t follow profile template - Assigned (Andrei)
  • CP-RAD-562 - Move DICOM Usage Conventions (Lynn)

(4) Assessment of RAD TI supplements: link to Assessment document on Google Drive

  • Final Text
    • AIR (Kevin)
    • DIFF (Wim)
    • XDR-I (Kinson)
    • IRWF - need advocate
  • Deprecate:
    • CDS-OAT
    • PAWF
    • RWF
    • PWF
    • XRR-WD
  • Retire:
    • FUS
    • PDI Extensions
Retrieved from "http://wiki.ihe.net/index.php?title=Rad_Tech_Minutes_2026-04-20-24&oldid=136116"