Minutes - Referral WG 2023-05-12

From Health Level 7 Belgium Wiki

Attendees

  • Anne Nerenhausen
  • Anthony Maton
  • Alexis Van Zeveren, Medispring
  • Bart Decuypere
  • Bart Reekmans
  • Dorsan de Fabricheckers
  • Emily Sevrin
  • Hans De Keersmaecker
  • Julien Beard
  • Karlien Erauw
  • Lionel Cremer
  • Maarten Cobbaert
  • Maxime Daive
  • Philippe Baise
  • Philippe Lejoly
  • Robin Merckx

Excused

  • Ben Goosse
  • Christophe Behaegel
  • Cyprien Janssens
  • Geert Vandenhole
  • Jacques Yakoub
  • Jean-Francois Coquelet
  • Jean-Michel Polfliet
  • José Costa Teixeira
  • Katleen Smedts
  • Katrien Dickx
  • Katrien Thorré
  • Marleen Van Eygen
  • Nathan Peeters
  • Laurent Lamouline
  • Pablo Christiaens
  • Pieter Devolder
  • Richard Francken

Agenda

  • continue resolution of issues

Meeting Minutes

  • Continue resolution of issues
  • namespace for identifier: an update with the security arguments was going to be provided ; no one present, no update received
  • will we add additional identifiers to the FHIR message; it is not up to the message to know where it will be used so it doesn't make sense to add identifiers ; however it would be easier for the prescriber softs and generating a UUID is a good practice
  • can we use an identifier in the header when sending the request, UHMEP would check the header and would send a message if already sent
  • everything on http level should be ok on FHIR level: will be checked by Bart/HL7 Belgium
  • execution period was mandatory, should be optional as the underlying field are optional
  • this is work in progress (not for June release), all feedback is welcome
  • changes have been made recently to the business rules
  • the values have been defined, they need to be added to orderDetail (5th option would be Other, in free text (on top of 1 Snomed code and temporary codes)
  • this is a basic prescription
  • looking into "1.5 Medication prefill preparation", see example here : is part of the June release but the example has not yet been created, will be done by next meeting
  • this would conclude all for the June release

Agenda next meeting

  • continue resolution of issues (214 is an important one)
  • continue review of examples of the use cases

Next meeting: next week Friday 26 May at 9AM