Minutes - FHIR Validation Group 2024-03-28

Agenda

• New Topics
  • Request for publication of core from the HL7 Core workgroup (Vitalink wants to use BeDocumentReference…) - Bart
  • PopulationScreening: "Subject" has to be mandatory - Veerle
  • Note au Commité de Gestion - Remarks and Followup - JM
  • "Validation by FHIR international" Topic - Jose
  • Request for Publication for Medication - Jose

• • Terminology Center Process
  • Data Dictionary Template
  • Datacapabilities Project - Andries
  • Allergy - Request for change from Corilus - Ongoing
  • General Rule Core package
  • Unique Identifier
  • Logical Model Lab IG
  • Patient Death Reporting
• Projects Status
  • Give projects overview for all active projects (Tools related)
  • European Joined Actions feedback
  • FHIR-a-Thon - JM & Karlien
  • Caresets
    • Next steps - Anne
  • Others
• FHIR Strategy
  • FHIR Versioning Strategy
• New Projects Proposal
• New Projects to come
  • Cohbra over FHIR - JM - to be started
• Other Topics
  • Allergy & Snomed: https://github.com/hl7-be/allergy/issues/110

Minutes

• Request for publication of core from the HL7 Core workgroup (Vitalink wants to use BeDocumentReference…) - Bart
  • Is this profile valid for all documents or only for Alivia?
    • Add in the guidance page that "This profile has been developed for the purpose of being used and possibly further developed for some projects. At this phase, the Working Group expects other projects and broader consensus on this. As a consequence, this profile may be especially subject to changes"
  • What about the other resources where attachments are available in the resource out-of-the-shelf
    • Maybe we can analyse further to have a consistent approach in all profiles
  • Release candidate: https://build.fhir.org/ig/hl7-be/core/branches/releasecandidate/
    • Issues in QA must be managed in an ad-hoc meeting with Jose and Bart
    • Methodology approach:
      • Proposal to approve the be core specification as present in the releasecandidate branch, provided the QA is free of errors and no warnings are shown
      • If some errors are not possible to be resolved, they will be discussed and will be sent to validation team members as a confirmation

• PopulationScreening: "Subject" has to be mandatory - Veerle
  • Managed by Github issues (mail to be received by
  • GO for the Change and republication

• Note au Commité de Gestion - Remarks and Followup - JM
  • Github's are the property of HL7-Be and are use according to the FHIR Governance
  • We have to improve the Handover from the WG's to the rest of the Governance process (like to eHealth platform Management Committee, WGSE, Program Board B,..)
    • Proposition is to tag the agreed open issues as "For next iteration" and add a printscreen to the 'Note for eHP Mngt Com.'
    • New issues introduced after this step are automatically considered as "For next iteration"

• "Validation by FHIR international" Topic - Jose
  • Input from Jose: "In some working groups (and possibly i have induced in the same error), I hear the expression "this aspect has been validated by FHIR international.". This statement doesn't seem to make sense as FHIR international doesn't exist, and HL7 international doesn't endorse or validate specifications. There is a way to seek alignment but in some projects i observe that the Belgian group members go fish for positive feedback. That is great but as members of the community we cannot take the answers we get as validation by the FHIR community and especially "validation by FHIR international". I would like to explain this as well as the mechanisms for "validation" so that the validation team members can help remove this issue in the different projects, instead of unknowingly amplifying it."
  • Proposition:
    • If it's in the norm/specification: we consider this as an authoritative position
    • If it's NOT in the norm/specification:
      • we do our best (including seeking in the community) to find a correct solution to our question/problem
      • Then we follow the FHIR Governance process