Difference between revisions of "Minutes - Security WG 2023-05-23"

From Health Level 7 Belgium Wiki
Line 43: Line 43:
 
* evolution of FHIR: a kind of end of life template is needed
 
* evolution of FHIR: a kind of end of life template is needed
 
::* work on FHIR capability server: have runtime information at one specific moment in time
 
::* work on FHIR capability server: have runtime information at one specific moment in time
 
+
::* intended data capabilities need to be written out
* versioning of resources: how to handle in FHIR
+
;;::* we discuss [https://drive.google.com/file/d/1bQg38faSQySh7NuXQrjG4WHJS-grbDbB/view?usp=share_link the presented document]
::* we discuss [https://drive.google.com/file/d/1bQg38faSQySh7NuXQrjG4WHJS-grbDbB/view?usp=share_link the presented document]
 
 
::* metadata meta.profile can be used but that should be done with caution ! a written guidance should be put together by HL7 Belgium
 
::* metadata meta.profile can be used but that should be done with caution ! a written guidance should be put together by HL7 Belgium
 
* the decision to migrate data to a new FHIR version has to be managed at project level by the project team
 
* the decision to migrate data to a new FHIR version has to be managed at project level by the project team
Line 53: Line 52:
  
 
===== Action items =====
 
===== Action items =====
* Security controls: continue work on use cases for permission and consent
+
* Position of HL7 Belgium on FHIR R5 release and versioniong needs to be written out (to cover the already upcoming questions from players and stakeholders in Belgium)
* Position of HL7 Belgium on the FHIR R5 release (to cover the already upcoming questions from players and stakeholders in Belgium)
+
* FHIR readiness of Belgian metahub-hub system: a guidance document needs to be started
* FHIR readiness of Belgian metahub-hub system: see preparation work
+
* Security controls & access controls: continue work on use cases for permission and consent
  
 
===== Next meetings =====
 
===== Next meetings =====
 
* Wednesday 14 June at 9AM online
 
* Wednesday 14 June at 9AM online

Revision as of 09:39, 23 May 2023

Attendees
  • Bart Decuypere
  • Benny Verhamme
  • Brecht Van Vooren (partially online)
  • Brian Thieren
  • Elien De Koker
  • Jean-Michel Polfliet
  • José Costa Teixeira
  • Karlien Erauw
  • Nick Hermans (partially online)
  • Steven Van den Berghe
  • Werner De Mulder
Excused/Not present
  • Anthony Maton
  • Cyprien Janssens
  • Didier Temans
  • Dominiek Leclerq
  • Erwin Bellon
  • Félix De Tavernier
  • Jan Stinissen
  • Filip Veldeman
  • Isabelle Pollet
  • Jan Lenie
  • Marco Busschots
  • Nico Vannieuwenhuyze
  • Philippe Baise
  • Stef Hoofd
Agenda
  • future work topics and way of working
Minutes
  • Determine scope and future action items of this working group
  • we need to look at the bigger picture and publish guidelines on a more strategic level
  • of course we need to continu to support projects to move towards mature FHIR implementations
  • on top of implementation guids we also need transition guides
  • what are the important topics that need our attention and for which guidelines are necessary:
  • hub/metahub system and FHIR readiness & functionalities
  • versioning and FHIR R5 release
  • access controls & security labels
  • evolution of FHIR: a kind of end of life template is needed
  • work on FHIR capability server: have runtime information at one specific moment in time
  • intended data capabilities need to be written out
  • metadata meta.profile can be used but that should be done with caution ! a written guidance should be put together by HL7 Belgium
  • the decision to migrate data to a new FHIR version has to be managed at project level by the project team
Action items
  • Position of HL7 Belgium on FHIR R5 release and versioniong needs to be written out (to cover the already upcoming questions from players and stakeholders in Belgium)
  • FHIR readiness of Belgian metahub-hub system: a guidance document needs to be started
  • Security controls & access controls: continue work on use cases for permission and consent
Next meetings
  • Wednesday 14 June at 9AM online