Rad Tech Minutes 2023-04-24-28

From IHE Wiki
Jump to navigation Jump to search

Participants

  • Andrei Leontiev
  • Steve Nichols
  • Wim Corbijn
  • Kinson Ho
  • Kevin O'Donnell
  • Antje Schroeder
  • Ben Larson
  • Eric Martin

RSNA Staff: TeRhonda McGee, Jamie Dulkowski

Reference Documents

Integrated Reporting Applications
Reporting Worklist Prioritization

All times are US Central Time.

Monday, April 24, 2023

  • A1: 8:45am-9:00am Administrative Time
  • S1: 9:00am-10:30am: Prioritization of Worklists for Reporting (POWR) [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]

All CPs approved

  • S3: 1:15pm-4:15pm: Integrated Reporting Applications (IRA) [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, April 25, 2023

  • A1: 8:45am-9:00am Administrative Time
  • S1: 9:00am-11:00am: Integrated Reporting Applications (IRA) [5hr]
  • S2: 11:15am-12:45pm: Prioritization of Worklists for Reporting (POWR) [3hr]
  • A2: 1:15pm-1:45pm: Administrative Time
    • Framework Republication Plan [Lynn]
  • S3: 1:45pm-3:45pm: Integrated Reporting Applications (IRA)[7hr]
  • S4: 4:00-5:00pm: Editorial Session (as needed)
  • Dinner at 6:30pm @Wildfire - 232 Oak Brook Center

Wednesday, April 26, 2023

  • A1: 8:45am-9:00am Administrative Time
  • S1: 9:00am-10:30am: Prioritization of Worklists for Reporting (POWR) [4.5hr]
  • S2: 10:45am-12:45pm: Integrated Reporting Applications (IRA) (RBC-IMR)[9hr]
  • A2: 1:15pm-1:45pm: Administrative Time
  • S3: 1:45pm-3:45pm: Integrated Reporting Applications (IRA) (RBC-IMR)[11hr]
  • S4: 4:00-5:00pm: Editorial Session (as needed)

Thursday, April 27, 2022

  • A1: 8:45am-9:00am Administrative Time
  • S1: 9:00am-10:30am: Integrated Reporting Applications (IRA)[13.5hr]
  • S2: 10:45am-12:15pm: Maintenance [3hr]
  • S3: 1:15pm-4:15pm: Prioritization of Worklists for Reporting (POWR) [6.5hr]
  • S4: 4:15-5:00pm Editorial Session (as needed)

Friday, April 28, 2023

TI-Prep Closing Assessments

Prioritization of Worklists for Reporting (POWR)

  • Did we line-by-line the entire document
Oops. Should have finished that in the last hour yesterday.
  • How ready is it to go out for TI: Completely, Almost, Soonish, Hmmm
Almost
  • How did the work fit in the allocated bandwidth? (Time to spare? Just right? Things were left undone?)
Time to spare
  • Review the evaluation. Which complexity/uncertainty/effort points missed the mark?
Basically right. Slightly overestimated the Effort/length, and the Complexity. Uncertainty right.
  • 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?
Yes.
  • What significant debates in TI-prep were not anticipated in the Kickoff or PC-Prep
Triage flagging (OBX-28/HL7 v2.7), Discharge Intent as a driver
  • Did the Breakdown of Tasks accurately reflect the work? What extra tasks arose?
(Review) Pretty much on target
  • What residual risks are worth noting
Nothing specific to this profile. Maybe v2.5+? FHIR-bias for communicating AI outputs (assumption that AIs won't be used until Hospitals have upgraded to FHIR)
  • Does it feel we've met all the use cases
Yes (although would have been nice to cover workflow factors)
  • Did the promised resources manifest
Yes (got input from SMEs)
  • What vendors are engaged (for each actor)
See previous checkpoint
  • Who should specifically be targeted for TI notification (implementers & advocates)
IAIP (Teri is window), RSNA RIC-IHE Cmte, ...
  • When will we have sample data/objects
(Sample HL7 Y1 messages in Sharazone, Lynn will ask Prioritizers what they want and try to prestage)
Not a big barrier. This isn't a content profile and we have the Rad 1,2,3,4,5...
  • Was the profile where it needed to be at the start of the TI meeting, if not what was the gap
Mostly. Could have had proposed resolutions for some more comments in place for review
  • Was the profile where it needed to be at the end of the TI meeting, if not what was the gap
Almost. Still have some TODOs to complete (mostly non-normative), missed line-by-line, especially example.
  • Do you need any tcons between now and TI Publication
Yes, 2 - schedule 2 hrs

Integrated Reporting Applications (IRA)

  • Did we line-by-line the entire document
No, not close
  • How ready is it to go out for TI: Completely, Almost (few more weeks), Soonish (later this summer), Hmmm (TI this year is a risk)
Soonish ... Large portion of the profile are stable. Most discussions are focus on architectural design to handle interruption and resume use case.
Don't hold up POWR to get IRA out.
  • How did the work fit in the allocated bandwidth? (Time to spare? Just right? Things were left undone?)
Over-budget, will need TC commit to keep meeting into June, July
Most time have been concentrated on a few but significant topics. These are important topics to address and the discussions are productive, with the help from the FHIRcast members too. However, the downside is that there are not enough time to review all public comments and review the profile line-by-line.
Collaboration with FHIRcast was efficient and effective; good cross-meeting participation, insightful contributions, timely responses; has benefited both projects. Good example of working with collaborating SDO
  • Review the evaluation. Which complexity/uncertainty/effort points missed the mark?
The interruption and resume use case is not identified in the task breakdown and it has been taken significant amount of time.
The use case was reviewed and discussed during public comment development, but there are subtle details identified that require lots of time to resolve
Effort maybe a touch low, Complexity was low, Uncertainty was Way Low (less than POWR?)
  • Or alternatively, estimate how many points you went over and assign the overage effort/complexity/uncertainty to the appropriate points.
Probably 11 points (2/4/5) for Interruption and Resume; also reliability expectations for our use case compared to FHIRcast intentions (e.g. Select)
Some issues aligning with FHIRcast (empty current)
  • Are all the open issues closed?
Not yet. Pending discussion
  • What significant debates in TI-prep were not anticipated in the Kickoff or PC-Prep
Close to Empty
Interruption and resume use case (selection handling, race conditions, "reliability", performance/timing/sync/asynch, local state saving, Which actors do what, update of non-current context (use case and spec), open (create) vs open (resume)
Actor bundling (Content creator vs optional Select/Update)
(TODO) in future meetings, task someone with tracking "big topics" and sometimes nudging to "move on"
  • Did the Breakdown of Tasks accurately reflect the work? What extra tasks arose?
Interruption and resume use case
Transactions became larger (and were reorganized a bit a couple of times)
Single Large Use Case should have been broken down more to better expose things like suspend resume details and selection expectations. (TODO Surfaced this somewhat during PC but didn't bump up the estimate - should have cut scope and/or added more tcons)
Missed a couple transactions. Didn't put uncertainty on some transactions, but otherwise size was rightish
Should add a Task to cover the weaving of all the transactions (complexity/uncertainty) - driven by the "use case" but an additional task. Sort of the digital view in addition to the user/operational view (Maybe allocate Actor# * Transaction#)
  • What residual risks are worth noting
Tcon time to review line-by-line, which is unfortunately not the most effective
FHIRcast alignment questions, and publication scheduling (FHIR R5 is fine)
  • Does it feel we've met all the use cases
Yes
  • Did the promised resources manifest
Yes. (FHIRcast support, Report Creator implementers were represented by Eric)
HIMSS/SIIM Reporting Group contributed to use case details
  • What vendors are engaged (for each actor)
See previous
  • Who should specifically be targeted for TI notification (implementers & advocates)
FHIRcast Working Group
RSNA Reporting Committee
IAIP Demo
Open Data Model for Radiology
  • When will we have sample data/objects
Already defined in the profile Artifacts tab, AI findings/observations, measurements, imaging selection
  • Was the profile where it needed to be at the start of the TI meeting, if not what was the gap
Yes? Almost all the comments were done or had a proposed resolution, just a few were still open for discussion
  • Was the profile where it needed to be at the end of the TI meeting, if not what was the gap
No. Much time spent on the issues described above
  • Do you need any tcons between now and TI Publication
Yes. Probably 4-6 @2 hours to start
Retrieved from "http://wiki.ihe.net/index.php?title=Rad_Tech_Minutes_2023-04-24-28&oldid=130127"