Minutes - Referral WG 2023-06-16

From Health Level 7 Belgium Wiki
Revision as of 08:02, 16 June 2023 by KarlienErauw (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Attendees

  • Anthony Maton
  • Bart Decuypere
  • Bart Reekmans
  • Ben Goosse
  • Cyprien Janssens
  • Emily Sevrin
  • Geert Vandenhole
  • Hans De Keersmaecker
  • Jean-Michel Polfliet
  • Julien Beard
  • Karlien Erauw
  • Maarten Cobbaert
  • Maxime Daive
  • Philippe Baise
  • Philippe Lejoly
  • Robin Merckx

Excused

  • Alexis Van Zeveren
  • Anne Nerenhausen
  • Christophe Behaegel
  • Dorsan de Fabricheckers
  • Jacques Yakoub
  • Jean-Francois Coquelet
  • José Costa Teixeira
  • Katleen Smedts
  • Katrien Dickx
  • Katrien Thorré
  • Lionel Cremer
  • Marleen Van Eygen
  • Nathan Peeters
  • Laurent Lamouline
  • Pablo Christiaens
  • Pieter Devolder
  • Richard Francken

Agenda

  • continue resolution of issues (214, 250 and new issues)

Meeting Minutes

  • Project Update
  • coobkbook pseudonmisation is missing details, a new update will be released by eHealth Platform, no update on when we might expect this
  • Update from Cyprien on an enhanced offer/comodity for integrators using $graph:
  • mainly ons SR is used for the phase 1 templates
  • bePerformerTask is used
  • working towards needing to do only one call
  • $graph resource will be used, which can return a bundle, a set of resources
  • the graph operation will be on the service request
  • there is an example of this bundle, starting with the SR, then practioner role resource
  • it is part of the October release and does not have any impact on the June release
  • it will be demonstrated in an example
  • Continue resolution of issues
  • issue 250: no update from Maarten from the business
  • issue 256: searching on the content is possible but no searching for the resource itself
  • the issue remains open as it has to be looked into detail
  • needed internal discussions
  • a date will be settled to discuss more
  • why not allow resource logical "identifier" to be used instead of technical "id" to reference a resource?
  • DPO needs to be consulted here


Agenda next meeting

  • continue resolution of issues and presentation of use cases

Next meeting: next week Friday 7 July at 9AM