Minutes - FHIR Validation Group 2024-01-04

Thursday, 4th January 2024, 10:00 CET

Agenda

• Projects Status
  • Publication of Pseudo - JM & Bart
  • FHIR-a-Thon - JM & Karlien
  • Caresets
    • SteerCo & Followup - Anne
    • Documentation - Anne
    • Note CG eHealth Platform - Anne
    • Process Improvement: Start 'Build' IG asap for new projects
  • Others
• FHIR Strategy
  • FHIR Versioning Strategy
• New Projects Proposal
  • Presentation of SamV2 over FHIR - Jeroen De Wilde
• New Projects to come
  • Cohbra over FHIR - JM
• Other Topics
  • Projects Overview
  • Meeting minutes
  • Agenda
  • Data Dictionary Template
  • Terminology Center Process
  • Publication of PatientWill
  • Publication of Profile Versioning
  • Give projects overview - at every meeting
  • Give feedback on European Joined Actions - at every meeting

Participants

• Bart Decuypere
• Jean-Michel Polfliet
• Veerle Michiels
• Philippe Baise - N
• Hanne Vuegen
• José Costa Teixeira
• Karlien Erauw
• Erwin Bellon - N
• Félix de Tavernier
• Filoretta Velica
• Anne Nerenhausen

Minutes

• SAMV2 over FHIR
  • Must be on R5
  • Sent to Programm Board B - No remark until here
  • Presented in WGSE
• R5 strategy
  • Discussion to be started - ASAP
  • We have to use a real project as a use case for the discussion like for Recip-e/Vidis/SAMV2
  • We must avoid to give a bad message to already ongoing projects on R4
  • What about the implementers that store FHIR-objects
  • https://github.com/ehealthplatformstandards/FHIRStandardVersioningStrategy

• Data Dictionary Template
  • Use the proposed template with a real example based on existing
  • To be rediscussed in an ad-hoc meeting

• Project Management Gantt chart
  • Check the possibility to have API-integrations with Google Sheet-like source of data

• PatientWill Publication
  • No remarks => Proceed with Publication on 12/1/2024

• Publication of Profile Versioning
  • To be presented

• Terminology Center Process
  • To be discussed in an ad-hoc meeting

• Communication / Meeting Invites
  • We have to find a way/tool to manage it without any work impact on Organizers (like Karlien)
  • In the meantime, we can publish a 'News' updated for every publication
  • Ballots step also must be managed