Difference between revisions of "Minutes - FHIR Validation Group 2024-06-06"

From Health Level 7 Belgium Wiki
 
(7 intermediate revisions by the same user not shown)
Line 1: Line 1:
 
= Agenda =
 
= Agenda =
 
* New Topics
 
* New Topics
** Business Publication on Website eSanté: DOcument validated by Stakeholders - For Information
+
** Business Publication on Website eSanté: Document validated by Stakeholders - '''For Information'''
** Request for publication of core from the HL7 Core workgroup (Vitalink wants to use BeDocumentReference…) - Follow-up - Bart
+
*** Next step: Patient Will
** PopulationScreening: "Subject" has to be mandatory - Veerle
+
** Request for publication of core from the HL7 Core workgroup - Follow-up - Bart
 +
** Update PopulationScreening - Veerle
 
** Note au Commité de Gestion - Remarks and Followup - JM
 
** Note au Commité de Gestion - Remarks and Followup - JM
 
** FHIR Governance - Add QA + New steps regarding Commité de Gestion & Reporting - JM & Hanne
 
** FHIR Governance - Add QA + New steps regarding Commité de Gestion & Reporting - JM & Hanne
Line 26: Line 27:
 
** Data Dictionary Template
 
** Data Dictionary Template
 
** Datacapabilities Project - Andries
 
** Datacapabilities Project - Andries
 +
*** Encounter - Trekker: Pablo
 
** Allergy - Request for change from Corilus - Ongoing
 
** Allergy - Request for change from Corilus - Ongoing
 
** General Rule Core package
 
** General Rule Core package
Line 46: Line 48:
 
* Other Topics
 
* Other Topics
 
** Allergy & Snomed: https://github.com/hl7-be/allergy/issues/110
 
** Allergy & Snomed: https://github.com/hl7-be/allergy/issues/110
 +
 +
= Minutes =
 +
** Business Publication on Website eSanté: Document validated by Stakeholders - '''For Information'''
 +
*** Contact to INAMI Added
 +
*** 'Published caresets have been validated by eHP Commité Gestion following FHIR Governance process' added
 +
*** Next step: Patient Will
 +
** Request for publication of core from the HL7 Core workgroup
 +
*** BeDocumentReference already published
 +
*** To be published: Examples have been updated following the QA review process
 +
** Update PopulationScreening - Veerle
 +
*** Go for publication of the technical updates
 +
*** Question: Must this kind of publication be notified in a note to eHP Management Comittee
 +
** Note au Commité de Gestion - Remarks and Followup
 +
*** A new note with the 'Linked actions' follow-up will be presented on Tue 12/06
 +
*** FHIR Governance - Add QA + New steps regarding Commité de Gestion & Reporting - JM & Hanne
 +
** Request for Publication for Medication - Follow-up - Jose
 +
*** Status to be provided by Anne N.
 +
** FHIR-a-Thon - ''JM & Karlien''
 +
*** 25-26/11
 +
*** Scope including Data Capabilities
 +
*** Next phase in Vaccination and Allergy
 +
*** Labo Phase 2 (not yet decided)
 +
* Hanne Topics
 +
'''** Will be rediscussed when Hanne is back'''
 +
** 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

Latest revision as of 09:09, 6 June 2024

Agenda

  • New Topics
    • Business Publication on Website eSanté: Document validated by Stakeholders - For Information
      • Next step: Patient Will
    • Request for publication of core from the HL7 Core workgroup - 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
  • 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


  • 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

Minutes

    • Business Publication on Website eSanté: Document validated by Stakeholders - For Information
      • Contact to INAMI Added
      • 'Published caresets have been validated by eHP Commité Gestion following FHIR Governance process' added
      • Next step: Patient Will
    • Request for publication of core from the HL7 Core workgroup
      • BeDocumentReference already published
      • To be published: Examples have been updated following the QA review process
    • Update PopulationScreening - Veerle
      • Go for publication of the technical updates
      • Question: Must this kind of publication be notified in a note to eHP Management Comittee
    • Note au Commité de Gestion - Remarks and Followup
      • A new note with the 'Linked actions' follow-up will be presented on Tue 12/06
      • FHIR Governance - Add QA + New steps regarding Commité de Gestion & Reporting - JM & Hanne
    • Request for Publication for Medication - Follow-up - Jose
      • Status to be provided by Anne N.
    • FHIR-a-Thon - JM & Karlien
      • 25-26/11
      • Scope including Data Capabilities
      • Next phase in Vaccination and Allergy
      • Labo Phase 2 (not yet decided)
  • Hanne Topics

** Will be rediscussed when Hanne is back

    • 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