Minutes - Referral WG 2023-07-07

From Health Level 7 Belgium Wiki
Revision as of 07:17, 7 July 2023 by KarlienErauw (talk | contribs)

Attendees

  • Anne Nerenhausen
  • Bart Decuypere
  • Bart Reekmans
  • Elliot Ananaba (smals)
  • Emily Sevrin
  • Geert Vandenhole
  • Jean-Michel Polfliet
  • Julien Beard
  • Karlien Erauw
  • Maarten Cobbaert
  • Maxime Daive
  • Philippe Lejoly
  • Robin Merckx

Excused

  • Alexis Van Zeveren
  • Anthony Maton
  • Ben Goosse
  • Christophe Behaegel
  • Cyprien Janssens
  • Dorsan de Fabricheckers
  • Hans De Keersmaecker
  • 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
  • Philippe Baise
  • Richard Francken

Agenda

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

Meeting Minutes

  • Project Update
  • cookbook pseudonmisation is missing details, a new update will be released by eHealth Platform, no update yet on when we might expect this
  • Update from Julien on an enhanced offer/comodity for integrators using $graph:
  • it is part of the October release and does not have any impact on the June release
  • it is demonstrated in an example : there is a SR, a requester, practionerRole, all the tasks (global and performer tasks), all caregivers, when calling the graph you will get the resources in a bundle
  • the example will be added to the IG
  • Continue resolution of issues
  • issue 250: no update from Maarten from the business
  • it should be possible to assign two different caregivers or performers, so the cardinality should be 1 to many
  • so we need to add an extension
  • issue 257 nd issue 256: await discussion in HL7 BE WG infrastructure and security on 13 July
  • both niss and inami number will be available but inami number will be optional, niss is mandatory
  • will they be available only for search ? it seems vitalink also needs this


  • 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