GDC Minutes 2023-04-05

Welcome

• Participants

• Mike Nusbaum (IHE Canada), co-Chair

• Agenda Approval

• Approved

• Permission to record this session

  Approved

National Deployment Committees

• Board reports and status updates

Rescheduling of Jun 7th Meeting

• Decision: Because of HIMSS -> re-scheduling on Jun 14th, 2023 (same time)

Future Special Presentations and tentative schedule 2023

• May 3, US/EU: Canada's Projectathon Results 2023 and expcted implications on procurement (Derek)
• Jun 14, EU/Asia: European EEHRxF and EHDS and its implications on the EU member states (Jürgen)
• Jul 5, Asia/US: tbd
• Aug 2, US/EU: tbd
• Sep 6, EU/Asia: XpanDH Project in Europe (Jürgen)
• Oct 4, Asia/US: tbd
• Nov 1, US/EU: tbd
• Dec 6, EU/Asia: Netherland's setting up of a National Test and Validation Center (Tie)

Special Topic: Connectathons / Projectathons and potential revenue streams

• Continue discussion of last call

• Key points of last call

• Projectathons are great, but there is a risk that this becomes a place where "propriety standardization happens"
• -> Feedback from projects/Projectathons back to standards development is needed (close loop)

• Several projects had this feedback loop (Austria, Swiss, ...)
• Coupling of IHE Catalyst with IHE Development Domains?

• Discussion

• Derek: Feedback loop is definitely required

• QRPH has strong relations to US, but tries to divide this feedback into what's "international" and what's US-specific

• General consensus: We need more "connection" of agencies/projects to IHE

• Derek: IHE should create processes which allow such a funding if it comes
• Jürgen: Projects should be encouraged to co-create their specifications with IHE. Has happened in the past, but not too often. Needs personal engagement of us to get them to (Deployment Committees)
• Derek: the bilateral meetings last year in Montreux have really influenced Infoway's thinking (especially including the ones with NL and Swiss!)
• Tie: Same for the Dutch delegation in Montreux
• Stephane: One problem is that "making it with IHE [or others]" is often considered as slowing down the realization

• Robin: IHE needs to look relevant (and be relevant) and our portfolio of specs looks like yesterday's news to an outside
• Roger: It's (still) not well known outside what IHE brings to the table -> this is a problem on government level
• Vince: In AUS in the Pathology area, currently not much drive to replace HL7v2 with FHIR, because it's simply working. Use of IHE needs to get much "easier"
• Tie: I think IHE has to think of another (additional) process in development of IHE profiles eg Sprint sessions of several days. Not having defined already a new IHE profile, but just start...18 months feels to the IHE outside world as 'slowing down vs FHIR process'. But they dont understand the difference between a FHIR profile and an IHE profile.
• Jürgen: The difference between countries seems to be huge. In some IHE has no standing, in others a very good one. Mostly an "impressive event" was the starting point for IHE being turned towards in those countries (such as a Connectathon visit, etc.)
• Stephane: IHE needs to become a bit more agile in evolving its profiles

Global Consortium for eHealth Interoperability Update

• No report

Open Forum (informal information sharing)

• None

Next meeting

• Wednesday, May 3, 2023, 09:00-10:00pm CDT (EU/US friendly time)
• Note: June 7th meeting moved to June 14th (same time)

Global Deployment Coordination Committee