Difference between revisions of "ITI Agenda July 2024 F2F"

Latest revision as of 09:34, 27 June 2024

This 5-days meeting is to move forward all the current work items in the continuous development cycle.

Meeting Location - RSNA Headquarters

Breakfast and Lunch will not be provided.

Teams information:

[tbd Join the Meeting here]

Meeting ID:

Passcode:

All times listed are tentative, and may be revised during the meeting; refresh often.

Day 1: Monday, 15 July 2024
Time Virtual (CDT, UTC−05:00)	Leads	Activity	Notes
8:30 am–9:00 am	Luke / John / Oliver / Steve	Introductions and Agenda Review Introductions Sponsor Communications https://www.ihe.net/about_ihe/patent_disclosure_process/ Agenda Review Decision Making and Goals Author commitments wiki updates, T-cons, F2F participation, ... continuous development: [Continuous Development] Public Comment Review DSG - JSON Signature -- https://github.com/IHE/ITI.DSGj Prepare for Public Comment Finance and Insurance Services -- https://github.com/IHE/ITI.Finance Scheduling for Mobile -- https://github.com/IHE/ITI.Scheduling projects Align DSUB with DSUBm (updates) ITI sex and gender profiling IPS Joint work assignments Integration of approved CPs Update existing IG, due to new publisher or bug reports Presentations for past releases DSUBm DSG JSON supplement	Participants: Minutes:
9:00 am–11:00 am	Ritika	DSG JSON	Agenda: Review Public-Comment, examples, and reference implementations Minutes:
11:00 am–12:00 pm	Luke / Uwe / Dragos	Finance and Insurance Services	Minutes:
12:00 am–1:30 am	all	Lunch
1:30 pm–3:00 pm	John	CP Integration	Minutes:
3:00 pm–4:00 pm	Joint PCC/ITI	IPS	Participants: Minutes:
4:00 pm–5:00 pm	John / Luke	Github issues	Minutes:

Day 2: Tuesday, 16 July 2024
Time Virtual (CDT, UTC−05:00)	Leads	Activity	Notes
8:30 am–10:00 am	Gianluca	Align DSUB with DSUBm	Participants: Minutes:
10:00 am–12:00 am	Luke / Uwe / Dragos	Finance and Insurance Services	Minutes:
12:00 am–1:30 am	all	Lunch
1:30 am–3:00 pm	Daniel	Connectathon Testing development planning	Minutes:
3:00 pm–5:00 pm	Vassil	Scheduling for Mobile	Minutes:

Day 3: Wednesday, 17 July 2024
Time Virtual (CDT, UTC−05:00)	Leads	Activity	Notes
8:30 am–10:00am	Ritika	DSG JSON	Participants: Minutes:
10:00 am–12:00pm	Luke / Uwe / Dragos	Finance and Insurance Services	Minutes:
12:00 am–1:30 pm	all	Lunch
1:30 pm–2:00pm	Vassil	Scheduling for Mobile	Minutes:
2:00 pm–3:00pm	John	IG Publisher (Open to All)	Minutes:
3:00 pm–5:00pm	All	Joint Domain Meeting	Minutes:

Day 4: Thursday, 18 July 2024
Time Virtual (CDT, UTC−05:00)	Leads	Activity	Notes
8:30 am–10:00am	Gianluca	Align DSUB with DSUBm	Participants: Minutes:
10:00 am–11:00 am	Luke / Uwe / Dragos	Finance and Insurance Services	Minutes:
11:00 am–12:00 pm	Sarah	CP Processing	Minutes:
12:00 pm–1:30 pm	all	Lunch
1:30 pm–3:00 pm	Vassil	Scheduling for Mobile	Minutes:
3:00 pm–4:00 pm	Steve	ITI sex and gender profiling	Participants: Minutes:

Day 5: Friday, 19 July 2024
Time Virtual (CDT, UTC−05:00)	Leads	Activity	Notes
8:30 am–12:00 pm	Luke / Oliver / John / Steve	Decisions and Open Agenda Questions stemming from Point of care ultrasound (Steve Nichols) Use-case https://drive.google.com/drive/folders/1E8KJl2A26LtJQtp0TIBw1xH7naciO-3W In the POCUS workflow, reports are generated on the POCUS Manager (i.e., PACS), and sent to the EMR. What attributes should be present to ensure they are correctly linked to the Patient's Encounter? When something goes wrong, and a report is not linked, how can this be corrected? In imaging, we can reject images using the IOCM profile (e.g. Inadvertent Capture of Images under the Wrong Patient ID). Is there an equivalent profile to reject and sequester EMR documents? Some vendors are enabling access to reporting application on the Modality. Some of these are web based, others on handheld devices may be app based. For web-based applications, there are several options for in-context launch SMART, FHIR Questionnaire, or something like IID. Is there a standard to launch a smartphone application in-context? Or is this something specific to the IOS or Android SDKs?	Participants: Minutes:

@@ Line 285: / Line 285: @@
 | style="text-align: center" |  Luke / Oliver / John / Steve
 | id="02-25-0830" | Decisions and Open Agenda
-* Point of care ultrasound (Steve Nichols)
+* Questions stemming from Point of care ultrasound (Steve Nichols)
 ** Use-case https://drive.google.com/drive/folders/1E8KJl2A26LtJQtp0TIBw1xH7naciO-3W
 ** In the POCUS workflow, reports are generated on the POCUS Manager (i.e., PACS), and sent to the EMR. What attributes should be present to ensure they are correctly linked to the Patient's Encounter? When something goes wrong, and a report is not linked, how can this be corrected?