Difference between revisions of "Rad Tech Agenda 2024-02-05-09"

From IHE Wiki
Jump to navigation Jump to search
Line 111: Line 111:
 
Putting these in the Agenda since there is no minutes page yet
 
Putting these in the Agenda since there is no minutes page yet
  
−
Profile Name: Reject Analysis
+
Profile Name: '''Reject Analysis'''
 
* Did we line-by-line the entire document
 
* Did we line-by-line the entire document
 
Yes. (although some edits to be completed)  
 
Yes. (although some edits to be completed)  

Revision as of 22:28, 8 February 2024

Quick Links

Join Zoom Meeting https://rsna-org.zoom.us/j/88293289078?pwd=EN6TpivcdbsTxW5s1aJBe3fu5pAk2u.1

Meeting ID: 882 9328 9078 Passcode: 810631

Monday, February 5, 2024

Tuesday, February 6, 2024

Wednesday, February 7, 2024

  • A1: 8:45am-9:00am Administrative Time
  • S1: 9:00am-10:30am: Imaging Diagnostic Report (IDR)
  • S2: 10:45am-12:15pm: Maintenance
  • A2: 1:00pm-1:30pm: Reject Analysis (RAM)
  • S3: 1:30pm-2:45pm: Imaging Diagnostic Report (IDR)
  • C1: 3:00pm-4:00pm: Clinical Consult
  • S5: 4:00pm-4:45pm: Imaging Diagnostic Report (IDR)
  • A3: 4:45pm-5:00pm: Administrative Time

Thursday, February 8, 2024

  • A1: 8:45am-9:00am Administrative Time
  • S1: 9:00am-10:30am: Imaging Diagnostic Report (IDR)
  • S2: 10:45am-12:15pm: Maintenance-
    • XCA CP on XCA-I titled: WADO-RS as an optional transaction between Initiating GW and Responding GW Actors of XCA-I
  • A2: 1:00pm-1:30pm: Administrative Time
  • S3: 1:30pm-3:00pm: Reject Analysis (RAM)
  • S4: 3:15-4:45pm Imaging Diagnostic Report (IDR)
  • A3: 4:45pm-5:00pm: Administrative Time

Friday, February 9, 2024

  • A1: 8:30am-9:00am Administrative Time - 2024-25 Cycle planning
  • S1: 9:00am-10:30am Checkpoint assessments; Tcon scheduling
  • S2: 10:45am-12:15pm Maintenance
  • A2: 12:30pm - Open time

Maintenance topics for the week

Link to RAD CP Tracking sheet

Link to RAD TF Maintenance folder in google drive

Maintenance topics:

  • Review / update Assessment of RAD profiles for promotion or deprecation
    • Review Antje's evaluation forms in this folder
      • MAWF deprecation evaluation
      • CXCAD deprecation evaluation
      • SMI deprecation evaluation
      • XCA CP on XCA-I titled: WADO-RS as an optional transaction between Initiating GW and Responding GW Actors of XCA-I
  • CP-related discussion topics for committee deliberation
    • CP-RAD-513-02 SWF.b: Clarify Intermittently Modality behavior in RAD-10 Storage Commitment (Steve, Sean) - Reworked as discussed. @Sean let me know if this is OK.
    • CP-RAD-519 BIR updates for Final Text (Steve) Reduced content items discussed during call in June. Added stuff we talked about to the rationale. Did I miss anything?
    • CP-RAD-517 NMI Cardiac Option - update to include support of PS (Steve) - Kevin asked that I elaborate on the option descriptions. I expanded them a bit, but they're not very wordy . Let me know your thoughts
  • Other CPs ready for committee review:
    • CP-RAD-463 - Add RDSR Display option in REM (Kevin)
    • CP-RAD-479-01 - RAD-60 - update reason codes reference to DICOM (Lynn)
    • CP-RAD-496-01 - Missing arrow in in SWF.b actor/transaction diagram (Lynn)
    • CP-RAD-478-01 - Remove out-of-date references to DICOM and supplement (Lynn)
    • CP-RAD-515-01 - Vol 2x: Fully integrate SWF.b into Appendix D (Lynn) -- cmte input needed
    • CP-RAD-483-00 - Deprecate PWF transactions (Lynn) -- get go-ahead from RAD Tech to do this
    • CP-RAD-305-02 - Revise profile dependencies (grouping) in Vol 1) (Lynn) -- cmte input needed; do it, or kill it...
    • CP-RAD-436-02 - Fix inconsistencies in IOCM actor / transaction and grouping requirements (Lynn) -- cmte input needed
    • CP-RAD-410-03 - XCA-I is out of date for Async (Lynn)
    • CP-RAD-491-01 - Code Mapping WP update (Lynn)
  • Review / update Top Ten CP list
    • Finalize content and timing of next CP ballot

Checkpoints

Putting these in the Agenda since there is no minutes page yet

Profile Name: Reject Analysis

  • Did we line-by-line the entire document

Yes. (although some edits to be completed)

  • How ready is it to go out for PC: Completely, Almost, Soonish, Hmmm

Almost~Soon

  • Which open issues are risky, and why

Aren't really risky. Need some modality quality code feedback.

  • Are all open issues phrased to solicit the needed information to close them?

Yes.

  • Which use cases need more input

Might get comments on analysis, but seems OK.

  • 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
  • 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: Imaging Diagnostic Report

  • 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
  • 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
Retrieved from "http://wiki.ihe.net/index.php?title=Rad_Tech_Agenda_2024-02-05-09&oldid=131926"