Rad Tech Agenda 2023-02-06-10

From IHE Wiki
Jump to navigation Jump to search

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-372 REM-NM
      • CP-RAD-501 WIA – RAD-129 fix in Expected Actions
      • CP-RAD-517 NMI Cardiac Option - update to include support of PS
    • 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:00am Admin - Checkpoint assessments
  • S2: 10:00-12:00: Realtime Bidirectional Communication for Interactive Multimedia Reporting (RBC-IMR)[15.5hr]
  • S3: 12:45am-2:45: Maintenance: Preparing the new Ballot 2023A [5hr]


Draft CP ballot timeline -

  • Ballot open announcement - February 17
  • Ballot close; votes/comments due - March 24
  • Ballot resolution t-conn - Thurs Apr 6 10 am CP ballot resolution

Draft RTC-IMR Public Comment publication timeline:

  • Submit to Mary - Mar 3 ish
  • Public Comment Start - Mar 20 ish
  • Public Comment End - 2nd week of april
  • TI publication F2F - April 24-28

Draft POWR Public Comment publication timeline:

  • Submit to Mary - Feb 24 ish
  • Public Comment Start - Mar 1-3 ish
  • Public Comment End - 1st week of April
  • TI publication F2F - April 24-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

Didn't really have any issues then

  • 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? (Check Kickoff for this finding)

Yes

  • Review ALL "complexity points" in the evaluation. Did each get appropriate text coverage/resolution?

Yes. (Note changed our mind here to add new transaction instead of reuse RAD-13, but not a big issues)

  • Review the "effort points" in the evaluation. Still seems right? Need more?

Seems right

  • 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 about right

  • Did the Breakdown of Tasks accurately reflect the work? What extra tasks arose?

There were a couple discussions (Need to think about it) that were new topics.

  • Looking forward, if you had to reduce scope to hit TI, what would you drop

Basically done.

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

Prioritizer: Canon, Siemens, Visage, GE, Philips Sources - haven't really dug in yet, but mostly we use existing functions.

  • 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

RSNA RIC (Chris), reach out to Nuance and Intelerad and RadAI and

  • 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

No. Good coverage of key transactions and main use case. Got halfway through.

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

Soonish? Not much controversy. Mostly implementing the decisions we reached

  • Which open issues are risky, and why

The SR JSON Issue is slightly risky because if we get drawn in, there could be some complexity in making sure the interoperability is robust.

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

Seems like it. List feels a bit short. Feel free to add questions during finalization.

  • Which use cases need more input

Consider open issue to find examples not covered by our general 5 step

  • Which issues from the Kickoff Closing Assessment are still unresolved
    • Haven't reviewed the FHIR resource mapping for the context and content sharing.
    • Reporting App Catalog (Critical Finding Followup app, Patient History Summary app, Trend Grapher, etc) - add to the open issue we mentioned, then we can confirm if an existing actor works for that and if the existing resources are sufficient)
    • Resolved several issues
    • Spent some time coming up with new stuctures for the new concepts (takes time)
    • Still finding it is big to get review through all the document - size issues
  • What significant debates in PC-prep were not anticipated in the Kickoff
    • Overall transaction structuring and transaction vs actor description split, Actor organization/grouping
    • FHIRcast capabilities (less and less, but still some technology learning)
  • Review ALL "uncertainty points" in the evaluation. Are all now resolved?
    • Mostly, some open
    • Havent looked at the resource mapping for a "posted" finding getting inserted into an actual report.
    • Were probably light on U. Estimated 5.5 for this vs 7 for Prioritization
    • Should have added more for profile structure since it doesn't really match. Also should add more than 2 for new tech like FHIRcast. Learning Curve!
  • Review ALL "complexity points" in the evaluation. Did each get appropriate text coverage/resolution?

STOPPED HERE - RESUME after rest of work done.

  • 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)
    • Would be nice to bridge FHIR CAT vendors into IHE CAT; they appreciate the detail of reporting WF that IHE brings
  • 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_2023-02-06-10&oldid=129601"