Minutes - FHIR Validation Group 2024-02-01

From Health Level 7 Belgium Wiki

Thursday, 1st February 2024, 10:00 CET

Agenda

  • Projects Status
    • Give projects overview for all active projects
    • 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

Participants

  • Anne Nerenhausen
  • Bart Decuypere
  • David Op de Beeck (partially)
  • Filoretta Velica
  • Hanne Vuegen
  • Jean-Michel Polfliet (partially)
  • José Costa Teixeira
  • Karlien Erauw (partially)
  • Marie-Alexandra Lambot
  • Philippe Baise
  • Veerle Michiels

Minutes

1) Terminology changes and profile freezes With regard to some remarks on the eHealth Management Committee, regarding the publishing and freezing of caresets (and the FHIR resource part of them), a clarification was asked about what impact this has on the link with terminology. There were two distinct points of view: from a medical point of view, endorsed by the NRC, terminology links from the FHIR profiles should always be modifiable according to the medical needs. From a software technical point of view, there was the remark that changes to a valueset managed by the NRC might have impact on the software, and might cause software developers, such as the vaults and the industry, to claim that the specification has changed, and thus the software development time (according to the agreements) should be restarted. The prevalent opinion is that “minor terminology changes” should be possible. However, we need a clear definition of what a minor change is, and what role “backwards compatibility” plays in it. “Backwards compatibility” is the main concern for software developers.

2) New developments at HL7 international with regard to interaction between the IG Publisher and the Validator and tx.fhir.org José further explained the modifications that were made to the tx.fhir.org terminology server (also known as the FHIR Int’l/Grahame Grieve terminology server) in order to enable it to be removed as a Single Point of Failure from the current HL7 FHIR Validation and Publication environment. These modifications are in line with what was presented last week, and make clear that Belgium needs an environment/architecture that avoids direct connection to the tx.fhir.org terminology server. This is possible since 16/1/2024, but a solution should be elaborated by the NRC and eHealth that enables to combine all terminology (both Belgian managed and FHIR Int’l managed) needs in one setup, that is transparent for the users (software vendors, hospitals, …). The NRC favours a decentral setup, because it minimizes the dependency from central components, and provides load balancing according to the needs of every company/institution. The question remains open who will provide the budget for the technical solution and maintain it.

3) Questions and updates about the R4/R5 migration or collaboration Some technical information (on the current situation 01/02/2024) has already been provided in document https://docs.google.com/document/d/1UUxCpMmkyr3z4_Au7x3SslKfwcb1ILLr/edit . We now strongly recommend organisations that already have applications in production, such as CIN/OAs and Vitalink, but also other organisations that are now developing, to estimate their costs and to indicate their preferred scenarios in the document above. We want to stress that projects such as SAMV2 on FHIR have indicated a preference to work with R5, and that many datacapabilities projects are looking at R5 (to base their logical models on).

4) We propose to invite Andries Nelissen, as the SPOC for the FPS datacapabilities projects to the FHIR validation team. Karlien, can you invite him?

5) Data Dictionary Template is postponed to next meeting

6) Terminology Centre Procedure as part of the FHIR Governance: Anne Nerenhausen, Marie Alexandra Lambot and David Op de Beeck are still working on a first draft.

7) There are requests for modification of the public-health IG (CvKO) -> a mail will be sent to the workgroup for approval.

8) There are requests for changes to allergy by Hans De keersmaecker (Corilus) -> check the urgency of the request.

9) There are requests from the field (datacapabilities projects) for the profiling of Procedure. Andries Nelissen should bring the involved projectleaders together to create a project proposal.

10) Marie Alexandra Lambot wants an index for all resources so that projects can see the status and other interested parties. For datacapabilities, this spreadsheet exists: https://docs.google.com/spreadsheets/d/1nyWc8bNyz0YJyZJIAaeNJd1FZttHk06N-dzVeraywkI/edit#gid=0

11) There is a request for a general rule in the “core” package about the use of the display field in codes. Bart will open an issue.