Rad Tech Minutes 2026-02-02-06: Difference between revisions
Jump to navigation
Jump to search
Jdulkowski1 (talk | contribs) |
No edit summary |
||
| Line 34: | Line 34: | ||
:*Nick Hermans | :*Nick Hermans | ||
:*Ana Kostadinovska | :*Ana Kostadinovska | ||
Profile Name: MADO | |||
* Did we line-by-line the entire document | |||
* How ready is it to go out for TI: Completely, Almost, Soonish, Hmmm | |||
* How did the work fit in the allocated bandwidth? (Time to spare? Just right? Things were left undone?) | |||
* Review the evaluation. Which complexity/uncertainty/effort points missed the mark? | |||
* Or alternatively, estimate how many points you went over and assign the overage effort/complexity/uncertainty to the appropriate points. | |||
* Are all the open issues closed? | |||
* What significant debates in TI-prep were not anticipated in the Kickoff or PC-Prep | |||
* Did the Breakdown of Tasks accurately reflect the work? What extra tasks arose? | |||
* What residual risks are worth noting | |||
* Does it feel we've met all the use cases | |||
* Did the promised resources manifest | |||
* What vendors are engaged (for each actor) | |||
* Who should specifically be targeted for TI notification (implementors & advocates) | |||
* When will we have sample data/objects | |||
* Was the profile where it needed to be at the start of the TI meeting, if not what was the gap | |||
* Was the profile where it needed to be at the end of the TI meeting, if not what was the gap | |||
* Do you need any tcons between now and TI Publication | |||
Profile Name: IDR | |||
* 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 ALL "uncertainty points" in the evaluation. Are all now resolved? | |||
* Review ALL "complexity points" in the evaluation. Did each get appropriate text coverage/resolution? | |||
* Review the "effort points" in the evaluation. Still seems right? Need more? | |||
* 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 | |||
:* Transactions. | |||
* 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 | |||
:* Report Creators | |||
:* Academic Rads, Private Practice Rads | |||
* 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 | |||
:* Structurally complete-ish. Enough there to work on, but didn't circulate ahead of the meeting, Quite a few TODOs | |||
* 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 | |||
:* Three. We'll see how it goes. | |||
* Do you need any tcons before TI Prep Meeting | |||
:* Schedule one. Can cancel. | |||
=='''Action Items'''== | =='''Action Items'''== | ||
1. Include Retrospective discussion at TI meeting (April). Invite Aaron Goldmuntz to discussion. | 1. Include Retrospective discussion at TI meeting (April). Invite Aaron Goldmuntz to discussion. | ||
Revision as of 00:07, 5 February 2026
Quick Links
- Daily Teams meeting details
- Meeting Link
- Meeting ID: 210 806 582 303 2
- Meeting Passcode: kC9a673f
- Minutes for this meeting are here: https://wiki.ihe.net/index.php/Rad_Tech_Minutes_2026-02-02-06
- Working folder for IHE RAD Tech 2026 cycle: https://drive.google.com/drive/folders/1XTCoCXrIUzlH0zg8zLFJcCqMoIoEWMvq?usp=sharing
- Daily Teams meeting details
Participants
In Person
- Kevin O'Donnell
- Jason Nagels (TPM)
- Steve Nichols
- Wim Corbijn
- Yasunari "Salt" Shiokawa
- Harald Zachmann
- Antje Schroeder
- Jamie Dulkowski
- Chris Carr
Remote
- Charles Parisot
- Andrei Leontiev
- Andries Hamster
- David Kwan
- Griffin Fairchok
- Kinson Ho
- Mike Bohl
- Rick Busbridge
- Bas van den Heuvel
- Nick Hermans
- Ana Kostadinovska
Profile Name: MADO
- Did we line-by-line the entire document
- How ready is it to go out for TI: Completely, Almost, Soonish, Hmmm
- How did the work fit in the allocated bandwidth? (Time to spare? Just right? Things were left undone?)
- Review the evaluation. Which complexity/uncertainty/effort points missed the mark?
- Or alternatively, estimate how many points you went over and assign the overage effort/complexity/uncertainty to the appropriate points.
- Are all the open issues closed?
- What significant debates in TI-prep were not anticipated in the Kickoff or PC-Prep
- Did the Breakdown of Tasks accurately reflect the work? What extra tasks arose?
- What residual risks are worth noting
- Does it feel we've met all the use cases
- Did the promised resources manifest
- What vendors are engaged (for each actor)
- Who should specifically be targeted for TI notification (implementors & advocates)
- When will we have sample data/objects
- Was the profile where it needed to be at the start of the TI meeting, if not what was the gap
- Was the profile where it needed to be at the end of the TI meeting, if not what was the gap
- Do you need any tcons between now and TI Publication
Profile Name: IDR
- 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 ALL "uncertainty points" in the evaluation. Are all now resolved?
- Review ALL "complexity points" in the evaluation. Did each get appropriate text coverage/resolution?
- Review the "effort points" in the evaluation. Still seems right? Need more?
- 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
- Transactions.
- 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
- Report Creators
- Academic Rads, Private Practice Rads
- 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
- Structurally complete-ish. Enough there to work on, but didn't circulate ahead of the meeting, Quite a few TODOs
- 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
- Three. We'll see how it goes.
- Do you need any tcons before TI Prep Meeting
- Schedule one. Can cancel.
Action Items
1. Include Retrospective discussion at TI meeting (April). Invite Aaron Goldmuntz to discussion.