Difference between revisions of "Rad Tech Agenda 2023-02-06-10"

From IHE Wiki
Jump to navigation Jump to search
Line 99: Line 99:
 
:*S2: 10:45am-11:45: Maintenance: Preparing the new Ballot 2023A [4hr]
 
:*S2: 10:45am-11:45: Maintenance: Preparing the new Ballot 2023A [4hr]
 
:*S3: 12:00-2:00pm: Realtime Bidirectional Communication for Interactive Multimedia Reporting (RBC-IMR)[17hr]
 
:*S3: 12:00-2:00pm: Realtime Bidirectional Communication for Interactive Multimedia Reporting (RBC-IMR)[17hr]
 +
 +
Draft CP ballot timeline -
 +
 +
* Ballot open announcement -
 +
* Ballot close; votes/comments due -
 +
* Ballot resolution t-conn -
 +
 +
Draft Public Commentpublication timeline:
 +
 +
* Submit to Mary -
 +
* Public Comment Start -
 +
* Public Comment End -
 +
* TI publication F2F - April 34-28
 +
  
 
===Post PC-Prep Checkpoint: POWR===
 
===Post PC-Prep Checkpoint: POWR===

Revision as of 10:15, 10 February 2023

Reference Documents

Integrated Reporting Applications
Reporting Worklist Prioritization

All times are US Central Time.

Monday, February 06, 2023

  • A1: 8:45am-9:00am Administrative Time
  • S1: 9:00am-10:30am: Reporting Worklist Prioritization (RWP) [1.5hr]
  • S2: 10:45am-12:15pm: Maintenance [1.5hr]
    • Link to RAD CP Tracking sheet
    • Link to Assessment of RAD TI Supplements
    • Top Ten:
      • CP-RAD-257 Clearly add Admitting Diagnosis to SWF for REM and TCE
      • CP-RAD-293 Extended CT Dose Reporting (SSDE and Dose Check Logs)
      • CP-RAD-349 Add close and logout to IID
      • CP-RAD-364 Clarify IID
      • CP-RAD-423 Add specificity to IOCM
      • CP-RAD-475 Extensions to RAD-107 for IMR
      • CP-RAD-486 Update RAD-108 Message Semantics
      • CP-RAD-501 WIA – RAD-129 fix in Expected Actions
    • Other active CPs:
    • CP-RAD-460-LB - XCA-I Clarify IIG behavior in the local community
      • -- Finalize the CP after two ballots
    • CP-RAD-305-02 - Revise profile dependencies (grouping) in Vol 1)
      • -- cmte input needed* CP-RAD-347-01 - XDS-I Vol 1 clean-up
    • CP-RAD-343-01 - Consistency in specification of PID segment & references to MPI
      • -- a few points for cmte discussion
    • CP-RAD-368-01 - Update/Remove MIMA Referenced in Vol 1 TF (editorial)
      • -- ready for cmte review; could be ready for ballot
    • CP-RAD-436-02 - Fix inconsistencies in IOCM actor / transaction and grouping requirements
      • -- cmte input needed
    • CP-RAD-410-03 - XCA-I is out of date for Async
    • CP-RAD-492-01 - Update SNM3 and SRT codes in Vol 2
    • CP-RAD-491-01 - Code Mapping WP update
    • CP-RAD-490-01 - Update Vol 1x to remove retired transport for Submit Dose Information [RAD-63]
  • S3: 1:15pm-4:15pm: Realtime Bidirectional Communication for Interactive Multimedia Reporting (RBC-IMR) [3hr]
    • 2:00pm-3:00pm: ITI Committee - Github Governance call [for those who are interested]
  • S4: 4:15pm-5:00pm: Editorial Session (as needed)

Tuesday, February 07, 2022

  • A1: 8:45am-9:00am Administrative Time
  • S1: 9:00am-10:30am: Reporting Worklist Prioritization (RWP)[3hr]
  • S2: 10:45am-12:45pm: Realtime Bidirectional Communication for Interactive Multimedia Reporting (RBC-IMR) [5hr]
  • A2: 1:15pm-1:45pm: Administrative Time
    • Radiology at European Connect-a-thon [Lynn]
  • S3: 1:45pm-3:45pm: Realtime Bidirectional Communication for Interactive Multimedia Reporting (RBC-IMR)[7hr]
  • S4: 4:00-5:00pm: Editorial Session (as needed)
  • Dinner at 6:30pm @Wildfire - 232 Oak Brook Center

Wednesday, February 8, 2022

  • A1: 8:45am-9:00am Administrative Time
  • S1: 9:00am-10:30am: Reporting Worklist Prioritization (RWP)[4.5hr]
  • S2: 10:45am-12:45pm: Realtime Bidirectional Communication for Interactive Multimedia Reporting (RBC-IMR)[9hr]
  • A2: 1:15pm-1:45pm: Administrative Time
  • S3: 1:45pm-3:45pm: Realtime Bidirectional Communication for Interactive Multimedia Reporting (RBC-IMR)[11hr]
  • S4: 4:00-5:00pm: Editorial Session (as needed)

Thursday, February 9, 2022

  • A1: 8:45am-9:00am Administrative Time
  • S1: 9:00am-10:30am: Realtime Bidirectional Communication for Interactive Multimedia Reporting (RBC-IMR)[13.5hr]
  • S2: 10:45am-12:15pm: Maintenance [3hr]
  • S3: 1:15pm-4:15pm: Reporting Worklist Prioritization (RWP) Checklist [6.5hr]
  • S4: 4:15-5:00pm Editorial Session (as needed)

Friday, February 10, 2022

  • A1: 8:30am-9:00am Administrative Time
  • S1: 9:00am-10:30am: Realtime Bidirectional Communication for Interactive Multimedia Reporting (RBC-IMR)[15hr]
  • S2: 10:45am-11:45: Maintenance: Preparing the new Ballot 2023A [4hr]
  • S3: 12:00-2:00pm: Realtime Bidirectional Communication for Interactive Multimedia Reporting (RBC-IMR)[17hr]

Draft CP ballot timeline -

  • Ballot open announcement -
  • Ballot close; votes/comments due -
  • Ballot resolution t-conn -

Draft Public Commentpublication timeline:

  • Submit to Mary -
  • Public Comment Start -
  • Public Comment End -
  • TI publication F2F - April 34-28


Post PC-Prep Checkpoint: POWR

  • Did we line-by-line the entire document

Basically, yes. (there will be new text for a number of edits)

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

Almost/Soonish - a week to complete edits as discussed.

  • Which open issues are risky, and why

None

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

Yes

  • Which use cases need more input

None

  • Which issues from the Kickoff Closing Assessment are still unresolved
  • What significant debates in PC-prep were not anticipated in the Kickoff

Didn't really have any big debates

  • 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?)

Seems right

  • How is the work fitting in the allocated bandwidth? (Time to spare? Just right? Things were left undone?)

Seems right

  • 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

Yes. Got clinical input. Still need to track down administrative input during PC

  • What vendors are engaged (for each actor)
  • When will we have sample data/objects

Won't really have sample objects. Could mock up some OBX examples.

  • 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

Basically. Could have been a bit more complete (OBX details and Adding Prioritizer Actor)

  • Was the profile where it needed to be at the end of the PC meeting, if not what was the gap

Basically. Would have been nice to have more of the discussed edits completed, but that would have been more night work

  • How many tcons would you like between now and PC Publication

Maybe 1

  • Do you need any tcons before TI Prep Meeting

Maybe 1 if any tricky comments are submitted

Post PC-Prep Checkpoint: RBC-IM

  • 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