Minutes - FHIR Validation Group 2024-09-12

From Health Level 7 Belgium Wiki

Agenda

  • New Topics
    • Is getTransactionList compatible in FHIR? (Hanne & Veerle)
    • Business rules BeAllergyIntolerance (see github)(Hanne & Veerle)
    • Business rules BeVaccination(Hanne & Veerle)
    • Sumehr in FHIR, clarification for all stakeholders(Hanne & Veerle)
    • What is the flow to add or change a SNOMED CT code? (Veerle)
    • Naming Convention for Logical models (Ilse Dossche)
    • Need for a Published Glossary
    • Diary Notes (linked to Vidis) (Didier Temans - Bart Verbeke)
    • Business Publication on Website eSanté: Document validated by Stakeholders - For Information
      • Next step: Patient Will
    • Publication of core from the HL7 Core - Follow-up - Bart
    • Update PopulationScreening - Veerle
    • Note au Commité de Gestion - Remarks and Followup - JM
    • FHIR Governance - Add QA + New steps regarding Commité de Gestion & Reporting - JM & Hanne
    • Request for Publication for Medication - Follow-up - Jose
    • FHIR-a-Thon - JM & Karlien
      • There is a need for Clarification about the different versions for Vaccination in RSW vs Vitalink (Vaccination v2 vs v1)
      • How to deal with the 2 versions: implementation aspect and documentation aspect (Business Documents)
  • Vaccination topics (from Isabelle)
    • Mise à disposition Mapping codes produits et vaccincodes -> Au niveau de la SAM v2 ? Est-ce que cette action est bien prise ne charge ? par qui ? quels sont les délais ?
    • Publication sur le site eHealth standard du Mapping entre CD-VACCINEINDICATION (Kmehr) et vaccincodes (FHIR) -> normalement promis pour la fin du mois de juin 2024 ; ou en est-on ?
  • Reference page for Build/Published Profiles - Meeting with JM & Jose
  • Hanne Topics
    • Documentation strategy: what is published when, by whom? -
      • Business rules doc  by esanté?
      • IG + guidance  by ehealth
        • Both documents need to be 100% compatible in term of content
      • What about generic technical information like versioning, use of security labels, use of identifiers, acces… ?
    • FHIR versioning strategy
      • Versioning of FHIR resources  Is there a validated approach? If yes, where to find? If no, how to continue discussion and where to publish?
      • Versioning of FHIR  How to make a transition to another FHIR version work in the ecosystem? We need a clear documented approach, backwards compatibility,…
    • Changes provided by the workgroup
      • How to handle change requests that are provided by the workgroups?
    • Alivia: question on organizing HL7 workgroups
    • Business Docs must be available when the Release Candidate is ready for Feedback, and must be attached to the communication email
  • Recurring topics
    • Terminology Center Process
    • Data Dictionary Template
    • Datacapabilities Project - Andries
      • Encounter - Trekker: Pablo
    • 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
    • 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
    • 'Must support' deprecation (from Hanne) - To be discussed
      • I am currently in a meeting for Xt-HER (patient summary workshop) where I hear that the ‘MUST SUPPORT’ classification in HL7 FHIR will be deprecated due to possibility on different interpretations. I know this is not the case yet, and I also know that we are in a earlier FHIR version where it will be in use. But due to these future changes I was wondering if we should keep a focus on this classification for the coming projects. It’s an open question maybe to discuss during the next validation team.
    • Feedback Business Publication (from Hanne) - To be discussed
      • Le KB78 n'existe plus et a été remplacé par la Loi relative à l'exercice des professions des soins de santé du 10 mai 2015 (WUG 2015). Je sais que nous parlons toujours des « KB78'ers » etc., mais je ne sais pas si nous pouvons y faire référence dans une publication formelle ?
      • En effet, les publications actuelles sont mentionnées. Tant pour l'Allergie que pour la Vaccination, une nouvelle version a été proposée pour validation. Ne devrions-nous pas, depuis cette page, faire référence aux ‘releasecandidates ? En principe, toute personne connaissant FHIR (et capable de lire un IG) devrait pouvoir évaluer la valeur des deux IGs. Les pages GitHub me semblent également intéressantes ?

Meeting Notes

    • Is getTransactionList compatible in FHIR? (Hanne & Veerle)
      • It is more wide subject. related to the Global Architecture (busy at RIZIV side)
    • Business rules BeAllergyIntolerance (see github)(Hanne & Veerle)
      • AP at Anne's side
    • Business rules BeVaccination(Hanne & Veerle)
      • AP at Anne's side
    • Sumehr in FHIR, clarification for all stakeholders(Hanne & Veerle)
      • Linked to Global Architecture + Transition plan
    • What is the flow to add or change a SNOMED CT code? (Veerle)
      • Take contact with Terminology Center
    • Naming Convention for Logical models (Ilse Dossche)
      • Ongoing
    • Need for a Published Glossary
      • Ongoing
    • Diary Notes (linked to Vidis) (Didier Temans - Bart Verbeke)
      • Follow-up by Anne N.
    • Business Publication on Website eSanté: Document validated by Stakeholders - For Information
      • Next step: Patient Will
      • Anne Nerenhausen will update the document and have it reviewed by the members of this group and WGSE.
    • Publication of core from the HL7 Core
      • Vaccination 1.1.0 - Core 2.1.2 successfully published
    • Note au Commité de Gestion
      • Comité de Gestion: 2nd Tuesday of every month. Only feedback from DIGIRELAB. We need progress on architecture and pseudonymisation.
    • FHIR Governance - Add QA + New steps regarding Commité de Gestion & Reporting - JM & Hanne
    • Request for Publication for Medication - Follow-up - Jose
    • FHIR-a-Thon - JM & Karlien

Fhir Governance: no work done. José adds issue about NamingConvention Medication: Nathan and José are preparing the publication of document and IG. Document will be ready by next meeting. Fhirization of SAMv2 is starting. FHIR-A-THON: Karlien is handling administration and budget. Tom Andries is to provide testcases for Abbott. There are still too few participants from Datacapabilities projects to the FHIR-A-TON. Vaccination: postponed because of the absence of Isabelle Pollet. Reference page for profiles: José and Jean-Michel will discuss this further. Vitalink: Imec has set up a formal test setup for the FHIR-A-TON Remove other topics by Hanne, except for the last one... Access and security labels: Is there a place where we can get legal input on security and patient rights? Félix says this is different for every region. Hanne would like to have an interfederal agreement on that. Profile versions: see infsec package FHIR standard versions: Now we are at R4, and there is no migration path to R5, R6... Deviations need to be discussed.

Retrieved from "https://wiki.hl7belgium.org/index.php?title=Minutes_-_FHIR_Validation_Group_2024-09-12&oldid=3066"