ITI Agenda July 2024 F2F

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:

Join the Meeting here

Meeting ID: 284 717 523 903

Passcode: SRrSiu

Agenda & Minutes

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

Monday, 15 July 2024

Day 1: Monday, 15 July 2024

Time Virtual (CDT, UTC−05:00)	Leads	Activity	Notes
8:30 am–9:00 am	Luke / John / 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: John Moehrke, Luke Duncan, Gianluca Pavan, Diletta Babato, Chris Melo, Steve Nichols, Carl Leitner, Ritika Rawlani, Matt Blackmon Minutes: Goals DSG JSON to TI FAIS to PC Scheduling to PC Align DSUB continue work CP Integration Discussed FHIR R6 for comment ballot
9:00 am–11:00 am	Ritika	DSG JSON	Agenda: Review Public-Comment, examples, and reference implementations Minutes: Reviewed public comments: https://github.com/IHE/ITI.DSGj/issues Reviewed example: https://docs.google.com/document/d/1wdaqdn5-98A4uB6fQ0aqVQCopppw1nkpHFTVjiw583o/edit
11:00 am–12:00 pm	Luke / Uwe / Dragos	Finance and Insurance Services	Minutes: Reviewed transactions and conformance resources. Clean up TOC and header name on transaction Review R6 to see if enrollmentrequest has a $submit operation Simplify request expected actions to point to the message semantics (2:3.YY1.4.1.3 Expected Actions). Add response codes to message semantics. Add to concepts to show the overview of transactions and order of use like on FHIR financial module. See about splitting the actor/transaction diagrams into 3, or combine claims manager into one box.
12:00 am–1:30 am	all	Lunch
1:30 pm–3:00 pm	John	CP Integration	Minutes: IUA CP has already been integrated and published mCSD CP has been integrated on CI build
3:00 pm–4:00 pm	Joint PCC/ITI	IPS	Additional Participants: Lori, Andrea, Derek, Michael, Jenny Minutes: Reviewed connectathon setup for IPS. Discussed use of IPS
4:00 pm–5:00 pm	John / Luke	Github issues	Minutes: Reviewed issues on github IGs. Reviewed MHD pull requests

Tuesday, 16 July 2024

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: John, Chris, Luke, Diletta, Gianluca, Steve, Matt, Vassil Minutes: Reviewed CP https://github.com/IHE/IT-Infrastructure/tree/master/DSUB
10:00 am–12:00 am	Luke / Uwe / Dragos	Finance and Insurance Services	Minutes: Reviewed new transactions Set status to canceled in the expected actions for cancel. Review if one server actor is better Review actions for beneficiary requestor on creating Coverage or other supporting resources.
12:00 am–1:30 am	all	Lunch
1:30 am–3:00 pm	Daniel	Connectathon Testing development planning When will the Connectathon open for registration? Need to identify what can change in gazelle before then, and before the event. can we change "IPS" profile in Gazelle to "PCC-IPS" so as to distinguish PCC-IPS, from IHE-sIPS, from FHIR-IPS. Clinical Content for use in QEDm/IPS testing . is connectathon github going to be improved? Do we need a tool to generate clinical content. How can we emphasize creation of IPS testing, in a way we can contribute to the broader IPS community? How do we test for contextually complete (vs purely FHIR validated)? We would need a given set of clinical content, with expectations of the content given will be in the IPS.	Additional Participants: Daniel, Lori, Andrea, Didi Minutes: Reviewed EU connectathon details Included plugathon Non-structured, may help with adoption pre-TI on profiles Reviewed upcoming NA connectathon planning schedule Reviewed connectathon data Reviewed new connectathon results website. Discussed testplan resource
3:00 pm–5:00 pm	Vassil	Scheduling for Mobile	Minutes: Reviewed recent updates Discussed updates from argonaut specifically FHIR release and for international use Subset of operations Added FHIR search for appointments Limited operations to POST and added explicit data types Ready for committee review

Wednesday, 17 July 2024

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:

Thursday, 18 July 2024

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 BALP PR - Add support for Trace-Context - propose to accept as approved pull-request pending example change PR - Interpretation of sentence in Bundle.entry.response.outcome - propose to accept as approved pull-request Active CPs CP-ITI-1301 - Parameter homeCommunityId in [ITI-18] with patient id - propose to approve for CP ballot	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 CP-ITI-1297	Participants: Minutes:

Friday, 19 July 2024

Day 5: Friday, 19 July 2024

Time Virtual (CDT, UTC−05:00)	Leads	Activity	Notes
8:30 am–12:00 pm	Luke / John / Steve	Decisions and Open Agenda Formal approval of work item milestones Release to Public-Comment - Scheduling -- https://build.fhir.org/ig/IHE/ITI.Scheduling/index.html Release to Public-Comment - Finance and Insurance Service (FAIS) -- https://build.fhir.org/ig/IHE/ITI.Finance/index.html Assess New work item proposals -- https://github.com/orgs/IHE/projects/8 Sharing Verifiable Health Links -- https://github.com/IHE/IT-Infrastructure/issues/215 Validate workflow document updates -- https://github.com/IHE/IT-Infrastructure/issues/212 Pick new work items based on available Resources and Planning assed work items Questions stemming from Point of care ultrasound (Steve Nichols) Use-case 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 IID. Is there a standard to launch a smartphone application in-context? Or is this something specific to the IOS or Android SDKs? Are there standards for physician notifications that could be profiled?	Participants: Minutes: