Minutes - FHIR Validation Group 2023-02-02

From Health Level 7 Belgium Wiki

Thursday, 02nd February 2023, 10:00 CET


  • COZO question about joining the FHIR Validation
  • Updates and feedback from previous requests for publication
  • Public Health IG approval
  • Vaccine codes updates
  • FHIR Maturity levels discussion


  • Freddy Carremans
  • Isabelle Pollet
  • Karlien Erauw
  • Bart Decuypere
  • Hanne Vuegen
  • Jean-Michel Polfliet
  • Veerle Michiels
  • Filoretta Velica
  • Anne Nerenhausen


COZO has asked if they could/should join the FHIR Validation team

We agree that we will invite the hubs also - so COZO and KU Leuven are going to be invited. We don't need a formal invite, RIZIV-INAMI (Anne) will update the calendar invite to include also the project managers. Karlien will inform them by email.

Updates and feedback from previous requests for publication


  • No objections received
  • We'll clean up the backlog (linking issues to changes) and in parallel eHealth will publish the profiles.
  • HL7 BE will ensure the updates and process are in order
  • **Agree for publication as new version of the federal standard**
  • This is a functional change, so it will be a minor version change (1.1.0)


  • No negative feedback received. The Validation WG agrees that this should go for publication - After the deadline has passed.
  • This will be published on the HL7 Belgium web site.
  • The eHealth site will also link to the HL7 IGs - e.g by adding a new card or other solution - eHealth will decide.
  • **Agree for publication as new Belgium Community standard**

Public Health

  • The standardization work is done. Some minor cosmetic fixes can be done but they are not blocking.
  • Our process determines (step 10) that the WGSE and PB will decide on the approval
  • We will send an email to the WGSE and inform them about the status. Send them a link to the IG and ask if they are interested in an ah-hoc meeting for a short presentation of the finished standard. If they don't want an ad-doc meeting and presentation, they will use 2 weeks to still provide feedback.
  • eHealth will discuss the content in the next WGSE (24th February) - so that there is a formal review, feedback, challenges...
  • eHealth will also discuss if the collaboration / feedback from WGSE can be streamlined to avoid long delays in the future.
  • In parallel, we will ask the community for their feedback.

Vaccine Code updates

  • We have worked on the vaccine codes for publication. Meanwhile some new codes were requested and should be added to the list.
    • This is necessary because the binding is required, so the new codes must be added.
  • When this is ready, there will be a new publication (can be a technical update) because the terminologies are currently hosted in the eHealth Implementation Guides. Normally would not even make it through the eHealth and HL7 process, because the terminologies would be hosted by the TC.

FHIR Maturity levels

  • We want to track the profiles as they get adopted, implemented, etc.
  • In FHIR we have FHIR maturity levels (http://build.fhir.org/versions.html#maturity) but this is bound to the HL7 process.
  • Proposal to use some indicator of maturity (a Belgian extension on the profiles) that defines how "ready" and "used" the profiles are.
  • We agree that we need to have the levels of maturity.
  • Levels (initial proposal):
    • Ready for implementation
    • Implemented (tested end-to-end, in production, or production-ready implementations)
    • Mature

We will start a proposal for defining these levels. This will consider key aspects like whether "mature" means "in production" etc. The proposal will be reviewed by this WG.