Minutes - FHIR Validation Group 2024-11-07
From Health Level 7 Belgium Wiki
Agenda
- New Topics
- Presentation of New project proposal 'Childrecord' - Hanne
- HL7-be WG's activities
- Request for Publication for First version of Referral Prescription
- Pseudo v2 (Hanne)
- Follow-up
- Add links to the specific cookbooks related to vaults on the CareSets page of the eSanté website (Vaults)
- Definition of test template: to assist you with the test case requests to be implemented on the FHIR test server (Anne N.)
- 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) - Closed but To be documented on eSanté Portal
- 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
- 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
- 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
- Caresets
- 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
- '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.
- 'Must support' deprecation (from Hanne) - To be discussed
- 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 ?
- Feedback Business Publication (from Hanne) - To be discussed
Minutes
- Tooling usage in production:
- Like using the validator for all incoming messages in
- Statements: "The FHIR Tooling eco-system exists to support design time and publication usage. It is not intended to support production use, and should not be used in operational systems"
- Alternative
- Glossary
- Work in progress here: https://docs.google.com/spreadsheets/d/1gut8dBs6urWCm1USIrYLlH84Nxpxf554QT0KEXJcWQI/edit?usp=sharing
- MA will copy-paste her input in the Google Sheet
- Anne will plan a meeting for week 18/11
- Is getTransactionList compatible in FHIR?
- Functionally: yes
- Technically: Depends on expectations
- Publications of Business Docs must be provided for the following profiles:
- QA check for Patient Will (IG pulished)
- Update on Vaccination (after publication of IG for Vaccinet V2) (IG pulished)
- Complete check for Medication Line (IG publication on hold: waiting for Business Doc)
- Start the QA check and publication process for the IG even without the Business Doc
- Mappings:
- Khmer <=> Snomed-CT + Additional codes: Anne + JM will work on this
- Indications in Snomed-CT for Vaccines (vaccincodes) in SAMV2